* Re: 2.4.15 + fs corruption.
@ 2001-11-23 23:50 Jahn Veach
2001-11-23 23:56 ` Russell King
2001-11-24 0:11 ` Andreas Dilger
0 siblings, 2 replies; 6+ messages in thread
From: Jahn Veach @ 2001-11-23 23:50 UTC (permalink / raw)
To: linux-kernel; +Cc: viro
> Breakage happens when you umount filesystem (_any_ local filesystem, be
> it ext2, reiserfs, whatever) that still has dirty inodes.
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?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.4.15 + fs corruption.
2001-11-23 23:50 2.4.15 + fs corruption Jahn Veach
@ 2001-11-23 23:56 ` Russell King
2001-11-24 0:11 ` Andreas Dilger
1 sibling, 0 replies; 6+ messages in thread
From: Russell King @ 2001-11-23 23:56 UTC (permalink / raw)
To: Jahn Veach; +Cc: linux-kernel, viro
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: 2.4.15 + fs corruption.
2001-11-23 23:50 2.4.15 + fs corruption Jahn Veach
2001-11-23 23:56 ` Russell King
@ 2001-11-24 0:11 ` Andreas Dilger
1 sibling, 0 replies; 6+ messages in thread
From: Andreas Dilger @ 2001-11-24 0:11 UTC (permalink / raw)
To: Jahn Veach; +Cc: linux-kernel, viro
On Nov 23, 2001 17:50 -0600, Jahn Veach wrote:
> > Breakage happens when you umount filesystem (_any_ local filesystem, be
> > it ext2, reiserfs, whatever) that still has dirty inodes.
>
> 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?
Well it appears to leave inodes around which do not point at existing files.
It is easy to fix on ext2/ext3, but may be harder for reiserfs. Maybe
reiserfs shows the problem differently, though, I don't know.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
^ permalink raw reply [flat|nested] 6+ messages in thread
* 2.4.15 + fs corruption.
@ 2001-11-23 22:45 war
2001-11-23 22:56 ` Alexander Viro
0 siblings, 1 reply; 6+ messages in thread
From: war @ 2001-11-23 22:45 UTC (permalink / raw)
To: linux-kernel
Is 2.4.15 ok to use?
Many people are experiencing filesystem corruption?
As long as you patch the kernel with Al Viro's patch it should be ok,
right?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.4.15 + fs corruption.
2001-11-23 22:45 war
@ 2001-11-23 22:56 ` Alexander Viro
2001-11-23 23:10 ` Alexander Viro
0 siblings, 1 reply; 6+ messages in thread
From: Alexander Viro @ 2001-11-23 22:56 UTC (permalink / raw)
To: war; +Cc: linux-kernel
On Fri, 23 Nov 2001, war wrote:
> Is 2.4.15 ok to use?
> Many people are experiencing filesystem corruption?
>
> As long as you patch the kernel with Al Viro's patch it should be ok,
> right?
In theory. Again, as a workaround - sync before umount (and don't boot
unpatched 2.4.15/2.4.15-pre9 again, obviously).
Breakage happens when you umount filesystem (_any_ local filesystem, be
it ext2, reiserfs, whatever) that still has dirty inodes.
IOW, if you are running 2.4.15 - build a patched kernel, install it and
do the following:
* switch to single-user
* sync
* umount everything non-buys
* remount the rest read-only
* turn the thing off
* boot with patched kernel or with anything before 2.4.15-pre9
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2001-11-24 0:15 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-11-23 23:50 2.4.15 + fs corruption Jahn Veach
2001-11-23 23:56 ` Russell King
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
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.