Bug 13230
Summary: | unexplained fsck error with ext4 on software raid 10 | ||
---|---|---|---|
Product: | File System | Reporter: | Florian Engelhardt (flo) |
Component: | ext4 | Assignee: | fs_ext4 (fs_ext4) |
Status: | CLOSED PATCH_ALREADY_AVAILABLE | ||
Severity: | high | CC: | tytso |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.29.2 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Florian Engelhardt
2009-05-03 12:53:05 UTC
What kind of filesystem operations were you doing, and how long had the filesystem been in service? This looks like an instance of "low block number corruption", which typically strikes the block group descriptors and inode table. It seems to happen mostly to people with RAID. We are very much interested in a way to easily reproduce this problem, as we haven't been able to reproduce it ourselves. I was coping files via NFS from my computer under my desk to that server. Something around 380 GB. The filesystem was serving until reboot ;) As i don´t need the server right now, i can build a tunnel and give you root access to that machine via ssh. Any news on this? I need to have this machine up and running stable until 15th of June, so i can still help, try patches, give you root access, ... As a matter of fact we think we found the cause of the problem just yesterday. The fix is now in mainline: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2ec0ae3acec47f628179ee95fe2c4da01b5e9fc4 Was this a problem you can easily reproduce? If so, I'd appreciate it if you could try out this patch, and confirm that you can no longer reproduce the problem with this patch. I applied that patch to the 2.6.29.4 kernel and recreated the filesystem. It´s up and running since four days now. I was not able to reproduce this bug. Good work, thanks so far. Is this patch also in the 2.6.30 mainline? This will allow me to switch back to the official kernel of my distribution. Yes, this patch is in 2.6.30, and it's in the 2.6.27.y and 2.6.29.y patches which Greg sent out for review yesterday. So 2.6.27.25 and 2.6.29.5 should have this patch when they get released next week. |