All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Wols Lists <antlists@youngman.org.uk>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Encrypted software RAID1 with Debian Stretch
Date: Thu, 14 Sep 2017 12:08:25 +0100	[thread overview]
Message-ID: <87r2v9sfkm.fsf@esperi.org.uk> (raw)
In-Reply-To: <59B95891.9040809@youngman.org.uk> (Wols Lists's message of "Wed, 13 Sep 2017 17:10:57 +0100")

On 13 Sep 2017, Wols Lists spake thusly:

> 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.

Oh! I failed to notice when that happened :)

... er, I just checked upstream master and ext2 still exists. ext3 was
removed in v4.3.

>> 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.

I lost two btrfses via "it had lots of space, now it's saying -ENOSPC,
and now I can't mount it any more" bugs. Both were rapidly fixed, but
that sort of thing dents your confidence :) mind you that was a couple
of years back and these things do improve with time.

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

Yeah, but... if you avoid the advanced features, why use btrfs? In
particular, why use it *for a backup medium* (where such features are
distinctly less useful than on a non-backup medium)?

-- 
NULL && (void)

  reply	other threads:[~2017-09-14 11:08 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
2017-09-14 11:08           ` Nix [this message]
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=87r2v9sfkm.fsf@esperi.org.uk \
    --to=nix@esperi.org.uk \
    --cc=antlists@youngman.org.uk \
    --cc=linux-raid@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 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.