From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Unable to mount filesystem
Date: Sun, 11 May 2014 02:51:46 +0000 (UTC) [thread overview]
Message-ID: <pan$9ae5$6b264925$51c778dc$642cda8e@cox.net> (raw)
In-Reply-To: 230A0896-9CCD-4B48-A0D2-4BB5932BDEAB@colorremedies.com
Chris Murphy posted on Sat, 10 May 2014 10:49:07 -0600 as excerpted:
> On May 8, 2014, at 7:06 AM, Chris Korent <ckorent@gmail.com> wrote:
>
>> Linux sysresccd 3.10.35-std420-amd64 #2 SMP Wed Apr 2 18:31:51 UTC
>>
>> btrfs --version Btrfs v3.14.1
>
> I'm uncertain if this is an OK combination. I'm under the impression
> that the kernel should be the same or newer version than progs. Also
> kernel 3.10 is old in Btrfs terms. Before altering the file system
> further, I'd try a normal mount with the newest kernel you can get your
> hands on.
In theory it's OK as the progs are supposed to be backward compatible at
least some way (I wouldn't try anything pre-2.6.32 for sure as that was
the last big format change, IIRC, and anything pre-3.5 or so may work but
I'd not suggest it), but... there are of course bugs, and btrfs is still
under intense enough development that there are bugs being fixed every
kernel...
So while yes, in theory the above version spread should work, the
recommendation to try the latest stable-kernel from the latest stable
series 3.14.x is an absolutely solid one, and in fact we're late enough
in the 3.15-rc cycle now that trying with that is ultimately the best bet.
In fact, as the output from mkfs.btrfs suggests, running the latest
stable at the oldest really is recommended, and kernel is a bit more
critical in that regard than btrfs-progs, since the kernel is what
actually handles the filesystem and thus running an old kernel really is
basically uselessly risking your btrfs and the data on it to known and
now fixed bugs.
--
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:[~2014-05-11 2:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 13:06 Unable to mount filesystem Chris Korent
2014-05-10 14:02 ` Marc MERLIN
2014-05-10 16:49 ` Chris Murphy
2014-05-11 2:51 ` Duncan [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-02 18:21 Wictor Lund
2017-07-16 13:55 ` André-Sebastian Liebe
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$9ae5$6b264925$51c778dc$642cda8e@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).