From: Marc MERLIN <marc@merlins.org>
To: Sylvain Alain <d2racing911@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Question about btrfs snapshot delay and rm -rf delay
Date: Wed, 5 Dec 2012 22:31:51 -0800 [thread overview]
Message-ID: <20121206063151.GC20550@merlins.org> (raw)
In-Reply-To: <CACR_K2s2NXFJfNknzJLLnQGK6=Sz+6Abs8y7kJfxxynUUaF+cA@mail.gmail.com>
On Wed, Dec 05, 2012 at 11:56:27PM -0500, Sylvain Alain wrote:
> Hi everyone, I'm running btrfs since octobre 2012 and I would like to
> understand 2 behavior that I noticed.
>
> 1. When I delete a big directory, sometimes it can hang my box for 1
> minutes or so, it seems that's the btrfs lock my SSD.
Doesn't directly answer your question, but if you don't have discard as a
mount option, you should try that.
Which SSD do you have? Do normal big file writes succeed or hang too?
My guess right now is that you don't have discard, and your drive is doing
very slow garbage collection. I had a Crucial C300 that did just that before
it ate itself and my data a month later.
Also check that your drive does not have a firmware update to remove those
hangs.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2012-12-06 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 4:56 Question about btrfs snapshot delay and rm -rf delay Sylvain Alain
2012-12-06 5:14 ` Rock Lee
2012-12-06 6:31 ` Marc MERLIN [this message]
2012-12-06 12:52 ` Sylvain Alain
2012-12-06 12:59 ` Sander
2012-12-06 18:52 ` Martin Steigerwald
2012-12-06 18:55 ` Martin Steigerwald
2012-12-06 19:37 ` Sander
2012-12-06 18:54 ` Martin Steigerwald
-- strict thread matches above, loose matches on Subject: below --
2012-12-07 13:48 Sylvain Alain
2012-12-08 11:41 ` Martin Steigerwald
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=20121206063151.GC20550@merlins.org \
--to=marc@merlins.org \
--cc=d2racing911@gmail.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).