From: Russell King <rmk@arm.linux.org.uk>
To: Jahn Veach <V64@Galaxy42.com>
Cc: linux-kernel@vger.kernel.org, viro@math.psu.edu
Subject: Re: 2.4.15 + fs corruption.
Date: Fri, 23 Nov 2001 23:56:11 +0000 [thread overview]
Message-ID: <20011123235611.E3141@flint.arm.linux.org.uk> (raw)
In-Reply-To: <013601c17479$933f0450$2b910404@Molybdenum>
In-Reply-To: <013601c17479$933f0450$2b910404@Molybdenum>; from V64@Galaxy42.com on Fri, Nov 23, 2001 at 05:50:03PM -0600
On Fri, Nov 23, 2001 at 05:50:03PM -0600, Jahn Veach wrote:
> What kind of breakage are we looking at here? I had a system that ran 2.4.15
> and got shut down without a sync. What kind of corruption will occur and is
> it something a simple fsck will fix?
fsck does seem to fix it, but it won't automatically detect the problem
(since the filesystem is marked clean).
It basically removes the inodes from the disk, but leaves the names in
the directory. On the next boot, init scripts which clear out certain
directories fail, and various daemons fail to start because of it.
It seems that the only solution is to force a fsck at boot:
shutdown -F -r now
should do the trick.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-11-23 23:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 23:50 2.4.15 + fs corruption Jahn Veach
2001-11-23 23:56 ` Russell King [this message]
2001-11-24 0:11 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2001-11-23 22:45 war
2001-11-23 22:56 ` Alexander Viro
2001-11-23 23:10 ` Alexander Viro
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=20011123235611.E3141@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=V64@Galaxy42.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.