From: Brian Litzinger <snblitz@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Filesystem corruption 1,800,000 inodes and counting
Date: Sun, 18 Jul 2004 10:06:06 -0700 [thread overview]
Message-ID: <d6fc441b04071810063fcf493b@mail.gmail.com> (raw)
Sorry to double post. The machine that is down processes most of my
email. However,
this account works.
A machine froze after 30 days uptime. After reboot, it fell out of
fsck with an unrecoverable
error.
I ran fsck -C -y /dev/md1. At 73% it starting reporting
Unattached inode 250143
Connect to /lost+found? yes
Inode 1815609 ref count is 2, should be 1. Fix? yes
It has gone from 250143 to 1815610 doing this over the last 36 hours.
And so far as I know will do on doing this forever?
Linux 2.4.25 untainted. ext2 filesystem (no journaling).
Any advice on how I should proceed?
reply other threads:[~2004-07-18 17:06 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=d6fc441b04071810063fcf493b@mail.gmail.com \
--to=snblitz@gmail.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