From: "Bryn M. Reeves" <breeves@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM on SATA/PATA disks
Date: Mon, 14 May 2007 09:38:07 +0100 [thread overview]
Message-ID: <46481FEF.802@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0705131307080.6567-100000@bmsred.bmsi.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stuart D. Gathman wrote:
> If out of order writes are enabled, then your server should hold power
> to the disk drives for part of a second after disabling further writes
> in software. LVM is a low risk because LVM changes are comparatively
> rare, and the modification window is small. But, theoretically, if
> you lost power right at the instant you pressed return on lvcreate,
> lvextend, or lvremove, on a system with busy disk io, you could corrupt
> the LVM metadata.
LVM metadata I/O does not pass through device-mapper unless you are
stacking volume groups so I'm not sure how your comment regarding
barriers is relevant here. It's also only going to affect devices under
snapshot and multipath mappings.
How does this differ from updating an MSDOS or GPT partition table, for
example?
Kind regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGSB/v6YSQoMYUY94RAubIAJ4vcB/tqherGhmW/M6n1wcO5KGungCffw1w
ISfLoRVk6CP3EryIzHTolXA=
=g18w
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-05-14 8:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 21:42 [linux-lvm] LVM on SATA/PATA disks Bertrand Renuart
2007-05-13 1:12 ` Stuart D. Gathman
2007-05-13 1:23 ` Brian J. Murrell
2007-05-13 1:34 ` Stuart D. Gathman
2007-05-13 2:06 ` David Brown
2007-05-13 16:46 ` Les Mikesell
2007-05-13 17:24 ` Stuart D. Gathman
2007-05-14 8:38 ` Bryn M. Reeves [this message]
2007-05-14 8:30 ` Bryn M. Reeves
2007-05-14 15:24 ` David Brown
2007-05-15 14:35 ` Bryn M. Reeves
2007-05-13 20:25 ` Bertrand Renuart
2007-05-14 14:53 ` Stuart D. Gathman
2007-05-14 14:59 ` Daniel Davidson
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=46481FEF.802@redhat.com \
--to=breeves@redhat.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).