Feature #19819
closedAdd support of FS_IOC_FIEMAP ioctl on files, accessible through CephFS
0%
Description
The purpose of this -- is to have standard interface for examining allocated extents of the files. For example, xfs_io command can use this to show extents on many filesystems, but unfortunatelly, not on CephFS.
(Also, can anyone tell which command from ceph toolbox should I use to show really allocated segents of the file)
Updated by Greg Farnum almost 7 years ago
- Project changed from Ceph to CephFS
- Category set to Administration/Usability
This is pretty infeasible right now -- nothing tracks which bits of a file are allocated or exist. The closest it comes is max size and the ability in RADOS to query specific allocations.
Updated by John Spray almost 7 years ago
Марк: is this ticket describing something you want to work on, or is it just a request? In either case, what's the motivation?
Updated by Марк Коренберг almost 7 years ago
This is feature request. I have no skills and proper knowledge on CephFS to implement this feature.
Motivation -- is ability to view which parts of file has been actually allocated, i.e. to know how many space is used actually for specific file.
Now, files on CephFS, create using `truncate` and `fallocate` are indistinguishable, and both are created momentarily. Moreover, fallocate on CephFS is a fake. It doesn't allocate space actually.
Updated by John Spray almost 7 years ago
- Status changed from New to Rejected
Okay. I'm going to close this, because implementing that ioctl efficiently isn't doable without major changes to how CephFS stores files (i.e. making CephFS keep an index of which parts of a file have been written).
If you have an application that needs a record of which parts of a file it has written, I would suggest implementing that within your application.
Updated by Марк Коренберг almost 7 years ago
Please don't close, since issue is valid, and maybe someone wil eventually fix it.