From 9e9e3c5620882d2f769694996ff4d7e0cf36cc2b Mon Sep 17 00:00:00 2001 From: raghavendra talur Date: Thu, 20 Aug 2015 15:09:31 +0530 Subject: Create basic directory structure All new features specs go into in_progress directory. Once signed off, it should be moved to done directory. For now, This change moves all the Gluster 4.0 feature specs to in_progress. All other specs are under done/release-version. More cleanup required will be done incrementally. Change-Id: Id272d301ba8c434cbf7a9a966ceba05fe63b230d BUG: 1206539 Signed-off-by: Raghavendra Talur Reviewed-on: http://review.gluster.org/11969 Reviewed-by: Humble Devassy Chirammal Reviewed-by: Prashanth Pai Tested-by: Humble Devassy Chirammal --- .../Gluster User Serviceable Snapshots.md | 39 ++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 done/GlusterFS 3.6/Gluster User Serviceable Snapshots.md (limited to 'done/GlusterFS 3.6/Gluster User Serviceable Snapshots.md') diff --git a/done/GlusterFS 3.6/Gluster User Serviceable Snapshots.md b/done/GlusterFS 3.6/Gluster User Serviceable Snapshots.md new file mode 100644 index 0000000..9af7062 --- /dev/null +++ b/done/GlusterFS 3.6/Gluster User Serviceable Snapshots.md @@ -0,0 +1,39 @@ +Feature +------- + +Enable user-serviceable snapshots for GlusterFS Volumes based on +GlusterFS-Snapshot feature + +Owners +------ + +Anand Avati +Anand Subramanian +Raghavendra Bhat +Varun Shastry + +Summary +------- + +Each snapshot capable GlusterFS Volume will contain a .snaps directory +through which a user will be able to access previously point-in-time +snapshot copies of his data. This will be enabled through a hidden +.snaps folder in each directory or sub-directory within the volume. +These user-serviceable snapshot copies will be read-only. + +Tests +----- + +​1) Enable uss (gluster volume set features.uss enable) A +snap daemon should get started for the volume. It should be visible in +gluster volume status command. 2) entering the snapshot world ls on +.snaps from any directory within the filesystem should be successful and +should show the list of snapshots as directories. 3) accessing the +snapshots One of the snapshots can be entered and it should show the +contents of the directory from which .snaps was entered, when the +snapshot was taken. NOTE: If the directory was not present when a +snapshot was taken (say snap1) and created later, then entering snap1 +directory (or any access) will fail with stale file handle. 4) Reading +from snapshots Any kind of read operations from the snapshots should be +successful. But any modifications to snapshot data is not allowed. +Snapshots are read-only \ No newline at end of file -- cgit