[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.4.15 (2.5.0) causes file system corruption
- To: "Nadav Har'El" <nyh(at-nospam)math.technion.ac.il>
- Subject: Re: 2.4.15 (2.5.0) causes file system corruption
- From: mulix <mulix(at-nospam)actcom.co.il>
- Date: Sat, 24 Nov 2001 18:01:26 +0200 (IST)
- Cc: <linux-il(at-nospam)linux.org.il>
- Delivered-To: linux.org.il-linux-il@linux.org.il
- In-Reply-To: <20011124175548.A22459@leeor.math.technion.ac.il>
- Sender: linux-il-bounce(at-nospam)cs.huji.ac.il
On Sat, 24 Nov 2001, Nadav Har'El wrote:
> On Sat, Nov 24, 2001, mulix wrote about "2.4.15 (2.5.0) causes file system corruption":
> > 2.4.15 has a problem with dirty inodes being left around on umount,
> >...
> > QA? wtf is QA?
>
> QA is when you let people use the kernel for a little more than 2 days before
> everybody and their uncle starts using this kernel...
in this case, QA is when you make sure the -pre kernel is used for more
than a day before you release -final, and -final is *exactly the same*
as -pre. you think having 2.4.14-pre used for a week or so wouldnt have
caught the loop.o bug? or using 2.4.15-pre for a week or so wouldnt have
caught the fs corruption bug?
> This is why I usually use Redhat's kernels, and now I'm using their 2.4.9.
> It is not the most state-of-the-art kernel, maybe it even has some bugs, but
> at least it was checked for enough time to make sure there are no "obvious"
> bugs (like umount corrupting the filesystem). I see no reason to always
> upgrade to the latest kernel-du-jour, unless of course you really need some
> feature that appeared only in 2.4.15.
i willingly live on the cutting edge. i take this choice of my own free
will. yet i still reserve the right to rave when a supposedly *stable*
kernel is oh so b0rken.
--
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