From: Andi Kleen <ak@muc.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 3/5: Device-mapper: snapshots
Date: 2 Jun 2004 21:20:45 +0200
Date: Wed, 2 Jun 2004 21:20:45 +0200 [thread overview]
Message-ID: <20040602192045.GA87771@colin2.muc.de> (raw)
In-Reply-To: <20040602185924.GS6302@agk.surrey.redhat.com>
> > Is this target supposed to be crash safe? What happens when
> > the computer crashes while writing to such a volume?
>
> The intention is for snapshot & origin still to be consistent with each other
> on disk. (No barriers yet, but some synchronous writes.)
So it's supposed to be crash safe?
How about documenting this somewhere in the source?
-Andi
next prev parent reply other threads:[~2004-06-02 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22Gkd-1AX-17@gated-at.bofh.it>
2004-06-02 18:06 ` [PATCH] 3/5: Device-mapper: snapshots Andi Kleen
2004-06-02 18:59 ` Alasdair G Kergon
2004-06-02 19:20 ` Andi Kleen [this message]
2004-06-02 22:02 ` Alasdair G Kergon
2004-07-03 5:30 ` Daniel Phillips
2004-07-03 6:04 ` Jeff Garzik
2004-07-03 9:09 ` Daniel Phillips
2004-06-02 15:42 Alasdair G Kergon
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=20040602192045.GA87771@colin2.muc.de \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
/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.