linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Moving btrfs fs disk between computers
Date: Sat, 19 Aug 2017 05:21:13 +0000 (UTC)	[thread overview]
Message-ID: <pan$3f6ee$469dad4a$bd79d02d$56f8cf2@cox.net> (raw)
In-Reply-To: 20170819023526.wbhl2wydq4bw6u75@angband.pl

Adam Borowski posted on Sat, 19 Aug 2017 04:35:26 +0200 as excerpted:

> On Fri, Aug 18, 2017 at 11:09:22PM -0300, Hérikz Nawarro wrote:
>> Hello everyone,
>> 
>> Can i create a btrfs fs in a machine and move the disk to another
>> machine like a ext4 or ntfs?
> 
> Yeah, no problem whatsoever, even for multi-device filesystems.
> Btrfs doesn't care about what devices it is on.
> 
> There has been no new incompat features in quite a while, so old kernels
> shouldn't be an issue either.
> 
> I think the only way for valid btrfs to be unmountable on another
> machine with a modern kernel is to mess with page size, which is AFAIK
> not even possible on x86.

IOW, as long as the two machines are the same arch, or more precisely, 
have the same page size if different archs, it should be fine as long as 
you're not running a really old kernel on one of them.

But don't try mounting a filesystem created on x86_64 on something exotic 
like sparc or ppc or something.  If the two archs' page sizes are the 
same it should work, but I'd still be sure I had an extra set of backups 
before I tried something like that.

-- 
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


      reply	other threads:[~2017-08-19  5:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19  2:09 Moving btrfs fs disk between computers Hérikz Nawarro
2017-08-19  2:35 ` Adam Borowski
2017-08-19  5:21   ` Duncan [this message]

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$3f6ee$469dad4a$bd79d02d$56f8cf2@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).