On Friday January 27, askernel2615@xxxxxxxxx wrote: > > On Fri, 27 Jan 2006, Chase Venters wrote: > > > After dealing with this leak for a while, I decided to do some dancing around > > with git bisect. I've landed on a possible point of regression: > > > > commit: a9701a30470856408d08657eb1bd7ae29a146190 > > [PATCH] md: support BIO_RW_BARRIER for md/raid1 > > I can confirm that it only leaks with raid! > > I rebooted with my raid5 root, read only, and it didn't leak. As soon as I > remount,rw it started leaking. Go back to ro and it stopped (although it > didn't clean up the old leaks). Tried my raid1 /boot and same thing - rw > leaks, ro doesn't. But, it only leaks on activity. > > I then tried a regular lvm mount (with root ro), and no leaks! It might be interesting, but probably not particularly helpful, to create an ext3 filesystem on this device and mount it with the barrier=1 mount option. That should send BIO_RW_BARRIER requests to the device just line md does. NeilBrown - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
