Thread (17 messages) read the whole thread 17 messages, 3 authors, 2008-03-07

Re: e2fsck dies with error "this should never happen!!!"

From: Bas van Schaik <hidden>
Date: 2008-02-22 17:44:31

Theodore Tso wrote:
quoted
On Fri, Feb 22, 2008 at 01:07:13PM +0100, Bas van Schaik wrote:
quoted
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.  Allocate<y>? yes

Directory inode 268451941 has an unallocated block #1.  Allocate<y>? yes

Directory inode 268451945 has an unallocated block #1.  Allocate<y>? yes

Directory inode 268451949 has an unallocated block #1.  Allocate<y>? yes

Directory inode 268451953 has an unallocated block #1.  Allocate<y>? yes

Directory inode 268451957 has an unallocated block #1.  Allocate<y>? yes

Directory inode 268451961 has an unallocated block #1.  Allocate<y>? yes

Directory inode 268451965 has an unallocated block #1.  Allocate<y>? yes

Directory inode 268451969 has an unallocated block #1.  Allocate<y>? yes

Directory inode 268451973 has an unallocated block #1.  Allocate<y>? yes

Directory inode 268451977 has an unallocated block #1.  Allocate<y>? yes

Directory inode 268451981 has an unallocated block #4.  Allocate<y>? 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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help