From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs hangs 3.19-10
Date: Fri, 3 Apr 2015 05:14:12 +0000 (UTC) [thread overview]
Message-ID: <pan$a9ed6$bb1c7fdd$74534d5d$7b638441@cox.net> (raw)
In-Reply-To: 20150402191312.1ee31af3@natsu
Roman Mamedov posted on Thu, 02 Apr 2015 19:13:12 +0500 as excerpted:
> Yeah I believe I just hit that in 3.14.37, system unbootable (locks up
> at "Scanning for Btrfs filesystems"), resulted in a many hour downtime
> as it was a remote system w/o IPMI. Fine after a reboot to 3.14.34. Too
> bad that even staying on the "stable" series kernel can back-stab you
> like that from time to time.
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...
If your goal is full stability, something that has been demonstrated
mature, stable, and problem free for some period (say six months if
you're edgy, a year if you're moderate, at least two years if you're
conservative), is still a far better choice. Given existing problems
even now, even if 4.0 btrfs proves entirely stable, btrfs won't have that
demonstrated history at least until the end of whatever length of period
you consider appropriate, because that couldn't start until 4.0's
release, which is still in the future.
--
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:[~2015-04-03 5:14 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 [this message]
2015-04-04 12:55 ` Russell Coker
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='pan$a9ed6$bb1c7fdd$74534d5d$7b638441@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