All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Reindl Harald <h.reindl@thelounge.net>
Cc: Wols Lists <antlists@youngman.org.uk>,
	commentsabout@riseup.net, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Encrypted software RAID1 with Debian Stretch
Date: Wed, 13 Sep 2017 14:52:22 +0100	[thread overview]
Message-ID: <87377qvh7t.fsf@esperi.org.uk> (raw)
In-Reply-To: <3a85ea27-602a-3f5b-3537-d4159a56c2ed@thelounge.net> (Reindl Harald's message of "Wed, 13 Sep 2017 03:34:21 +0200")

On 13 Sep 2017, Reindl Harald uttered the following:

> Am 13.09.2017 um 01:30 schrieb Nix:
>> ext2 is probably too old (it's not maintained much any more)
>
> sorry, but when you are talking about betrayed filesystems above and
> then take ext2, a non journaled filesystem which takes ages for fsck,

On slow links like USB2, the overhead of throwing heaps of metadata into
the journal across such a slow link often dominates any overhead from
fsck, particularly if the filesystem is usually unmounted (as is often
also true of backup filesystems) so is unlikely to benefit from a
journal anyway. Of course this depends on the backup model. bup doesn't
trigger many metadata updates (a few huge files): the late lamented
obnam and rdiff-backup trigger lots.

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.

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!)

> in your mouth....

Oh yes, it's Reindl, destroyer of mailing list civility everywhere. How
wonderful it isn't to find you here.

I can't even tell what 'in your mouth' *means* in this context, but I'm
fairly sure it's meant to be offensive, simply because *everything* you
say is meant that way. Are you arguing that ext2 is well-maintained,
and thus should be used, or that it is unjournalled and thus should not
be used, or that it is unjournalled and thus less reliable, or that fsck
is slow and therefore the filesystem is unreliable?

God knows, and I'll never find out... because you are going back in my
otherwise-empty killfile. However *did* you get out? (Probably it
happened after you became the first person in the history of the
spamassassin list to go into a moderation queue.)

I encourage everyone else who's had enough of Reindl to killfile him as
well. 80% of what he says is wrong, spoken in tones of great authority,
but thankfully he undermines his misinformation by being so thoroughly
unpleasant that nobody wants to follow his instructions. The real
problem is that he's just as viciously nasty to newbies seeking help,
and they won't know to killfile him...

  reply	other threads:[~2017-09-13 13:52 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 [this message]
2017-09-13 16:10         ` Wols Lists
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=87377qvh7t.fsf@esperi.org.uk \
    --to=nix@esperi.org.uk \
    --cc=antlists@youngman.org.uk \
    --cc=commentsabout@riseup.net \
    --cc=h.reindl@thelounge.net \
    --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.