All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Mike Snitzer <msnitzer@redhat.com>,
	"Alasdair G. Kergon" <agk@redhat.com>
Cc: dm-devel@redhat.com
Subject: [PATCH] dm snapshot: improve documentation
Date: Wed, 2 Dec 2015 12:32:49 -0500 (EST)	[thread overview]
Message-ID: <alpine.LRH.2.02.1512021230450.15019@file01.intranet.prod.int.rdu2.redhat.com> (raw)

Regarding bug 1286898 - the documentation doesn't specify the requirement 
that the origin target must be suspended, so we should add this paragraph 
to the file snapshot.txt.


From: Mikulas Patocka <mpatocka@redhat.com>

Add a node to snapshot.txt that the origin target must be suspended when
loading or unloading the snapshot target.

Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>

---
 Documentation/device-mapper/snapshot.txt |    4 ++++
 1 file changed, 4 insertions(+)

Index: linux-4.4-rc3/Documentation/device-mapper/snapshot.txt
===================================================================
--- linux-4.4-rc3.orig/Documentation/device-mapper/snapshot.txt	2015-12-02 18:26:34.000000000 +0100
+++ linux-4.4-rc3/Documentation/device-mapper/snapshot.txt	2015-12-02 18:29:10.000000000 +0100
@@ -49,6 +49,10 @@ The difference between persistent and tr
 snapshots less metadata must be saved on disk - they can be kept in
 memory by the kernel.
 
+When loading or unloading the snapshot target, the corresponding
+snapshot-origin or snapshot-merge target must be suspended. A failure to
+suspend the origin target could result in data corruption.
+
 
 * snapshot-merge <origin> <COW device> <persistent> <chunksize>
 

                 reply	other threads:[~2015-12-02 17:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LRH.2.02.1512021230450.15019@file01.intranet.prod.int.rdu2.redhat.com \
    --to=mpatocka@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=msnitzer@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.