From: Calvin Walton <calvin.walton@kepstin.ca>
To: Roger Binns <rogerb@rogerbinns.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: data DUP
Date: Sat, 27 Apr 2013 17:40:36 -0400 [thread overview]
Message-ID: <1367098836.14073.5.camel@ayu> (raw)
In-Reply-To: <kkv6o8$9f0$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
On Sat, 2013-04-20 at 16:01 -0700, Roger Binns wrote:
> On 20/04/13 14:23, Hugo Mills wrote:
> > You should upgrade anyway -- there's been a number of serious bugs in
> > btrfs fixed since then.
>
> 13.04 is imminent so I'll pick up a newer kernel as part of that anyway.
> (Also Tanglu which I hope to move to intends to use the Ubuntu kernel anyway.)
>
> In any event I am not worried. Bug fixes get backported. The probability
> of hitting any serious bug is low (others would likely be victims first)
> and worst case I have backups (snapshots, other machines, Google/Dropbox,
> DVDs & hard drives at other people's houses etc).
Unfortunately, bugfixes in btrfs have tended to be *not* backported;
aside from a few special cases, btrfs changes only go into new kernel
3.x releases. A few of the Linux distributions that officially support
btrfs (Possibly Oracle, Red Hat, Suse? You would have to contact them
for details...) may be backporting fixes themselves.
As a result, we recommend that btrfs users should generally run whatever
the latest upstream kernel release is - in particular, you should try
the latest kernel before reporting bugs in btrfs.
--
Calvin Walton <calvin.walton@kepstin.ca>
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4027 bytes --]
next prev parent reply other threads:[~2013-04-27 21:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 20:17 data DUP Roger Binns
2013-04-20 20:48 ` Hugo Mills
2013-04-20 21:15 ` Roger Binns
2013-04-20 21:23 ` Hugo Mills
2013-04-20 23:01 ` Roger Binns
2013-04-27 21:40 ` Calvin Walton [this message]
2013-04-27 23:29 ` Roger Binns
2013-04-28 2:53 ` Alex Elsayed
2013-04-28 8:29 ` Roger Binns
2013-04-22 13:37 ` David Sterba
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=1367098836.14073.5.camel@ayu \
--to=calvin.walton@kepstin.ca \
--cc=linux-btrfs@vger.kernel.org \
--cc=rogerb@rogerbinns.com \
/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.