From: Marc MERLIN <marc@merlins.org>
To: "Miguel Negrão" <miguel.negrao-lists@friendlyvirus.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs tragedy: lack of space for metadata leads to loss of fs.
Date: Tue, 25 Aug 2015 07:59:22 -0700 [thread overview]
Message-ID: <20150825145922.GE20179@merlins.org> (raw)
In-Reply-To: <loom.20150825T151154-787@post.gmane.org>
On Tue, Aug 25, 2015 at 01:44:12PM +0000, Miguel Negrão wrote:
> Hi list,
>
> This weekend had my first btrfs horror story.
>
> system: 3.13.0-49-lowlatency, btrfs-progs v4.1.2
Sorry to say, but that's a very old kernels with many btrfs bugs, some
did lead to corruption.
> A disclaimer: I know 3.13 is very out of date, but I the requirement of
> keeping kernel up to date clashes with my requirement of keeping a stable
> system. At the moment I can't disturb my system as I'm doing important work,
Unfortunately you have conflicting goals.
> upgrading kernel requires upgrading ubuntu, which will upgrade a lot of
> packages and might lead to problems which I don't have time to fix. One
You're doing it wrong :)
Upgrade/compile your own kernel without upgrading the OS.
> block group 32...... flags 36'). This is a OCZ vertex 3, a quite fast SSD.
I've had 5 (yes 5, I replaced my drive 4 times) OCZ Vertex 4 drives, and
they all gave me corruption with btrfs on unclean power down. The last
one didn't work any better, I just gave up and went to Samsung EVO 840
and those have been fine.
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
next prev parent reply other threads:[~2015-08-25 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 13:44 Btrfs tragedy: lack of space for metadata leads to loss of fs Miguel Negrão
2015-08-25 14:00 ` Austin S Hemmelgarn
2015-08-25 14:26 ` Miguel Negrão
2015-08-25 14:53 ` Austin S Hemmelgarn
2015-08-25 14:59 ` Marc MERLIN [this message]
2015-08-25 15:24 ` Miguel Negrão
2015-08-25 15:43 ` Austin S Hemmelgarn
2015-08-25 15:17 ` Matt Ruffalo
2015-08-25 15:53 ` Miguel Negrão
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=20150825145922.GE20179@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=miguel.negrao-lists@friendlyvirus.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 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.