From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Regression in: [PATCH 4/4] btrfs: qgroup: account shared subtree during snapshot delete
Date: Sun, 1 Nov 2015 22:57:22 +0000 (UTC) [thread overview]
Message-ID: <pan$5a6ef$2dd4598a$565dd5ea$17edba05@cox.net> (raw)
In-Reply-To: 56367AE8.9030509@profihost.ag
Stefan Priebe posted on Sun, 01 Nov 2015 21:49:44 +0100 as excerpted:
> this one: http://www.spinics.net/lists/linux-btrfs/msg47377.html
>
> adds a regression to my test systems with very large disks (30tb and
> 50tb).
>
> btrfs balance is super slow afterwards while heavily making use of cp
> --reflink=always on big files (200gb - 500gb).
>
> Sorry didn't know how to correctly reply to that "old" message.
Just on the message-reply bit...
Gmane.org carries this list (among many), archiving the posts with both
nntp/news and http/web interfaces. Both the web and news interfaces
normally allow replies to both old and current messages via the gmane
gateway forwarding to the list, tho the first time you reply to a list
via gmane, it'll respond with a confirmation to the email address you
used, requiring you to reply to that before forwarding the mail on to the
list. If you don't reply within a week, the message is dropped.
However, at least for the news interface (not sure about the web
interface), you only have to confirm for a particular list/newsgroup
once, after that, it forwards to the list without further confirmations.
That's how I follow all my lists, reading and replying to them as
newsgroups via the gmane list2news interface.
http://gmane.org for more info.
The one caveat is that while on a lot of lists replies to the list only
is the norm, on the Linux kernel and vger.kernel.org hosted lists
(including this one), replying to all, list and previous posters, is the
norm, and I'm not sure if the web interface allows that. On the news
interface it of course depends on your news client -- mine is more
adapted to news than mail, and while it allows forwarding to your normal
mail client for the mail side, normal followups are to news only, and
it's not easy to reply to all, so I generally reply to list (as
newsgroup) only, unless a poster specifically requests to be CCed on
replies.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-11-01 22:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 20:49 Regression in: [PATCH 4/4] btrfs: qgroup: account shared subtree during snapshot delete Stefan Priebe
2015-11-01 22:57 ` Duncan [this message]
2015-11-02 1:34 ` Qu Wenruo
2015-11-02 5:46 ` Stefan Priebe
2015-11-03 19:15 ` Mark Fasheh
2015-11-03 19:26 ` Mark Fasheh
2015-11-03 19:42 ` Stefan Priebe
2015-11-03 23:31 ` Mark Fasheh
2015-11-04 2:22 ` Chris Mason
2015-11-04 1:01 ` Qu Wenruo
2015-11-05 19:23 ` Mark Fasheh
2015-11-06 1:02 ` Qu Wenruo
2015-11-06 3:15 ` Mark Fasheh
2015-11-06 3:25 ` Qu Wenruo
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='pan$5a6ef$2dd4598a$565dd5ea$17edba05@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).