From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: mount btrfs takes 30 minutes, btrfs check runs out of memory
Date: Fri, 14 Aug 2015 00:30:33 +0000 (UTC) [thread overview]
Message-ID: <pan$9bab3$33004c18$3a12cc04$86d0a7bb@cox.net> (raw)
In-Reply-To: CAJCQCtQ2fK4S_RJRzg3EE+0qu4ipFtDVfshWuxjnF2nzpF8vLA@mail.gmail.com
Chris Murphy posted on Thu, 13 Aug 2015 17:19:41 -0600 as excerpted:
> Well I think others have suggested 3000 snapshots and quite a few things
> will get very slow. But then also you have autodefrag and I forget the
> interaction of this with many snapshots since the snapshot aware defrag
> code was removed.
Autodefrag shouldn't have any snapshots mount-time-related interaction,
with snapshot-aware-defrag disabled. The interaction between defrag
(auto or not) and snapshots will be additional data space usage, since
with snapshot-aware disabled, defrag only works with the current copy,
thus forcing it to COW the extents elsewhere while not freeing the old
extents as they're still referenced by the snapshots, but it shouldn't
affect mount-time.
--
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-08-14 0:30 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ3TwYQXqUZiKhYc5rciTmvGX1RLkHnkQb5SSYAJ7AD+kbudag@mail.gmail.com>
2015-07-31 2:34 ` mount btrfs takes 30 minutes, btrfs check runs out of memory Qu Wenruo
2015-07-31 4:10 ` John Ettedgui
2015-08-02 5:44 ` Georgi Georgiev
[not found] ` <CAJ3TwYRN+1tJY+paz=qZT0_XP=r9CcTKbBgX_kZRFOWj8vSK=w@mail.gmail.com>
2015-07-31 4:52 ` Qu Wenruo
[not found] ` <CAJ3TwYR5g-JhjmGnZUXqLXc7qV1_=AN5_6sj54JQODbtgG9Aag@mail.gmail.com>
2015-07-31 5:40 ` Qu Wenruo
2015-07-31 5:45 ` John Ettedgui
2015-08-01 4:35 ` John Ettedgui
2015-08-01 10:05 ` Russell Coker
2015-08-04 1:39 ` Qu Wenruo
2015-08-04 1:55 ` John Ettedgui
2015-08-04 2:31 ` John Ettedgui
2015-08-04 3:01 ` Qu Wenruo
2015-08-04 4:58 ` John Ettedgui
2015-08-04 6:47 ` Duncan
2015-08-04 11:28 ` Austin S Hemmelgarn
2015-08-04 17:36 ` John Ettedgui
2015-08-05 11:30 ` Austin S Hemmelgarn
2015-08-13 22:38 ` Vincent Olivier
2015-08-13 23:19 ` Chris Murphy
2015-08-14 0:30 ` Duncan [this message]
2015-08-14 2:42 ` Vincent Olivier
2015-08-18 17:36 ` Vincent Olivier
2015-08-14 2:39 ` Vincent Olivier
[not found] ` <CAJ3TwYSW+SvbBrh1u_x+c3HTRx03qSR6BoH5cj_VzCXxZYv6EA@mail.gmail.com>
2016-07-15 3:56 ` Qu Wenruo
[not found] ` <CAJ3TwYRXwDVVfT0TRRiM9dEw-7TvY8qG=WvMYKczZOv6wkFWAQ@mail.gmail.com>
2016-07-15 5:24 ` Qu Wenruo
2016-07-15 6:56 ` Kai Krakow
[not found] ` <CAJ3TwYSTnQfj=qmBLtnmtXQKexMMD4x=9Gk3p3anf4uF+G26kw@mail.gmail.com>
[not found] ` <CAJ3TwYTnMPVwkrZEU-=Q_Nq+9Bn0vM3z+EFC8RP=RTyaufSoqw@mail.gmail.com>
2016-07-18 1:13 ` Qu Wenruo
[not found] ` <CAJ3TwYRpc_R-wVur0T6+Uy_aPVXTGpvp_ag1Ar9K2HoB0H1ySQ@mail.gmail.com>
2016-07-18 8:41 ` Qu Wenruo
[not found] ` <CAJ3TwYRH8JVkuv2Hu7FYb+BSwKGrq1spx079zwOF_FO1y=9NFA@mail.gmail.com>
2016-07-18 9:07 ` Qu Wenruo
2016-07-18 15:31 ` Duncan
[not found] ` <CAJ3TwYS6UTkWf=PNku3RG7hPrXMKz3yhk2WqCRLix4v_VwgrmA@mail.gmail.com>
2016-07-21 8:10 ` Qu Wenruo
[not found] ` <CAJ3TwYQ47SVpbO1Pb-TWjhaTCCpMFFmijwTgmV8=7+1_a6_3Ww@mail.gmail.com>
2016-07-21 8:19 ` Qu Wenruo
2016-07-21 15:47 ` Graham Cobb
2017-04-10 0:52 ` Qu Wenruo
2018-02-13 10:21 ` John Ettedgui
2018-02-13 11:04 ` Qu Wenruo
2018-02-13 11:25 ` John Ettedgui
2018-02-13 11:40 ` Qu Wenruo
2018-02-13 12:06 ` John Ettedgui
2018-02-13 12:46 ` Qu Wenruo
2018-02-13 12:52 ` John Ettedgui
2018-02-13 12:26 ` Holger Hoffstätte
2018-02-13 12:54 ` Qu Wenruo
2018-02-13 16:24 ` Holger Hoffstätte
2018-02-14 0:43 ` Qu Wenruo
2016-07-15 11:29 ` Christian Rohmann
2016-07-16 23:53 ` Qu Wenruo
2016-07-18 13:42 ` Josef Bacik
2016-07-19 0:35 ` Qu Wenruo
2016-07-25 13:01 ` David Sterba
2016-07-25 13:38 ` Josef Bacik
2015-08-04 14:38 ` Chris Murphy
2015-07-29 5:46 Georgi Georgiev
2015-07-29 6:19 ` 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$9bab3$33004c18$3a12cc04$86d0a7bb@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).