All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs hangs 3.19-10
Date: Sat, 4 Apr 2015 12:55:08 +0000	[thread overview]
Message-ID: <201504041255.08052.russell@coker.com.au> (raw)
In-Reply-To: <pan$a9ed6$bb1c7fdd$74534d5d$7b638441@cox.net>

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.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/

  reply	other threads:[~2015-04-04 12:55 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 [this message]
2015-04-04 13:00         ` Hugo Mills
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=201504041255.08052.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.