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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <47D145F8.3040300@tuxes.nl>
Date:	Fri, 07 Mar 2008 14:41:12 +0100
From:	Bas van Schaik <bas@...es.nl>
To:	Theodore Tso <tytso@....EDU>
CC:	linux-ext4@...r.kernel.org
Subject: Re: e2fsck dies with error "this should never happen!!!"

Bas van Schaik wrote:
> Theodore Tso wrote:
>   
>> 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.
>>   
>>     
> Last night I returned from my holiday trip, so I'm available again. The
> e2image dump completed somewhere during my absence and has grown to 1.6
> gigabytes (bzip2), too large to actually publish if you ask me. I think
> it is okay to provide you access to the system, please contact me
> (preferably using a GPG-encrypted message) so we can agree on the
> details. Of course it would be great if you can send a patch which will
> make e2fsck more verbose.

Hmmm, it is starting to annoy me that I can't get the filesystem to
work... I just tried to restore the ext3 metadata from a LVM snapshot
(taken two weeks ago, before running e2fsck), but that didn't work:
> # e2image /dev/loop1 e2image-pre-e2fsck-snapshot_2008-03-06
> e2image 1.40-WIP (14-Nov-2006)
> # e2image -I /dev/loop2 e2image-pre-e2fsck-snapshot_2008-03-06
> e2image 1.40-WIP (14-Nov-2006)
> e2image-pre-e2fsck-snapshot_2008-03-06: File too large

(note that loop0 is the real filesystem which is messed up and looks
unrecoverable, loop1 is the LVM snapshot I took before doing any attempt
to fix loop0 and loop2 is a LVM snapshot of loop0 which I created a few
hours ago to test e2image on without making things worse)

Why is e2image refusing to restore the metadata, and what does "File too
large" mean?

I think this is pretty much the moment were I can say "HELP!!!"

  -- Bas


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html