From: Stephane Chazelas <stephane_chazelas@yahoo.fr>
To: Chris Mason <chris.mason@oracle.com>
Cc: cwillu <cwillu@cwillu.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Memory leak?
Date: Fri, 8 Jul 2011 21:04:12 +0100 [thread overview]
Message-ID: <20110708200412.GG4284@yahoo.fr> (raw)
In-Reply-To: <1310141349-sup-9515@shiny>
2011-07-08 12:15:08 -0400, Chris Mason:
[...]
> I'd definitely try without -o compress_force.
[...]
Just started that over the night.
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!?
--dsk/sda-- --dsk/sdb-- --dsk/sdc-- --dsk/sdd--
read writ: read writ: read writ: read writ
1000k 0 : 580k 0 :2176k 0 : 0 0
1192k 0 : 76k 0 : 988k 0 : 0 0
436k 0 : 364k 0 :1984k 0 : 0 33M
824k 0 : 812k 0 :4276k 0 : 0 0
3004k 0 :2868k 0 :5488k 0 : 0 0
796k 564k: 640k 25M:2284k 4600k: 0 0
108k 0 : 68k 23M: 648k 35M: 0 0
1712k 12k:1644k 12k:2476k 7864k: 0 0
732k 0 : 620k 0 :3192k 0 : 0 0
1148k 0 :1116k 0 :3532k 0 : 0 19M
1392k 0 :1380k 0 :4416k 0 : 0 7056k
1336k 0 :1212k 0 :6664k 0 : 0 3148k
820k 0 : 784k 0 :4528k 0 : 0 48M
1336k 0 :1340k 0 :3964k 0 : 0 8996k
1528k 0 :1280k 0 :2908k 0 : 0 0
1352k 0 :1216k 0 :3880k 0 : 0 0
864k 0 : 888k 0 :1684k 0 : 0 0
1268k 0 :1208k 0 :3072k 0 : 0 0
(source FS is on sda4+sdb+sdc, target on sdd, sda alsa has an
ext4 FS)
How can that be? Some garbage collection, background defrag or
something like that? But then, if I stop the rsync, those writes
stop as well.
--
Stephane
next prev parent reply other threads:[~2011-07-08 20:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 19:09 Memory leak? Stephane Chazelas
2011-07-03 19:38 ` cwillu
2011-07-06 8:11 ` Stephane Chazelas
2011-07-07 8:09 ` Stephane Chazelas
2011-07-07 8:20 ` Li Zefan
2011-07-07 8:37 ` Stephane Chazelas
2011-07-08 12:44 ` Stephane Chazelas
2011-07-08 15:06 ` Chris Mason
2011-07-08 15:41 ` Stephane Chazelas
2011-07-08 16:11 ` Stephane Chazelas
2011-07-08 16:17 ` Chris Mason
2011-07-08 16:57 ` Stephane Chazelas
2011-07-09 17:11 ` Stephane Chazelas
2011-07-08 16:15 ` Chris Mason
2011-07-08 17:06 ` Stephane Chazelas
2011-07-08 20:04 ` Stephane Chazelas [this message]
2011-07-08 20:12 ` Chris Mason
2011-07-09 7:09 ` Stephane Chazelas
2011-07-09 7:42 ` A lot of writing to FS only read (Was: Memory leak?) Stephane Chazelas
2011-07-10 5:58 ` Memory leak? Stephane Chazelas
2011-07-09 17:09 ` Stephane Chazelas
2011-07-09 19:25 ` cwillu
2011-07-09 20:36 ` Stephane Chazelas
2011-07-10 12:44 ` Chris Mason
2011-07-10 18:37 ` Stephane Chazelas
2011-07-11 9:01 ` Stephane Chazelas
2011-07-11 15:00 ` Chris Mason
2011-07-11 15:35 ` Stephane Chazelas
2011-07-11 16:25 ` Chris Mason
2011-07-11 16:34 ` Stephane Chazelas
2011-07-12 11:40 ` Stephane Chazelas
2011-07-16 12:12 ` write(2) taking 4s. (Was: Memory leak?) Stephane Chazelas
2011-07-16 16:22 ` Stephane Chazelas
2011-07-17 9:17 ` Stephane Chazelas
2011-07-18 10:39 ` write(2) taking 4s Stephane Chazelas
2011-07-18 19:37 ` Stephane Chazelas
2011-07-19 9:32 ` Stephane Chazelas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110708200412.GG4284@yahoo.fr \
--to=stephane_chazelas@yahoo.fr \
--cc=chris.mason@oracle.com \
--cc=cwillu@cwillu.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).