Re: Don't use kernel 2.4.15/2.5.0 (fs corruption) [BANDAID]
In article <[🔎] 20011124191048.A4771@muffin.local.lan>,
Veit Waltemath <veitw@wsbt.de> wrote:
>On Sat, Nov 24, 2001 at 10:11:06AM -0200, Jeronimo Pellegrini wrote:
>> "2.4.15: FS corruption on EXT2"
> ^^^^
>Only on EXT2 or on all fs, i'm using EXT3.
All filesystems. The broken versions are 2.4.15-pre9 and
2.4.15 itself (aka 2.4.15-greased-turkey). Versions before that
are presumably not broken.
The jury is still out on the correct way to fix it. Several
patches have been posted to the kernel mailinglist, they all
appear to fix the problem so it's now a question of which
patch is the most aestethically pleasing, I think.
Anyway they say one way to prevent the problem is to call
sync before umount, so if you edit /etc/init.d/umountfs and
put a line with just the word "sync" just above every line
that starts with "umount" or "mount" you should be safe for now.
Note that this is not the "right" fix, the "right" fix should
be in the next kernel! It's just a bandaid.
Here's an untested patch:
--- /etc/init.d/umountfs.orig Tue Nov 6 13:18:43 2001
+++ /etc/init.d/umountfs Sat Nov 24 18:25:13 2001
@@ -12,6 +12,7 @@
*) FORCE="-f" ;;
esac
+sync
umount -ttmpfs $FORCE -a -r
echo -n "Deactivating swap... "
@@ -20,9 +21,11 @@
# We leave /proc mounted.
echo -n "Unmounting local filesystems... "
+sync
umount -tnoproc $FORCE -a -r
echo "done."
+sync
mount -n -o remount,ro /
: exit 0
Mike.
--
"Only two things are infinite, the universe and human stupidity,
and I'm not sure about the former" -- Albert Einstein.
Reply to: