From: Brian Litzinger <brian@worldcontrol.com>
To: linux-kernel@vger.kernel.org
Subject: FileSystem Corruption 1,493,339 and counting
Date: Sat, 17 Jul 2004 21:32:24 -0700 [thread overview]
Message-ID: <20040718043224.GA11925@top.worldcontrol.com> (raw)
The other day a machine of mine froze for reasons unknown after about
30 days of uptime. No response to anything.
Upon reboot it got an unrecoverable file system error during
fsck.
So I dropped into a shell and issued the command fsck -y -C /dev/md1.
Around 73% it starting reporting
Unattached inode 250083
Connect to /lost+found? yes
Inode 250083 ref count is 2, should be 1. Fix? yes
This has been going on for 24 hours now, and fsck is
at
Unattached inode 1494419
Connect to /lost+found? yes
Inode 1494419 ref count is 2, should be 1. Fix? yes
Do you suppose this will ever end? Has fsck gotten into
an infinite loop? Shall I scrap the filesystem or let
it keep going?
How many days might it take?
I'm running linux 2.4.25 untainted with an ext2 filesystem
on an Athlon XP 2000+.
--
Brian Litzinger
reply other threads:[~2004-07-18 4:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040718043224.GA11925@top.worldcontrol.com \
--to=brian@worldcontrol.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox