From: Ron Johnson <ron.l.johnson@cox.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Powerfailure and snapshot consistency
Date: Mon, 28 Mar 2011 14:43:20 -0500 [thread overview]
Message-ID: <4D90E4D8.4020702@cox.net> (raw)
In-Reply-To: <alpine.LRH.2.00.1103281346250.14152@bmsred.bmsi.com>
On 03/28/2011 12:54 PM, Stuart D. Gathman wrote:
> On Mon, 28 Mar 2011, Les Mikesell wrote:
>
>> On 3/26/2011 11:07 AM, Stuart D. Gathman wrote:
>>>
>> Is there some non-destructive diagnostic that can tell you if a
>> running machine can or can't manage write ordering correctly through
>> all of its software and hardware layers?
>
> http://blog.nirkabel.org/2008/12/07/ext3-write-barriers-and-write-caching/
>
> The above mentions a test program that demonstrates the ext3 weakness.
> You should be able to run it in a test VM, and destroy (virtual power off)
> the VM. When the barrier=1 mount option is turned on, the mapper is
> supposed
> to log a warning if this is not supported at some level. There appear to
> be disks, however, with hardware write caching that do not correct support
> barriers. You must turn off hardware write caching on these models.
>
"Why did our reports sudden take 85 hours to run?"
--
"Neither the wisest constitution nor the wisest laws will secure
the liberty and happiness of a people whose manners are universally
corrupt."
Samuel Adams, essay in The Public Advertiser, 1749
next prev parent reply other threads:[~2011-03-28 19:43 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 [this message]
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=4D90E4D8.4020702@cox.net \
--to=ron.l.johnson@cox.net \
--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).