[gentoo-user] File system corruption?
Eric Paynter
with this:
>>> /usr/share/man/man3/English.3.gz
>>> /usr/share/man/man3/CGI::Push.3.gz
>>> /usr/share/man/man3/ExtUtils::Command.3pm.gz
>>> /usr/share/man/man3/File::Basename.3pm.gz
!!! ERROR: There appears to be FILE SYSTEM CORRUPTION. A file that
is listed
!!! as existing is not capable of being stat'd. If you are
using an
!!! experimental kernel, please boot into a stable one, force
an fsck,
!!! and ensure your filesystem is in a sane state. 'shutdown
-Fr now'
!!! File:
/var/tmp/portage/perl-5.8.3/image/usr/share/man/man3/Hash::Util.tmp
!!! Error: [Errno 2] No such file or directory:
'/var/tmp/portage/perl-5.8.3/image/usr/share/man/man3/Hash::Util.tmp'
Now, I did the recommended 'shutdown -Fr now' and got the same
error, so I cd-booted and did a "fsck.ext3 -c -c /dev/hda1" (which
ran for several hours!!!) and still the same error. Is the problem
really filesystem corruption? Or what else might it be?
btw, it's a 2.4.22-gentoo-r7 kernel...
Thanks for any help!
-Eric
--
arctic bears - email and name services
25 email addresses@yourdomain CA$11.95/month
DNS starting at CA$3.49/month - domains from CA$25.95/year
for details contact in...@arcticbears.com or visit
http://www.arcticbears.com
--
gento...@gentoo.org mailing list
Mark Knecht
Eric,
This is a known bug with hashed btrees in the ext3 filesystem. It's
been around a while. Don't know why it isn;t getting fices unless the
fix is difficult.
Take a look at
http://bugs.gentoo.org/show_bug.cgi?id=24991
for a fix. Basically:
1) turn off the btree stuff
2) erase the left over MERGING files
3) do the emerge of perl again
4) Turn on btrees
Good luck,
Mark
P.S. - It was in the bug system, so maybe a search there in the future
would be a good idea. - MWK
--
gento...@gentoo.org mailing list
Eric Paynter
> This is a known bug with hashed btrees in the ext3 filesystem.
Hmmm... known bugs in the filesystem not getting fixed... kinda
scary...
Anyhow, thanks for the tip. I'm trying the emerge again with the
suggested workaround. Hopefully it works. :)
-Eric.
Collin Starkweather
> > !!! ERROR: There appears to be FILE SYSTEM CORRUPTION. A file that
> > is listed
>
> been around a while. Don't know why it isn;t getting fices unless the
> fix is difficult.
This has got to be the worst error message I've seen in some time. It
is basically a panic inducer where there is no need for one.
I have a question for those who know a thing or two about filesystems
(which I do not count myself amongst). I have a server that I won't
have physical access to for at least a few weeks. Unmounting /var and
tune2fsing as recommended in the bug report would be a major pain and I
would like to wait until I have physical access to the box just in
case.
Is this something that can cause cascading problems or can I put it off
for a few weeks? (So far the box has been functioning perfectly.) Any
thoughts / advice would be appreciated.
-Collin
P.S. I asked the same question of the bug responders on Bugzilla but
so far have gotten nada.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Collin Starkweather, Ph.D. collin.st...@collinstarkweather.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
gento...@gentoo.org mailing list
Eric Paynter
> I have a question for those who know a thing or two about
> filesystems (which I do not count myself amongst). I have a
> server that I won't have physical access to for at least a few
> weeks. Unmounting /var and tune2fsing as recommended in the bug
> report would be a major pain and I would like to wait until I have
> physical access to the box just in case.
I ran the tune2fs command (tune2fs -O ^dir_index /dev/hda1) on the
*mounted* filesystem and successfully merged the package that was
causing errors.
Mark Knecht
> Collin Starkweather said:
>
>>I have a question for those who know a thing or two about
>>filesystems (which I do not count myself amongst). I have a
>>server that I won't have physical access to for at least a few
>>weeks. Unmounting /var and tune2fsing as recommended in the bug
>>report would be a major pain and I would like to wait until I have
>>physical access to the box just in case.
>
>
> I ran the tune2fs command (tune2fs -O ^dir_index /dev/hda1) on the
> *mounted* filesystem and successfully merged the package that was
> causing errors.
>
> -Eric
>
That's the way I did it and I was fine also.
Same the instructions...you're likely to run into this again. I've seen
it twice.
To answer Colin's question, there is no cascading problem that I know
of. You jsut won't be able to get past the emerge of this package.
- Mark
--
gento...@gentoo.org mailing list