[Gluster-users] [Gluster-devel] Hole punch support

[Ankireddypalle Reddy]

Niels,
             Below are the two issues that I noticed and created bugs for tracking.
             1)  For disperse volumes hole punch is currently not supported. The support seems to be in works.
                   https://bugzilla.redhat.com/show_bug.cgi?id=1394298

             2)  For a replica/distribute volume after punching hole in the file the reported size is not correct.
                   You could see the description of problem in 
                   https://bugzilla.redhat.com/show_bug.cgi?id=1398381

Thanks and Regards,
Ram                   

-----Original Message-----
From: Niels de Vos [mailto:ndevos at redhat.com] 
Sent: Monday, November 28, 2016 10:32 AM
To: Ankireddypalle Reddy
Cc: gluster-users at gluster.org; Gluster Devel (gluster-devel at gluster.org)
Subject: Re: [Gluster-devel] Hole punch support

On Thu, Nov 24, 2016 at 03:58:01PM +0000, Ankireddypalle Reddy wrote:
> Hi,
>       Gluster does not seem to be supporting hole punch support correctly. This might be a limiting factor for people switching from hardware based storage  to glusterfs for archival/backup use cases.  In these use cases hole punch support is one of the key deciding factors. I request gluster developers to expedite their efforts in this direction.

Hi Ram,

this is something we should be able to fix somehow. There is a similar bug reported for this already:

  fallocate + punch_hole used instead of fallocate + zero_range in glfs_discard()
  https://bugzilla.redhat.com/show_bug.cgi?id=1327857

>From a cursory look, libgfapi supports punching holes through the
glfs_discard() function. FUSE also has an implementation for fallocate().

How are you testing this, and what is the behaviour you see?

Thanks,
Niels
***************************Legal Disclaimer***************************
"This communication may contain confidential and privileged material for the
sole use of the intended recipient. Any unauthorized review, use or distribution
by others is strictly prohibited. If you have received the message by mistake,
please advise the sender by reply email and delete the message. Thank you."
**********************************************************************