Bug 1301332 - improve sparse file handling by supporting SEEK_HOLE / SEEK_DATA
Summary: improve sparse file handling by supporting SEEK_HOLE / SEEK_DATA
Alias: None
Product: nfs-ganesha
Classification: Retired
Version: unspecified
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Niels de Vos
QA Contact:
Depends On: 1220173
TreeView+ depends on / blocked
Reported: 2016-01-24 10:20 UTC by Niels de Vos
Modified: 2020-06-24 11:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2020-06-24 11:18:45 UTC

Attachments (Terms of Use)

Description Niels de Vos 2016-01-24 10:20:24 UTC
Description of problem:
NFSv4 supports SEEK_HOLE and SEEK_DATA and this can improve the handling of sparse files (like virtual machine images) a lot. Gluster is going to support this soon too, see bug 1220173 for more details.

Steps to Reproduce:
1. create a sparse file on a NFSv4 mountpoint (use 'qemu-img')
2. copy the sparse file from the NFSv4 mount to somewhere (use 'cp')
3. compare the allocated space of the two files

Actual results:
The copy is fully allocated.

Expected results:
The copy should have holes as well.

Comment 1 Pasi Karkkainen 2018-08-31 13:57:11 UTC
Does nfs-ganesha support SEEK_HOLE / SEEK_DATA these days? 
Those features are part of NFSv4.2 protocol standard.

Comment 2 Jiffin 2018-09-05 03:39:45 UTC
The support was added in 2.7 branch(current devel branch) https://review.gerrithub.io/#/c/ffilz/nfs-ganesha/+/393642/. But not available in stable releases.

Comment 3 Pasi Karkkainen 2018-09-05 06:37:16 UTC
Great, thanks!

Comment 4 Kaleb KEITHLEY 2020-06-24 11:18:45 UTC
If this is still an issue please open an issue in the github tracker at https://github.com/nfs-ganesha/nfs-ganesha/issues

Note You need to log in before you can comment on or make changes to this bug.