On Fri, 27 Jan 2006, Ariel 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!
What's interesting is that the mount was ro NOT the md (which can be set ro
independently). So it looks like it only leaks if you write to the md device,
and that's why setting the mount ro stopped the leaks.
Yeah, if the mount is ro, md won't have any reasons to write the
superblock any more, which means it won't be sending out bio's with
barriers any more.
I'm in the middle of a crash course on block IO and SATA, but hopefully
some more skillful devs will beat me to the punch :)
-Ariel
Cheers,
Chase
-
: 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
