[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.4.15 (2.5.0) causes file system corruption



On Sat, 24 Nov 2001, Tzafrir Cohen wrote:

> On Sat, 24 Nov 2001, mulix wrote:
>
> > 2.4.15 has a problem with dirty inodes being left around on umount,
> > therefore causing file system corruption. don't run it if you value your
> > data. if you are already running it (i was), here are instructions what
> > to do:
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=100655627817897&w=2
> >
> > and here's a patch to fix it:
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=100655322609664&w=2
> >
> > if you already rebooted once with a 2.4.15 kernel, you probably want to
> > do 'shutdown -F -r now', to force fsck onboot. the file sytem is marked
> > clean, so fsck will *not* run automatically.
>
> What about 'touch /forcefsck; sync'

what's /forcefsck? i'm assuming it's a flag telling the init scripts to
run fsck?

> (is 'sync' enough?)

not sure. sync before umount should be enough, but can you make sure
things stay synced while you reboot? see al viro's mail for the except
steps necessary.

> > QA? wtf is QA?
>
> That's what you get when you run a x.0 !

wrong. 2.5.0 == 2.4.15, except for the version string. 2.4.11dont_use,
2.4.14 loop.o not compiling, 2.4.15eat_my_fs_please, need i say more?
-- 
mulix

http://www.pointer.co.il/~mulix/
http://syscalltrack.sf.net/



=================================================================
To unsubscribe, send mail to linux-il-request@linux.org.il with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail linux-il-request@linux.org.il