severity 310823 normal
tags 310823 unreproducible
thanks
On Thu, May 26, 2005 at 11:03:59AM +0200, Jo?o Miguel Neves wrote:
> Subject: e2fsprogs: e2fsck gets a signal 11 when clearing a i_fsize
> Package: e2fsprogs
> Version: 1.37+1.38-WIP-0509-1
> Severity: critical
> Justification: breaks the whole system
This is hardly a critical bug, as it occurs only in the case of a
filesystem corruption. It by the way is also something that I can't
reproduce.
> I had problems with the my root filesystem (setup at /dev/hda2).
> Automatic fsck at boot failed.
> fsck -y /dev/hda2 also failed.
> fsck /dev/hda2 reported a signal 11 everytime after reporting (from
> memory):
>
> i_fsize for inode XXX is YY (...) should be zero.
> Clear<y>?
>
> Everytime I pushed "y", it would crash.
When you have a problem like this, ***please*** save the full
transcript of the e2fsck run, and ideally, grab an raw e2image dump
(see the e2image man page). Otherwise there's very little I can do.
The case of clearing i_fsize is something which is already tested in
e2fsck's regression test suite (in the test f_badinode), and I always
test e2fsprogs against the full set of regression tests before I do a
release. I've tried it again, as well as trying a few other
variations to see if I can trigger a core dump, and I have not been
able to.
> Workaround was to say no to "Clear<y>?", let fsck put them in /lost
> +found, note down the inode numbers and delete the files (mounting the
> filesystem with errors).
... and I assume this means that you didn't capture any further
information before you worked around the problem. Sigh.
Please send me any additional information, since without any other way
to work this bug, I may have to close it as undreproducible.
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
