Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751547AbWA0S6H (ORCPT ); Fri, 27 Jan 2006 13:58:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932218AbWA0S6H (ORCPT ); Fri, 27 Jan 2006 13:58:07 -0500 Received: from relay02.pair.com ([209.68.5.16]:49159 "HELO relay02.pair.com") by vger.kernel.org with SMTP id S1751552AbWA0S6F (ORCPT ); Fri, 27 Jan 2006 13:58:05 -0500 X-pair-Authenticated: 67.163.102.102 Date: Fri, 27 Jan 2006 12:58:01 -0600 (CST) From: Chase Venters X-X-Sender: root@turbotaz.ourhouse To: Ariel cc: Chase Venters , linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, akpm@osdl.org, a.titov@host.bg, axboe@suse.de, jamie@audible.transient.net, neilb@suse.de, arjan@infradead.org Subject: Re: More information on scsi_cmd_cache leak... (bisect) In-Reply-To: Message-ID: References: <200601270410.06762.chase.venters@clientec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1516 Lines: 40 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 - 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/