I would certainly be willing to help test this. I would even suggest a
step further where a volume option would automatically poke the hole if
a write created a null block.
On 01/22/16 08:58, Niels de Vos wrote:
On Fri, Jan 22, 2016 at 04:07:54PM +0000, Ankireddypalle Reddy wrote:
Hi,
Thanks for checking this. If this is not supported through FUSE can
this be done through libgfapi.
Not yet. I was thinking of adding support for this after
SEEK_HOLE/SEEK_DATA has been merged. Maybe we can include hole punching
in gfapi for 3.8, where FUSE follows later. Would you be willing to
assist with the development or testing of that?
Thanks,
Niels
Thanks and Regards,
Ram
-----Original Message-----
From: Niels de Vos [mailto:[email protected]]
Sent: Friday, January 22, 2016 11:05 AM
To: Ankireddypalle Reddy
Cc: [email protected]
Subject: Re: [Gluster-users] support for hole punching in glusterfs
On Fri, Jan 22, 2016 at 03:05:16PM +0000, Ankireddypalle Reddy wrote:
Hi,
Hole punching through fallocate succeeds for a ext4 mount path. But it
fails for a glusterfs mount path. The volume is a disperse volume.
fallocate(fd,FALLOC_FL_PUNCH_HOLE|FALLOC_FL_KEEP_SIZE,0,sizeof(array))
fails with a return code of EOPNOTSUPP.
The ext4 file system mount arguments are
"rw,noexec,nosuid,nodev,user_xattr,discard".
This is currently not supported yet. I'm not sure if the FUSE kernel module
support punching holes yet, either. Please file a bug for this feature so that
we can figure out a plan to work on it.
https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS&component=fuse
Note that support for SEEK_HOLE and SEEK_DATA is also not availeble yet.
Some work has been done, but it is not ready for inclusion at this moment.
Hopefully it lands in the upcoming 3.8 release.
https://bugzilla.redhat.com/show_bug.cgi?id=1220173
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."
**********************************************************************
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
