All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun He <jhe@cs.wisc.edu>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs -o discard bug in latest dev branches
Date: Wed, 26 Aug 2015 19:09:50 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150826T205442-520@post.gmane.org> (raw)
In-Reply-To: pan$a3d06$a94167e8$2a203b5d$1ff3d7f1@cox.net

Thanks for the info. In the attached reproducer, I don't do sync after running
the workload (but I've tried that before.). Just to be sure, I ran again with
sync and waited for 60 seconds before collecting data. The behavior was the
same. 

Then I tried one more thing, which corrected btrfs behavior. I sync-ed after
each write, which produced the following space-time graph: 

https://gist.githubusercontent.com/junhe/b6ce39eeb6de8887e66a/raw/d31ac85559f83c
d86aef8e4250b3d3d859226c8d/sync-after-each-write.png

Each time a write is finished, the extent of the last write is discarded. 






  reply	other threads:[~2015-08-26 19:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26  4:04 btrfs -o discard bug in latest dev branches Jun He
2015-08-26  6:14 ` Duncan
2015-08-26 19:09   ` Jun He [this message]
2015-08-26 13:24 ` Jeff Mahoney
2015-08-26 16:02   ` Jun He
2015-08-27  3:03     ` Jun He

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=loom.20150826T205442-520@post.gmane.org \
    --to=jhe@cs.wisc.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.