linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Filipe David Manana <fdmanana@gmail.com>
Cc: Paul Harvey <csirac2@gmail.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS corruption w/kernel 3.13 while using docker -s btrfs
Date: Thu, 9 Apr 2015 07:53:35 -0700	[thread overview]
Message-ID: <20150409145335.GS1211@merlins.org> (raw)
In-Reply-To: <CAL3q7H7ovr1Ai54ptt+0qofU_T4TZYG15LT4e2K3zN2VHoDD9w@mail.gmail.com>

Thank you for trying btrfs, it's great for snapshots in docker, but
outside of the 2 helpful comments you already got, do yourself a favour
and use a newer kernel.

Btrfs moves fast, and 3.13 is way too old. The number of bugs (including
corruption bugs) that has been fixed since then is too long to list.

Try getting something newer than 3.16.2 at least, and if you're building
your own, 3.19.3 + this patch
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/42241
(btrfs: simplify insert_orphan_item / 381cf6587f8a8a8e981bc0c1aaaa8859b51dc756 )

Cheers,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

      reply	other threads:[~2015-04-09 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-18  5:28 BTRFS corruption w/kernel 3.13 while using docker -s btrfs Paul Harvey
2015-04-09  8:10 ` Liu Bo
2015-04-09  9:27 ` Filipe David Manana
2015-04-09 14:53   ` Marc MERLIN [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=20150409145335.GS1211@merlins.org \
    --to=marc@merlins.org \
    --cc=csirac2@gmail.com \
    --cc=fdmanana@gmail.com \
    --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).