[Bugs] [Bug 1218383] New: [Backup]: To capture path for deletes in changelog file
bugzilla at redhat.com
bugzilla at redhat.com
Mon May 4 18:36:21 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1218383
Bug ID: 1218383
Summary: [Backup]: To capture path for deletes in changelog
file
Product: GlusterFS
Version: 3.7.0
Component: glusterfind
Assignee: bugs at gluster.org
Reporter: khiremat at redhat.com
QA Contact: bugs at gluster.org
CC: avishwan at redhat.com, bugs at gluster.org,
khiremat at redhat.com, sanandpa at redhat.com
Depends On: 1214561
Blocks: 1186580 (qe_tracker_everglades), 1217935
+++ This bug was initially created as a clone of Bug #1214561 +++
Description of problem:
Glusterfind API presently is just able to mention the files which have been
newly created, or have had data/metadata changes. In case a file is deleted, it
is not able to get that information from the changelog file
This bug is to track the progress made on that front.
Version-Release number of selected component (if applicable):
Glusterfs 3.7 upstream
How reproducible: Always
Steps to Reproduce:
1. Have a gluster volume of type distribute/replicate
2. Create 2 files 'file1' and 'file2'
3. Edit the contents of 'file2'
4. Delete 'file2'
5. Change the permissions of 'file1' to (say) read-only
6. Verify the contents of changelog file.
Actual results:
Step 6 should shows Entry operations for 'file1' and 'file2', followed with
Data operation for 'file2', and a Metadata operation for 'file1'
Delete operation of 'file2' (step4) is not recorded in the changelog file.
Expected results:
Delete operation of 'file2' should get recorded in the changelog file, which in
turn can be used by Glusterfind.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1186580
[Bug 1186580] QE tracker bug for Everglades
https://bugzilla.redhat.com/show_bug.cgi?id=1214561
[Bug 1214561] [Backup]: To capture path for deletes in changelog file
https://bugzilla.redhat.com/show_bug.cgi?id=1217935
[Bug 1217935] [Backup]: To capture path for deletes in changelog file
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list