e2fsck dies with error this should never happen!!!
Hi all, Currently, I have a big problem: e2fsck refuses to fix my currupted filesystem... The filesystem (about 3TB) is created on an LVM LV, which spans a number of RAID5 arrays, for which the underlying devices are imported using ATA over Ethernet. Because of some strange network failure, the filesystem got corrupted and was remounted read-only. e2fsck presented me really _a lot_ of errors, especially much duplicated blocks. After fixing them all, e2fsck restarts the check and after a while dies with XXX should never happen!!!. The complete output: e2fsck 1.40-WIP (14-Nov-2006) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Directory inode 268451937 has an unallocated block #1. Allocate? yes Directory inode 268451941 has an unallocated block #1. Allocate? yes Directory inode 268451945 has an unallocated block #1. Allocate? yes Directory inode 268451949 has an unallocated block #1. Allocate? yes Directory inode 268451953 has an unallocated block #1. Allocate? yes Directory inode 268451957 has an unallocated block #1. Allocate? yes Directory inode 268451961 has an unallocated block #1. Allocate? yes Directory inode 268451965 has an unallocated block #1. Allocate? yes Directory inode 268451969 has an unallocated block #1. Allocate? yes Directory inode 268451973 has an unallocated block #1. Allocate? yes Directory inode 268451977 has an unallocated block #1. Allocate? yes Directory inode 268451981 has an unallocated block #4. Allocate? yes XXX should never happen!!! Aborted Furthermore I'm running the default Debian stable kernel 2.6.18. When trying to mount the damaged filesystem and removing the directories which were supposed to have problems (I saw some output about those directories in earlier e2fsck runs), the filesystem of course reports problems: # dmesg | tail kjournald starting. Commit interval 10 seconds EXT3-fs warning: mounting fs with errors, running e2fsck is recommended EXT3 FS on loop0, internal journal EXT3-fs: mounted filesystem with writeback data mode. EXT3-fs error (device loop0): ext3_free_inode: bit already cleared for inode 275087393 Remounting filesystem read-only Can anyone please help me fix this filesystem? I will be on vacation next week, so my reply might be a little bit late... Thanks! Regards, -- Bas - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: e2fsck dies with error this should never happen!!!
Theodore Tso wrote: On Fri, Feb 22, 2008 at 01:07:13PM +0100, Bas van Schaik wrote: Hi all, Currently, I have a big problem: e2fsck refuses to fix my currupted filesystem... The things that I would suggest first of all is upgrading to the latest version of e2fsprogs. If that doesn't fix it, I'm going to need either a compressed e2image file (see the e2image man page) or login access to see what is up. Thanks for the suggestion, I was naively assuming that e2fsck wasn't under active development. I've installed the statically linked 1.40.6 from Debian Lenny and it's running. However, it will take quite a long time before it will actually hit the point where the old version found problems. I'll let you know what the results are! Regards, -- Bas - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: e2fsck dies with error this should never happen!!!
Theodore Tso wrote: On Fri, Feb 22, 2008 at 01:07:13PM +0100, Bas van Schaik wrote: Hi all, Currently, I have a big problem: e2fsck refuses to fix my currupted filesystem... The things that I would suggest first of all is upgrading to the latest version of e2fsprogs. If that doesn't fix it, I'm going to need either a compressed e2image file (see the e2image man page) or login access to see what is up. Thanks for the suggestion, I was naively assuming that e2fsck wasn't under active development. I've installed the statically linked 1.40.6 from Debian Lenny and it's running. However, it will take quite a long time before it will actually hit the point where the old version found problems. I'll let you know what the results are! Unfortunately it didn't work out. Apart from the e2fsck version number, the output did not change: e2fsck 1.40.6 (09-Feb-2008) /dev/loop0: recovering journal Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Directory inode 268451937 has an unallocated block #1. Allocatey? yes Directory inode 268451941 has an unallocated block #1. Allocatey? yes Directory inode 268451945 has an unallocated block #1. Allocatey? yes Directory inode 268451949 has an unallocated block #1. Allocatey? yes Directory inode 268451953 has an unallocated block #1. Allocatey? yes Directory inode 268451957 has an unallocated block #1. Allocatey? yes Directory inode 268451961 has an unallocated block #1. Allocatey? yes Directory inode 268451965 has an unallocated block #1. Allocatey? yes Directory inode 268451969 has an unallocated block #1. Allocatey? yes Directory inode 268451973 has an unallocated block #1. Allocatey? yes Directory inode 268451977 has an unallocated block #1. Allocatey? yes Directory inode 268451981 has an unallocated block #4. Allocatey? yes XXX should never happen!!! Aborted In a few hours I will hit the road towards France for a holiday, from which I will return on the 3rd of March. I would be _really_ grateful if you could assist me solving this problem. Regards, -- Bas - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: e2fsck dies with error this should never happen!!!
Bas van Schaik wrote: In a few hours I will hit the road towards France for a holiday, from which I will return on the 3rd of March. I would be _really_ grateful if you could assist me solving this problem. Providing the compressed e2image would let ted or others look into the problem. Thanks, -Eric - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: e2fsck dies with error this should never happen!!!
Bas van Schaik wrote: In a few hours I will hit the road towards France for a holiday, from which I will return on the 3rd of March. I would be _really_ grateful if you could assist me solving this problem. Providing the compressed e2image would let ted or others look into the problem. Should that be a raw image or a 'normal' one? -- Bas - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: e2fsck dies with error this should never happen!!!
Bas van Schaik wrote: Bas van Schaik wrote: In a few hours I will hit the road towards France for a holiday, from which I will return on the 3rd of March. I would be _really_ grateful if you could assist me solving this problem. Providing the compressed e2image would let ted or others look into the problem. Should that be a raw image or a 'normal' one? Raw, I think; that way you can compress it as well. -Eric - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: e2fsck dies with error this should never happen!!!
Bas van Schaik wrote: Bas van Schaik wrote: In a few hours I will hit the road towards France for a holiday, from which I will return on the 3rd of March. I would be _really_ grateful if you could assist me solving this problem. Providing the compressed e2image would let ted or others look into the problem. Should that be a raw image or a 'normal' one? Raw, I think; that way you can compress it as well. I'm working on it, but it seems that the image creation process is going to take a long time... If it will make it before my departure, I will publish it somewhere and post the link here. If it takes too long, I will publish it in about a week and a half. Thanks for your support! -- Bas - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: e2fsck dies with error this should never happen!!!
On Fri, Feb 22, 2008 at 07:06:10PM +0100, Bas van Schaik wrote: Bas van Schaik wrote: Bas van Schaik wrote: In a few hours I will hit the road towards France for a holiday, from which I will return on the 3rd of March. I would be _really_ grateful if you could assist me solving this problem. Providing the compressed e2image would let ted or others look into the problem. Should that be a raw image or a 'normal' one? Raw, I think; that way you can compress it as well. I'm working on it, but it seems that the image creation process is going to take a long time... If it will make it before my departure, I will publish it somewhere and post the link here. If it takes too long, I will publish it in about a week and a half. Yeah, it could be quite big, given that you have a 3TB filesystem. That's why I suggested the or given me login access to the system, although understand there could be all sorts of privacy and security issues involved with that request. - Ted - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: e2fsck dies with error this should never happen!!!
On Fri, Feb 22, 2008 at 07:06:10PM +0100, Bas van Schaik wrote: Bas van Schaik wrote: Bas van Schaik wrote: In a few hours I will hit the road towards France for a holiday, from which I will return on the 3rd of March. I would be _really_ grateful if you could assist me solving this problem. Providing the compressed e2image would let ted or others look into the problem. Should that be a raw image or a 'normal' one? Raw, I think; that way you can compress it as well. I'm working on it, but it seems that the image creation process is going to take a long time... If it will make it before my departure, I will publish it somewhere and post the link here. If it takes too long, I will publish it in about a week and a half. Yeah, it could be quite big, given that you have a 3TB filesystem. That's why I suggested the or given me login access to the system, although understand there could be all sorts of privacy and security issues involved with that request. The dump is not ready yet... Whatever we will do, it will have to wait for a week and a half. For now I really appreciate all the help. Cheers, -- Bas - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: e2fsck dies with error this should never happen!!!
On Fri, Feb 22, 2008 at 08:31:13PM +0100, Bas van Schaik wrote: Yeah, it could be quite big, given that you have a 3TB filesystem. That's why I suggested the or given me login access to the system, although understand there could be all sorts of privacy and security issues involved with that request. The dump is not ready yet... Whatever we will do, it will have to wait for a week and a half. For now I really appreciate all the help. Ok, when you get back, I should also have a patch for you that will allow the XXX should never happen message to display more information, so if the dump is too big for us to move over the network, I'll have another way of doing some remote debugging. - Ted - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
