From: Hugo Mills <hugo@carfax.org.uk>
To: Russell Coker <russell@coker.com.au>
Cc: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs hangs 3.19-10
Date: Sat, 4 Apr 2015 13:00:47 +0000 [thread overview]
Message-ID: <20150404130047.GC13864@carfax.org.uk> (raw)
In-Reply-To: <201504041255.08052.russell@coker.com.au>
[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]
On Sat, Apr 04, 2015 at 12:55:08PM +0000, Russell Coker wrote:
> On Fri, 3 Apr 2015 05:14:12 AM Duncan wrote:
> > Well, btrfs itself isn't really stable yet... Stable series should be
> > stable at least to the extent that whatever you're using in them is, but
> > with btrfs itself not yet entirely stable...
>
> Also for stable operation you want both forward and backward compatability.
> You could make an Ext3 filesystem and expect that any random ancient Linux box
> you are likely to encounter can read it. Even Ext4 has been supported for a
> long time and most systems you are likely to encounter won't have any problems
> with it.
>
> I recently made a BTRFS filesystem on a Debian/Jessie system (kernel 3.16.7)
> with default options and discovered that Debian/Wheezy (kernel 3.2.65) can't
> read it. I think that one criteria for "stable" in a filesystem is that
> kernels from a couple of previous releases can mount it. By that criteria
> BTRFS won't be "stable" for use in Debian for about 4 years.
>
> As an aside are there options to mkfs.btrfs that would make a filesystem
> mountable by kernel 3.2.65? If so I'll file a Debian/Jessie bug report
> requesting that a specific mention be added to the man page.
Yes, there are. It's probably -O^extref, but if you can show the
dmesg output from the 3.2 kernel on the failed mount (so that it shows
what the actual failure was), we should be able to give you a more
precise answer.
Hugo.
--
Hugo Mills | Welcome to Hollywood, a land just off the coast of
hugo@... carfax.org.uk | Planet Earth
http://carfax.org.uk/ |
PGP: 65E74AC0 | The Cat's Meow
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-04-04 13:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 11:38 Btrfs hangs 3.19-10 Timofey Titovets
2015-04-02 11:46 ` Hugo Mills
2015-04-02 11:47 ` Timofey Titovets
2015-04-02 14:13 ` Roman Mamedov
2015-04-03 5:14 ` Duncan
2015-04-04 12:55 ` Russell Coker
2015-04-04 13:00 ` Hugo Mills [this message]
2015-04-05 3:16 ` Duncan
2015-04-05 3:30 ` Russell Coker
2015-04-05 10:04 ` Hugo Mills
2015-04-06 3:21 ` Duncan
2015-04-06 8:39 ` Russell Coker
2015-04-06 7:40 ` Pavel Volkov
2015-04-06 8:37 ` Russell Coker
2015-04-06 9:20 ` Duncan
2015-04-06 9:29 ` Duncan
2015-04-06 10:13 ` 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=20150404130047.GC13864@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
/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