On Saturday 24 November 2001 19:28, Stefan Smietanowski wrote:
> Hi people.
>
> I might have triggered a bug, but I haven't looked into where it's at.
> If it's the filesystem or the kernel.
>
> I downloaded the 2.4.15-pre7 kernel from cvs and I ran it for 24 hours
> about.
>
> Today I went into a directory to run a program and the binary was ..
> broken. Couldn't load.
>
> Tried recompiling from source and that failed too, so I looked at the
> source file and it was missing the end of the file.
> It was my source so I gather it was the last bytes that were missing.
Stefan,
If you were running 2.4.15-pre9, I'd say it was the new major oops in the
kernel. Fixed in 2.4.16pre1. In case you somehow got caught, here are Al
Viro's suggestions on fixing it.
> 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
Peter
|