From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephane Chazelas Subject: Re: Memory leak? Date: Sun, 10 Jul 2011 06:58:33 +0100 Message-ID: <20110710055833.GA4277@yahoo.fr> References: <20110703190913.GA4474@yahoo.fr> <20110706081111.GA6931@yahoo.fr> <20110708124429.GB4284@yahoo.fr> <1310137241-sup-8158@shiny> <20110708154123.GA17886@yahoo.fr> <1310141349-sup-9515@shiny> <20110708200412.GG4284@yahoo.fr> <1310155908-sup-9183@shiny> <20110709070955.GA4294@yahoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: cwillu , linux-btrfs To: Chris Mason Return-path: In-Reply-To: <20110709070955.GA4294@yahoo.fr> List-ID: 2011-07-09 08:09:55 +0100, Stephane Chazelas: > 2011-07-08 16:12:28 -0400, Chris Mason: > [...] > > > I'm running a "dstat -df" at the same time and I'm seeing > > > substantive amount of disk writes on the disks that hold the > > > source FS (and I'm rsyncing from read-only snapshot subvolumes > > > in case you're thinking of atimes) almost more than onto the > > > drive holding the target FS!? > > > > These are probably atime updates. You can completely disable them with > > mount -o noatime. > [...] > > I don't think it is. First, as I said, I'm rsyncing from > read-only snapshots (and I could see atimes were not updated) > and nothing else is running. Then now looking at the traces this > morning, There was a lot written in the first minutes, then it > calmed down. [...] How embarrassing, sorry In that instance I wasn't rsyncing from the right place, so I was indeed copying non-readonly volumes before copying readonly ones. So, those writes were probably due to atimes. -- Stephane