From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs filesystem read only on error
Date: Sat, 14 Jun 2014 03:07:56 +0000 (UTC) [thread overview]
Message-ID: <pan$c592e$bc1a92a7$ef735cdd$fc66f65b@cox.net> (raw)
In-Reply-To: CA+3u+RfJQ07aci3k=PBO33RNjWzNx6iBZdKaVJ+gGyU44-VrTQ@mail.gmail.com
David Bloquel posted on Fri, 13 Jun 2014 12:51:32 +0200 as excerpted:
> Informations about my system:
> Linux nas1 3.12-0.bpo.1-amd64 #1 SMP Debian 3.12.9-1~bpo70+1
> (2014-02-07)
> x86_64 GNU/Linux brtfs version:
> Btrfs v0.19
Yikes, that's old! Particularly the 0.19 btrfs-progs, tho there have
been a lot of kernel btrfs fixes since the 3.12 series as well, not all
of which will have been backported.
Due to the rate of fixes going into btrfs, users are strongly recommended
to keep up with current stable kernels, now 3.15, and not get /too/ far
behind on btrfs-progs either.
I'm actually a bit behind myself ATM as I've been focused on other
things, kernel from git but not rebuild since 3.14, and btrfs-progs from
git at v3.14.2. I'd recommend kernel 3.14 if not 3.15, and a btrfs-progs
no older than 3.12. I think there are some snapshotting fixes in kernel
3.15 so you'll probably want that given the snapshotting you report
doing. (I do little snapshotting and 3.14 has been pretty stable for me,
the reason I've let myself get a bit behind, what with other things I
have been doing.)
--
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
prev parent reply other threads:[~2014-06-14 3:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 10:51 Btrfs filesystem read only on error David Bloquel
2014-06-14 3:07 ` Duncan [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='pan$c592e$bc1a92a7$ef735cdd$fc66f65b@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).