linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Nix <nix@esperi.org.uk>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Encrypted software RAID1 with Debian Stretch
Date: Wed, 13 Sep 2017 17:10:57 +0100	[thread overview]
Message-ID: <59B95891.9040809@youngman.org.uk> (raw)
In-Reply-To: <87377qvh7t.fsf@esperi.org.uk>

On 13/09/17 14:52, Nix wrote:
> Nonetheless, fs/ext2 is almost unmaintained these days, and bugs are
> slowly creeping back in. fs/ext4 can take up its duties perfectly well
> these days, reading and writing both ext4-sans-journal and traditional
> ext2 filesystems perfectly well.

ext2 as filesystem code in linux no longer exists. Likewise, I believe,
ext3. Both have been dropped and deleted. The only supported/maintained
ext driver now is ext4, which has backwards compatibility with 3 and 2.

Much like XFS I gather, which although nominally a single filesystem, is
actually full of compatibility code for earlier, incompatible variants.
> 
> One person having no problems with a filesystem as new as btrfs does not
> mean the filesystem is reliable enough to use for backup. The
> reliability bar for such filesystems is far higher than that for fses in
> daily use! ("The required-feature bar is often also much lower. All they
> have to do is store stuff that rarely changes and not lose it!")

"The required-feature bar is often also much lower. All they
have to do is store stuff that rarely changes and not lose it!"

Actually, btrfs is very good at that! PROVIDED you don't use the fancy
new experimental features (like raid :-) in btrfs, it works very well.
It's a nice, stable, very decent filesystem.

The only real bug left in basic functionality is IF you combine
snapshots with a disk full, it can be a disaster. Hence my comments
about monitoring disk space! Seriously, I would be very happy to set my
system up as I suggested and, apart from the learning curve (I'm
currently still on raid-1/ext on my home system, would love to upgrade
but can't afford it), I would be only to happy to entrust my backup to
btrfs.

The rule is simple - don't abuse your tools, and btrfs - USED WITHIN ITS
LIMITATIONS - is a powerful and reliable file system.

Cheers,
Wol

  reply	other threads:[~2017-09-13 16:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 23:58 Encrypted software RAID1 with Debian Stretch commentsabout
2017-09-01  9:46 ` Wols Lists
2017-09-12 23:30   ` Nix
2017-09-13  1:34     ` Reindl Harald
2017-09-13 13:52       ` Nix
2017-09-13 16:10         ` Wols Lists [this message]
2017-09-14 11:08           ` Nix
2017-09-14 12:01             ` Wols Lists
2017-09-14 13:08               ` Nix
2017-09-14 13:39                 ` Roman Mamedov
2017-09-14 15:02                   ` Nix
2017-09-14 16:22                     ` Roman Mamedov
2017-09-15 11:35                       ` Nix
2017-09-14 17:01                     ` Reindl Harald
2017-09-14 16:56                 ` Wols Lists
2017-09-15 11:38                   ` Nix

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=59B95891.9040809@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=nix@esperi.org.uk \
    /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).