Re: fsck problems
This is a known bug, it was announced yesterday on debian-devel. We've
been in contact with the upstream maintainer, Ted T'so. It appears to be
a bug in glibc. The crux of the bug is that for partitions over 2 gig,
the function llseek is used. Well it seems the implementation in glibc is
buggy, and causes fsck to wack out on large partitions.
Well it seems that unstable really is unstable now. :-)
Shaya
On Mon, 21 Jul 1997, Alex Romosan wrote:
> this is a warning to everybody running e2fsprogs version 1.10-4. there
> is something really wrong with it, i've lost my second file system in
> the past few days. i downgraded to e2fsprogs version 1.10-2 which
> seems to be a bit more stable but i still can't recover from the
> damage done by version 4. when i run fsck now i get something like:
>
> no room left in lost+found. expand? yes
>
> and then fsck core dumps. i am still hoping i can recover this file
> system (i had to re-install from scratch on the other computer). does
> anybody have any ideas what i can do next? how can i increase the size
> of the lost+found directory? this is kind of urgent. thanks.
>
> --alex--
>
> --
> | I believe the moment is at hand when, by a paranoiac and active |
> | advance of the mind, it will be possible (simultaneously with |
> | automatism and other passive states) to systematize confusion |
> | and thus to help to discredit completely the world of reality. |
>
>
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> debian-user-request@lists.debian.org .
> Trouble? e-mail to templin@bucknell.edu .
>
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: