From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs convert running out of space
Date: Tue, 27 Jan 2015 06:20:45 +0000 (UTC) [thread overview]
Message-ID: <pan$699f3$69a09ae3$223042ab$ffc7f7d1@cox.net> (raw)
In-Reply-To: CA+WRLO_hvAVRXxzrD-1QguZiRJk7tpnnWuZJ-en=X0mBO5GzBQ@mail.gmail.com
Gareth Pye posted on Tue, 27 Jan 2015 14:24:03 +1100 as excerpted:
> Have gone with the move stuff off then finish convert plan. Convert has
> now finished and I'm 60% of the way through moving all the big files
> back on.
>
> Thanks for the help guys.
Glad the big-file-move-off seems to have worked for you, and thanks for
confirming that moving them off did indeed solve your conversion
blockers. Evidently btrfs still has a few rough spots to iron out when
it comes to those big files. =:^(
Please confirm when all big files are moved back on, too, just to be sure
there's nothing unexpected on that side, but based on the conversion-from-
ext* reports, I expect it to be smooth sailing. Btrfs really does have a
problem with large files existing in large enough extents that it can't
really handle them properly, and once they are off the filesystem
temporarily, generally even moved off and back on, it does seem to break
up the log jam (well, in this case huge-extent-jam =:^) and you're back
in business! =:^)
--
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-01-27 6:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 23:45 btrfs convert running out of space Gareth Pye
2015-01-20 0:13 ` Gareth Pye
2015-01-20 5:39 ` Lakshmi_Narayanan_Du
2015-01-20 7:38 ` Chris Murphy
2015-01-20 21:25 ` Gareth Pye
2015-01-20 21:41 ` Chris Murphy
2015-01-20 21:49 ` Gareth Pye
2015-01-20 22:53 ` Chris Murphy
2015-01-20 23:04 ` Gareth Pye
2015-01-21 4:03 ` Chris Murphy
2015-01-22 21:58 ` Gareth Pye
2015-01-22 21:58 ` Gareth Pye
2015-01-23 4:34 ` Duncan
2015-01-23 7:54 ` Marc Joliet
2015-01-23 8:46 ` Duncan
2015-01-25 15:23 ` Marc Joliet
2015-01-27 3:24 ` Gareth Pye
2015-01-27 6:20 ` Duncan [this message]
2015-01-27 21:53 ` Gareth Pye
2015-01-28 0:18 ` Duncan
2015-01-20 23:33 ` Hugo Mills
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$699f3$69a09ae3$223042ab$ffc7f7d1@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).