From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs convert running out of space
Date: Fri, 23 Jan 2015 08:46:23 +0000 (UTC) [thread overview]
Message-ID: <pan$40d11$63f07406$84874b72$fbf45436@cox.net> (raw)
In-Reply-To: 20150123085441.79265c9a@marcec.fritz.box
Marc Joliet posted on Fri, 23 Jan 2015 08:54:41 +0100 as excerpted:
> Am Fri, 23 Jan 2015 04:34:19 +0000 (UTC)
> schrieb Duncan <1i5t5.duncan@cox.net>:
>
>> Gareth Pye posted on Fri, 23 Jan 2015 08:58:08 +1100 as excerpted:
>>
>> > What are the chances that splitting all the large files up into sub
>> > gig pieces, finish convert, then recombine them all will work?
>>
> [...]
>> Option 2: Since new files should be created using the desired target
>> mode (raid1 IIRC), you may actually be able to move them off and
>> immediately back on, so they appear as new files and thus get created
>> in the desired mode.
>
> With current coreutils, wouldn't that also work if he moves the files to
> another (temporary) subvolume? (And with future coreutils, by copying
> the files without using reflinks and then removing the originals.)
If done correctly, yes.
However, "off the filesystem" is far simpler to explain over email or the
like, and is much less ambiguous in terms of "OK, but did you do it
'correctly'" if it doesn't end up helping. If it doesn't work, it
doesn't work. If "move to a different subvolume under specific
conditions in terms of reflinking and the like" doesn't work, there's
always the question of whether it /really/ didn't work, or if somehow the
instructions weren't clear enough and thus failure was simply the result
of a failure to fully meet the technical requirements.
Of course if I was doing it myself, and if I was absolutely sure of the
technical details in terms of what command I had to use to be /sure/ it
didn't simply reflink and thus defeat the whole exercise, I'd likely use
the shortcut. But in reality, if it didn't work I'd be second-guessing
myself and would probably move everything entirely off and back on to be
sure, and knowing that, I'd probably do it the /sure/ way in the first
place, avoiding the chance of having to redo it to prove to myself that
I'd done it correctly.
Of course, having demonstrated to myself that it worked, if I ever had
the problem again, I might try the shortcut, just to demonstrate to my
own satisfaction the full theory that the effect of the shortcut was the
same as the effect of doing it the longer and more fool-proof way. But
of course I'd rather not have the opportunity to try that second-half
proof. =:^)
Make sense? =:^)
--
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-23 8:46 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 [this message]
2015-01-25 15:23 ` Marc Joliet
2015-01-27 3:24 ` Gareth Pye
2015-01-27 6:20 ` Duncan
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$40d11$63f07406$84874b72$fbf45436@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).