[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.4.15 (2.5.0) causes file system corruption
- To: mulix <mulix(at-nospam)actcom.co.il>
- Subject: Re: 2.4.15 (2.5.0) causes file system corruption
- From: Tzafrir Cohen <tzafrir(at-nospam)technion.ac.il>
- Date: Sat, 24 Nov 2001 14:22:45 +0200 (IST)
- Cc: <linux-il(at-nospam)linux.org.il>
- Delivered-To: linux.org.il-linux-il@linux.org.il
- In-Reply-To: <Pine.LNX.4.33.0111241244500.2159-100000@alhambra.merseine.nu>
- Sender: linux-il-bounce(at-nospam)cs.huji.ac.il
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'
(is 'sync' enough?)
>
> QA? wtf is QA?
That's what you get when you run a x.0 !
--
Tzafrir Cohen
mailto:tzafrir@technion.ac.il
http://www.technion.ac.il/~tzafrir
=================================================================
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