From: Hugo Mills <hugo@carfax.org.uk>
To: Steve Keller <keller.steve@gmx.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: State of BTRFS
Date: Thu, 26 Nov 2020 18:18:07 +0000 [thread overview]
Message-ID: <20201126181807.GC1908@savella.carfax.org.uk> (raw)
In-Reply-To: <trinity-ca02807b-66c1-46e7-a4ed-efa79636413b-1606411979151@3c-app-gmx-bs37>
On Thu, Nov 26, 2020 at 06:32:59PM +0100, Steve Keller wrote:
> What is the state of btrfs concerning stability and reliability?
>
> Is it safe to my /home file system on btrfs? I need no RAID,
> currently, as I have mdraid with LVM on top of that already, and I
> have an LVM volume for /home. But I do like snapshots and would
> probably use them quite a lot.
>
> Currently, I have ext4 for /home but I consider switching to btrfs.
> But I want to be really sure not to loose data or otherwise have
> to repair the file system.
In general, it's in pretty good shape. Avoid parity RAID
(especially for metadata), and qgroups. Other than that, the FS itself
should be good.
The main concern these days is broken hardware: Disks that have
poor cache behaviour in the face of power failure, or that simply lie
about stuff having reached permanent storage, or have other serious
firmware bugs. These can lead to the (generally unrecoverable) transid
error state (see the FAQ [1] for a detailed explanation).
Hugo.
[1] https://btrfs.wiki.kernel.org/index.php/FAQ#What_does_.22parent_transid_verify_failed.22_mean.3F
--
Hugo Mills | Do not meddle in the affairs of system
hugo@... carfax.org.uk | administrators, for they are subtle, and quick to
http://carfax.org.uk/ | anger.
PGP: E2AB1DE4 |
prev parent reply other threads:[~2020-11-26 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 17:32 State of BTRFS Steve Keller
2020-11-26 17:55 ` A L
2020-11-26 18:18 ` Hugo Mills [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=20201126181807.GC1908@savella.carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=keller.steve@gmx.de \
--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