From: Roman Mamedov <rm@romanrm.net>
To: Remi Gauvin <remi@georgianit.com>
Cc: Kai Krakow <hurikhan77+btrfs@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: fstab autodegrag with 5.10 & 5.15 kernels, Debian?
Date: Fri, 28 Jan 2022 23:44:30 +0500 [thread overview]
Message-ID: <20220128234430.63f67d20@nvm> (raw)
In-Reply-To: <19bf3e06-3156-99b4-4656-6ac794ad1ca8@georgianit.com>
On Fri, 28 Jan 2022 13:29:22 -0500
Remi Gauvin <remi@georgianit.com> wrote:
> MDraid, and any hardware raid I'm aware of, will resynchronize the 2
> copies whenever there is an unclean shutdown. which copy becomes the
> new master is arbitrary, but both will be the same.
I believe mdraid writes event count to each device, and the device with the
highest event count (which has seen completed writes as late in time prior to
shutdown as possible) will be used as the source for synchronizing the other
ones.
Secondly, it has a write intent bitmap, to only resync the areas that are
different on that chosen device compared to the others.
--
With respect,
Roman
next prev parent reply other threads:[~2022-01-28 18:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 15:25 fstab autodegrag with 5.10 & 5.15 kernels, Debian? piorunz
2022-01-27 21:14 ` Chris Murphy
2022-01-27 22:45 ` Qu Wenruo
2022-01-28 11:55 ` Kai Krakow
2022-01-28 12:14 ` piorunz
2022-01-28 12:42 ` Qu Wenruo
2022-01-29 1:37 ` piorunz
2022-01-28 13:00 ` Qu Wenruo
2022-01-28 15:48 ` Kai Krakow
2022-01-28 16:05 ` Remi Gauvin
2022-01-28 18:01 ` Kai Krakow
2022-01-28 18:09 ` Remi Gauvin
2022-01-28 18:23 ` Kai Krakow
2022-01-28 18:29 ` Remi Gauvin
2022-01-28 18:44 ` Roman Mamedov [this message]
2022-01-28 18:33 ` Remi Gauvin
2022-01-28 22:42 ` Forza
2022-01-28 16:25 ` Remi Gauvin
2022-01-28 18:07 ` Kai Krakow
2022-01-28 18:23 ` Remi Gauvin
2022-01-29 1:33 ` piorunz
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=20220128234430.63f67d20@nvm \
--to=rm@romanrm.net \
--cc=hurikhan77+btrfs@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=remi@georgianit.com \
/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.