linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Ray Morris <support@bettercgi.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Powerfailure and snapshot consistency
Date: Sat, 26 Mar 2011 02:49:22 -0500	[thread overview]
Message-ID: <20110326024922.19c9382d@bettercgi.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1103260013380.25820@bmsred.bmsi.com>

On Sat, 26 Mar 2011 00:24:56 -0400 (EDT)
"Stuart D. Gathman" <stuart@bmsi.com> wrote:

> Assuming my theory is correct, the morals would be:
...
> 2) make sure important LVs do not span multiple PVs (except for LVM
>     mirroring) - you could be unhappy in the event of a system crash.

   I don't believe that multiple PVs necesarily makes a 
difference. On a single PV, there is no guarantee that 
writes make it to disk during a power failure, what order
they make it in, or even if a write is correct while voltage
is dropping. The drive itself could reorder a write (NCQ), 
the raid card could do so, etc. One might say the moral
of the story is "don't run important production servers 
on spotty power systems without an effective UPS".  

  Someone mentioned journaling. Journaling does not of
course guarantee data consistency, only makes meta data, 
more likely to be consistent, so regardless when you 
undervolt a drive during power failure something is subject
to go wrong, aside from the more obvious effects of even
an instant power cut while writing a block.  Moral - 
don't yank the power is the data is important.
-- 
Ray Morris
support@bettercgi.com

Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/

Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/

Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php

      parent reply	other threads:[~2011-03-26  7:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26  4:24 [linux-lvm] Powerfailure and snapshot consistency Stuart D. Gathman
2011-03-26  4:42 ` Ron Johnson
2011-03-26  4:52   ` Stuart D. Gathman
2011-03-26  5:25     ` Ron Johnson
2011-03-26  5:53       ` hansbkk
2011-03-26 16:07       ` Stuart D. Gathman
2011-03-26 20:30         ` Mike Snitzer
2011-03-27 21:55           ` Stuart D. Gathman
2011-03-28 17:20             ` Phillip Susi
2011-03-28 17:24               ` Stuart D. Gathman
2011-03-28 17:37                 ` Phillip Susi
2011-03-28 21:26                   ` Stuart D. Gathman
2011-03-28 18:34                 ` Mike Snitzer
2011-03-28 17:26         ` Les Mikesell
2011-03-28 17:54           ` Stuart D. Gathman
2011-03-28 19:43             ` Ron Johnson
2011-03-26  7:49 ` Ray Morris [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=20110326024922.19c9382d@bettercgi.com \
    --to=support@bettercgi.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).