From: Les Mikesell <lesmikesell@gmail.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Powerfailure and snapshot consistency
Date: Mon, 28 Mar 2011 12:26:10 -0500 [thread overview]
Message-ID: <4D90C4B2.6020902@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1103261143510.28300@bmsred.bmsi.com>
On 3/26/2011 11:07 AM, Stuart D. Gathman wrote:
>
> It is not a bug. Some progress can be made with barriers (similar to
> fsync())
> that block until all affected blocks are confirmed written on all devices
> through all levels of the storage stack (e.g. written to all legs
> of a raid1 device). My database does an fsync after each journal batch,
> and I think it reasonable to hope that this guarantees that the writes
> from the journal batch complete before any subsequent writes. I don't
> depend on any other ordering.
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?
--
Les Mikesell
lesmikesell@gmail.com
next prev parent reply other threads:[~2011-03-28 17:26 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 [this message]
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=4D90C4B2.6020902@gmail.com \
--to=lesmikesell@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.