archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <>
To: Daniel Pocock <>,
Subject: Re: 64k and 4k page size inter-op?
Date: Mon, 14 Sep 2020 10:06:58 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 14.09.20 г. 1:49 ч., Daniel Pocock wrote:
> I recently ran into trouble moving btrfs volumes between an amd64 host
> (4k page size) and powerpc64el (64k page size)
> As far as I can tell, the only option to ensure compatibility between
> the two hosts is to
> a) recompile the powerpc64el kernel for a 4k page size,
> b) re-format any volumes created with 64k sectorsize so they have 4k instead
> Is there any other reasonable way to proceed?
> Are there any downsides to using the 4k page size on powerpc64el?

There is currently work underway to allow btrfs to work with subpage
blocksizes i.e being able to mount a 4k filesystem on a 64k page
filesystem. Currently you cannot do this so as you correctly deduced -
you'd have to either equalize the page sizes of both systems or wait
until this work lands in upstream.

> Regards,
> Daniel

  reply	other threads:[~2020-09-14  7:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-13 22:49 64k and 4k page size inter-op? Daniel Pocock
2020-09-14  7:06 ` Nikolay Borisov [this message]
2020-09-14  7:19   ` Daniel Pocock

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).