![]() | |||||||||||||
Messages in this thread |
On Sun, Mar 17, 2002 at 08:03:17PM -0700, Andreas Dilger wrote: > On Mar 17, 2002 10:37 -0800, Mike Fedyk wrote: > > On Sun, Mar 17, 2002 at 12:26:53AM -0700, Andreas Dilger wrote: > > > Yes, I have always considered this a kernel bug (introduced in 2.4.10), > > > but my (admittedly feeble) attempts to get it fixed were not accepted. > > > At one point I thought a fix went into 2.4.18-pre[12] or so, but I > > > guess not. I haven't tried in a while, so maybe I should make another > > > attempt. > > > > > > > Was that part of the 2.4.10-pre11 -aa VM merge, or was it from another > > seperate patch? > > Well, at the same time as Linus merged -aa VM, he also merged > blockdev-in-pagecache from -aa. This caused this problem, among others. Ahh yes, I remember now. > With blockdev-in-pagecache, the kernel thinks block device access is the > same as reading a file, so it imposes file limits. It also caused the Right. > problem that the block device (pagecache) and the filesystem (buffer > cache) were not coherent, causing e2fsck, tune2fs, etc to not work. > This was fixed in 2.4.12 I believe. I also heard one offhand remark that similar problems have crept back into the kernel recently. Is that true? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 12:25 [W:0.187 / U:0.010 seconds] ©2003-2008 Jasper Spaans | |||||||||||||