On Wednesday 24 December 2014 02:30 PM, Raghavendra Bhat wrote:
Hi,
I have a doubt. In user serviceable snapshots as of now statfs call is
not implemented. There are 2 ways how statfs can be handled.
1) Whenever snapview-client xlator gets statfs call on a path that
belongs to snapshot world, it can send the
statfs call to the main volume itself, with the path and the inode
being set to the root of the main volume.
In this approach, when statfs call is sent to main volume with path and
inode set to the root can give incorrect value when quota and
deem-statfs are enabled.
path/inode should be set to the parent of '.snaps'
Thanks,
Vijay
OR
2) It can redirect the call to the snapshot world (the snapshot demon
which talks to all the snapshots of that particular volume) and send
back the reply that it has obtained.
Please provide feedback.
Regards,
Raghavendra Bhat
_______________________________________________
Gluster-devel mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-devel
