On Tue, Jan 6, 2015 at 12:43 PM, Raghavendra Bhat rab...@redhat.com wrote:
On Monday 29 December 2014 01:19 PM, RAGHAVENDRA TALUR wrote:
On Sun, Dec 28, 2014 at 5:03 PM, Vijay Bellur vbel...@redhat.com wrote:
On 12/24/2014 02:30 PM, Raghavendra Bhat wrote:
Hi,
I have a doubt. In user
On Monday 29 December 2014 01:19 PM, RAGHAVENDRA TALUR wrote:
On Sun, Dec 28, 2014 at 5:03 PM, Vijay Bellur vbel...@redhat.com wrote:
On 12/24/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
On 12/24/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
On Sun, Dec 28, 2014 at 5:03 PM, Vijay Bellur vbel...@redhat.com wrote:
On 12/24/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
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
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
