From: "Péter Sárközi" <xmisterhu@gmail.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Possible bug with concurrent RAID syncs on the same underlying devices
Date: Mon, 12 Apr 2021 21:08:22 +0200 [thread overview]
Message-ID: <CAP1D0fSsNyF=3=R5ZiTNcmU-KhoxDoo6CUibAoRYRmU-00Evpg@mail.gmail.com> (raw)
In-Reply-To: <20210412184742.GH10314@redhat.com>
David Teigland <teigland@redhat.com> ezt írta (időpont: 2021. ápr.
12., H, 20:47):
>
> On Sat, Apr 10, 2021 at 02:32:52AM +0200, Péter Sárközi wrote:
> > Although this is just due to the insane amount of integrity kworker
> > processes, and the system is pretty usable, I think it would be much
> > nicer to only have 1 sync running on the same physical device at a
> > time.
>
> Create one at a time, waiting for integrity init to finish between them
> (sync_percent 100 on each integrity image you see in lvs -a.)
> I have some doubt that the end result will perform well enough given the
> way you're using the partitions.
> Dave
>
That's what I'm doing right now, it would just be much more convenient
to have it set up once and let it finish everything without
interaction.
This is just a home server, so performance isn't critical, but I don't
see why this would perform significantly worse then a whole-disk raid.
I'm planning to use the resulting arrays under 1 filesystem without
striping. So as long as I'm filling it up I will be hitting 1 array at
a time.
After it's filled up from the backup and I'm starting to use it as a
regular filesystem, continuous reads or writes still gonna hit 1 array
at a time most of time so it seems like the same amount of seek and/or
parity calculations as with whole disks.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
prev parent reply other threads:[~2021-04-12 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 0:32 [linux-lvm] Possible bug with concurrent RAID syncs on the same underlying devices Péter Sárközi
2021-04-12 18:47 ` David Teigland
2021-04-12 19:08 ` Péter Sárközi [this message]
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='CAP1D0fSsNyF=3=R5ZiTNcmU-KhoxDoo6CUibAoRYRmU-00Evpg@mail.gmail.com' \
--to=xmisterhu@gmail.com \
--cc=linux-lvm@redhat.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 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).