From: boris <6401e46d@opayq.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Snapshots slowing system
Date: Fri, 11 Mar 2016 23:38:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20160312T002538-774@post.gmane.org> (raw)
In-Reply-To: 56E324AD.6010002@petezilla.co.uk
I wondered whether you had elimated fragmentation, or any other known gotchas,
as a cause?
Out of curiosity, what is/was the utilisation of the disk? Were the snapshots
read-only or read-write?
Apropos Nada: quick shout out to Qu to wish him luck for the 4.6 merge.
[Also, damn you autocorrection on my phone!]
next prev parent reply other threads:[~2016-03-11 23:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 20:03 Snapshots slowing system Pete
2016-03-11 23:38 ` boris [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-12 13:01 pete
2016-03-13 3:28 ` Duncan
2016-03-14 23:03 pete
2016-03-15 15:52 ` Duncan
2016-03-15 22:29 ` Peter Chant
2016-03-16 11:39 ` Austin S. Hemmelgarn
2016-03-17 21:08 ` Pete
2016-03-18 9:17 ` Duncan
2016-03-18 11:38 ` Austin S. Hemmelgarn
2016-03-18 17:58 ` Pete
2016-03-18 23:58 ` Duncan
2016-03-18 18:16 ` Pete
2016-03-18 18:54 ` Austin S. Hemmelgarn
2016-03-19 0:59 ` Duncan
2016-03-19 1:15 ` Duncan
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.20160312T002538-774@post.gmane.org \
--to=6401e46d@opayq.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).