From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: weekend of btrfs findings
Date: Wed, 4 Apr 2012 04:52:45 +0000 (UTC) [thread overview]
Message-ID: <pan.2012.04.04.04.52.44@cox.net> (raw)
In-Reply-To: pan.2012.04.04.04.45.23@cox.net
Duncan posted on Wed, 04 Apr 2012 04:45:24 +0000 as excerpted:
> Oh, and one more thing. Because btrfs /is/ experimental, (a) be
> prepared to lose any data you put on it (but by your comments you
> probably understand that bit already), and (b) running current kernels
> is critical, as each one still includes a lot of fixes from the one
> before. That means at *LEAST* 3.2. There's apparently a regression for
> some people in 3.3 but you'd normally be expected to be upgrading to it
> about now, and many testers run the mainline Linus rc kernels (3.4-rc1
> currently), or even newer not-yet-in-linus-tree btrfs. Again, see the
> wiki for more.
... And 3.4-rc1 has a regression too, see the btrfs io erros on 3.4rc1
thread. But that one should be fixed well before 3.4 full release. Of
course if you're testing btrfs, following this list is helpful, and you
can see and apply the patch yourself, or check when Linus applies it in
his tree.
--
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:[~2012-04-04 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 19:11 weekend of btrfs findings Remco Hosman
2012-04-04 4:45 ` Duncan
2012-04-04 4:52 ` Duncan [this message]
2012-04-04 5:04 ` Remco Hosman
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.2012.04.04.04.52.44@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).