[Gluster-users] gluster snapshot status --xml doesn't work on v3.7.5
Hsiu-Chang Chen
syuusyou at gmail.com
Tue Nov 3 03:29:22 UTC 2015
Hi,
I have a volume created by 4 bricks and already took 2 snapshots. When I
try to get snapshot status by 'gluster snapshot status --xml', it will
return uncompleted output. Here are some examples:
*Example 1: Print all snapshots' status*
When I run 'gluster snapshot status', it returns:
Snap Name : snap1_GMT-2015.11.03-02.51.11
Snap UUID : 95dca986-7492-42f8-8a20-133e186dbdf7
Brick Path :
gfs-m1:/run/gluster/snaps/dd45a201cd1c4788b05b57b5a652aeb8/brick1/fs
Volume Group : vg1
Brick Running : No
Brick PID : N/A
Data Percentage : 0.31
LV Size : 100.00g
Brick Path :
gfs-m1:/run/gluster/snaps/dd45a201cd1c4788b05b57b5a652aeb8/brick2/fs
Volume Group : vg1
Brick Running : No
Brick PID : N/A
Data Percentage : 0.31
LV Size : 100.00g
Brick Path :
gfs-m1:/run/gluster/snaps/dd45a201cd1c4788b05b57b5a652aeb8/brick3/fs
Volume Group : vg1
Brick Running : No
Brick PID : N/A
Data Percentage : 0.31
LV Size : 100.00g
Brick Path :
gfs-m1:/run/gluster/snaps/dd45a201cd1c4788b05b57b5a652aeb8/brick4/fs
Volume Group : vg1
Brick Running : No
Brick PID : N/A
Data Percentage : 0.31
LV Size : 100.00g
Snap Name : snap2_GMT-2015.11.03-02.51.57
Snap UUID : 9b31a4fd-6e04-460d-9aaf-b16d1bfed8a2
Brick Path :
gfs-m1:/run/gluster/snaps/3aaf2d06b3034799bab05ba1f1479e9c/brick1/fs
Volume Group : vg1
Brick Running : No
Brick PID : N/A
Data Percentage : 0.31
LV Size : 100.00g
Brick Path :
gfs-m1:/run/gluster/snaps/3aaf2d06b3034799bab05ba1f1479e9c/brick2/fs
Volume Group : vg1
Brick Running : No
Brick PID : N/A
Data Percentage : 0.31
LV Size : 100.00g
Brick Path :
gfs-m1:/run/gluster/snaps/3aaf2d06b3034799bab05ba1f1479e9c/brick3/fs
Volume Group : vg1
Brick Running : No
Brick PID : N/A
Data Percentage : 0.31
LV Size : 100.00g
Brick Path :
gfs-m1:/run/gluster/snaps/3aaf2d06b3034799bab05ba1f1479e9c/brick4/fs
Volume Group : vg1
Brick Running : No
Brick PID : N/A
Data Percentage : 0.31
LV Size : 100.00g
But when I run 'gluster snapshot status --xml' it returns
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<cliOutput>
<opRet>0</opRet>
<opErrno>0</opErrno>
<opErrstr/>
<snapStatus>
<snapshots>
<snapshot>
<name>snap1_GMT-2015.11.03-02.51.11</name>
<uuid>95dca986-7492-42f8-8a20-133e186dbdf7</uuid>
<volCount>1</volCount>
<volume>
<brickCount>4</brickCount>
<brick>
<path>gfs-m1:/run/gluster/snaps/dd45a201cd1c4788b05b57b5a652aeb8/brick1/fs</path>
<volumeGroup>vg1</volumeGroup>
<snapshot>
<name>snap2_GMT-2015.11.03-02.51.57</name>
<uuid>9b31a4fd-6e04-460d-9aaf-b16d1bfed8a2</uuid>
<volCount>1</volCount>
<volume>
<brickCount>4</brickCount>
<brick>
<path>gfs-m1:/run/gluster/snaps/3aaf2d06b3034799bab05ba1f1479e9c/brick1/fs</path>
<volumeGroup>vg1</volumeGroup>
</brick>
</volume>
</snapshot>
</brick>
</volume>
</snapshot>
</snapshots>
</snapStatus>
</cliOutput>
*Example 2: Print specified snapshot's status*
When I run 'gluster snapshot status snap1_GMT-2015.11.03-02.51.11', it returns
Snap Name : snap1_GMT-2015.11.03-02.51.11
Snap UUID : 95dca986-7492-42f8-8a20-133e186dbdf7
Brick Path :
gfs-m1:/run/gluster/snaps/dd45a201cd1c4788b05b57b5a652aeb8/brick1/fs
Volume Group : vg1
Brick Running : No
Brick PID : N/A
Data Percentage : 0.31
LV Size : 100.00g
Brick Path :
gfs-m1:/run/gluster/snaps/dd45a201cd1c4788b05b57b5a652aeb8/brick2/fs
Volume Group : vg1
Brick Running : No
Brick PID : N/A
Data Percentage : 0.31
LV Size : 100.00g
Brick Path :
gfs-m1:/run/gluster/snaps/dd45a201cd1c4788b05b57b5a652aeb8/brick3/fs
Volume Group : vg1
Brick Running : No
Brick PID : N/A
Data Percentage : 0.31
LV Size : 100.00g
Brick Path :
gfs-m1:/run/gluster/snaps/dd45a201cd1c4788b05b57b5a652aeb8/brick4/fs
Volume Group : vg1
Brick Running : No
Brick PID : N/A
Data Percentage : 0.31
LV Size : 100.00g
But when I run 'gluster snapshot status snap1_GMT-2015.11.03-02.51.11
--xml', it doesn't returns anything.
Regards,
Hsiu-Chang Chen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151103/8d99e377/attachment.html>
More information about the Gluster-users
mailing list