All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <phill@thesusis.net>
To: Luigi Fabio <luigi.fabio@gmail.com>
Cc: Phil Turmel <philip@turmel.org>, linux-raid@vger.kernel.org
Subject: Re: RAID5 failure and consequent ext4 problems
Date: Tue, 13 Sep 2022 08:47:16 -0400	[thread overview]
Message-ID: <87wna7zbe1.fsf@vps.thesusis.net> (raw)
In-Reply-To: <CAJJqR21jhoE5Ot1Vc9qRB10sOCB70dMBsLQkZ71Buy1=kBtvyQ@mail.gmail.com>


Luigi Fabio <luigi.fabio@gmail.com> writes:

> The way I have found it explained in multiple places is that the
> backups only get updated as a consequence of an actual userspace
> interaction. So you have to run fsck or at least change settings in
> tune2fs, for instance, or resize2fs ... then all the backups get
> updated.

Exactly.  Changing the filesystem with tune2fs or resize2fs requires
that all of the backups be updated.

> The jury is still out on whether automated fscks - for those lunatics
> who haven't disabled them - update or not. There is conflicting
> information.

IIRC, a preen ( the automatic fsck at boot ) normally just sees that the
dirty flag is not set ( since the filesystem was cleanly unmounted,
right? ), and doesn't do anything else.  If there was an unclean
shutdown though, and a real fsck is run, then it updates the first
backup.



  reply	other threads:[~2022-09-13 12:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 14:51 RAID5 failure and consequent ext4 problems Luigi Fabio
2022-09-08 17:23 ` Phil Turmel
2022-09-09 20:32   ` Luigi Fabio
2022-09-09 21:01     ` Luigi Fabio
2022-09-09 21:48       ` Phil Turmel
2022-09-09 22:11         ` David T-G
2022-09-09 22:50         ` Luigi Fabio
2022-09-09 23:04           ` Luigi Fabio
2022-09-10  1:29             ` Luigi Fabio
2022-09-10 15:18               ` Phil Turmel
2022-09-10 19:30                 ` Luigi Fabio
2022-09-10 19:55                   ` Luigi Fabio
2022-09-10 20:12                     ` Luigi Fabio
2022-09-10 20:15                       ` Phil Turmel
2022-09-10 20:14                     ` Phil Turmel
2022-09-10 20:17                       ` Phil Turmel
2022-09-10 20:24                         ` Luigi Fabio
2022-09-10 20:54                           ` Luigi Fabio
2022-09-12 19:09                     ` Phillip Susi
2022-09-13  3:58                       ` Luigi Fabio
2022-09-13 12:47                         ` Phillip Susi [this message]
2022-09-12 19:06                 ` Phillip Susi
2022-09-13  4:02                   ` Luigi Fabio
2022-09-13 12:51                     ` Phillip Susi

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=87wna7zbe1.fsf@vps.thesusis.net \
    --to=phill@thesusis.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=luigi.fabio@gmail.com \
    --cc=philip@turmel.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.