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]
Date:	Sun, 02 Mar 2008 20:08:47 +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!!!"

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.

  -- 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ