From: Chuck Ebbert <cebbert.lkml@gmail.com>
To: Jason Vas Dias <jason.vas.dias@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: mount BTRFS filesystems created with 3.8+ under 2.6.32 kernels ?
Date: Thu, 25 Sep 2014 01:07:09 -0500 [thread overview]
Message-ID: <20140925010709.56113e17@as> (raw)
In-Reply-To: <CALyZvKyHQVeEZ+r3qRLXx15AXnj0-8hqfD4FNxHmQrMtygmpJg@mail.gmail.com>
On Mon, 22 Sep 2014 19:07:39 +0100
Jason Vas Dias <jason.vas.dias@gmail.com> wrote:
> Of course the solution was to have created the filesystem in the first
> place with
> 'mkfs.btrfs -O ^extref' . Found this after some more googling ...
> Shouldn't this be the default ?
Even worse, your vendor might change the default, like Red Hat did in
RHEL 7. ext4 filesystems created by the installer, even very small ones,
get the 64bit feature enabled and can't be mounted in RHEL 6.5.
prev parent reply other threads:[~2014-09-25 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 16:44 mount BTRFS filesystems created with 3.8+ under 2.6.32 kernels ? Jason Vas Dias
2014-09-22 18:07 ` Jason Vas Dias
2014-09-25 6:07 ` Chuck Ebbert [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=20140925010709.56113e17@as \
--to=cebbert.lkml@gmail.com \
--cc=jason.vas.dias@gmail.com \
--cc=linux-kernel@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