linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: "Stuart D. Gathman" <stuart@bmsi.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Powerfailure and snapshot consistency
Date: Mon, 28 Mar 2011 13:37:30 -0400	[thread overview]
Message-ID: <4D90C75A.2090203@cfl.rr.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1103281319240.13964@bmsred.bmsi.com>

On 3/28/2011 1:24 PM, Stuart D. Gathman wrote:
> Ah, thank you!  Yes, I am using ext3 with EL5.5 defaults, and will now
> learn
> about the barrier option.  Seems like a good thing to turn on when "replace
> battery" comes up on the ups.
> 
> It sounds like dumb luck/divine mercy that the raid 1 PV on which the
> production LV resides did not have a similar issue.

It actually should be on all the time, which is why it defaults to on in
ext4.  A UPS doesn't help if the kernel crashes or some hardware fails.
 I have no idea why incidents like this are not common place with ext3
since it is inherently unsafe without barriers, whether you are using
lvm or mdadm or not.

  reply	other threads:[~2011-03-28 17:33 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 [this message]
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

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=4D90C75A.2090203@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=linux-lvm@redhat.com \
    --cc=stuart@bmsi.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).