Bug #8542
closed
kcephfs: fsx failure on read (expected 0's)
Added by Sage Weil almost 10 years ago.
Updated almost 8 years ago.
Description
2014-06-05T01:59:10.768 INFO:teuthology.task.workunit.client.0.plana67.stdout:READ BAD DATA: offset = 0x1bede, size = 0x49b6, fname = 1MB
2014-06-05T01:59:10.768 INFO:teuthology.task.workunit.client.0.plana67.stdout:OFFSET GOOD BAD RANGE
2014-06-05T01:59:10.768 INFO:teuthology.task.workunit.client.0.plana67.stdout:0x1d387 0x0000 0x9c2d 0x 0
ubuntu@teuthology:/a/teuthology-2014-06-02_23:02:10-kcephfs-master-testing-basic-plana/289501
teuthology-2014-06-06_23:01:56-kcephfs-master-testing-basic-plana/297431/
/a/teuthology-2014-06-01_23:02:07-kcephfs-next-testing-basic-plana/285055
/teuthology-2014-05-30_23:02:02-kcephfs-master-testing-basic-plana/283020/
- Status changed from New to Resolved
ceph_fallocate() does not recognize FALLOC_FL_ZERO_RANGE
So...we need to implement that functionality, don't we? Just knowing the problem isn't a resolution, if we're no longer compliant with Linux ABI expectations.
There is no way we can support it
/*
* FALLOC_FL_ZERO_RANGE is used to convert a range of file to zeros preferably
* without issuing data IO. Blocks should be preallocated for the regions that
* span holes in the file, and the entire range is preferable converted to
* unwritten extents - even though file system may choose to zero out the
* extent or do whatever which will result in reading zeros from the range
* while the range remains allocated for the file.
*
* This can be also used to preallocate blocks past EOF in the same way as
* with fallocate. Flag FALLOC_FL_KEEP_SIZE should cause the inode
* size to remain the same.
*/
- Status changed from Resolved to 12
We can support it, just not "preferably without issuing data IO". It needs to iterate over the range and zero the range or delete the objects. I thought this was already supported, actually... I know Client implements it.
file system may choose to zero out the extent or do whatever which will result in reading zeros from the range while the range remains allocated for the file
I don't I think we should treat FALLOC_FL_ZERO_RANGE the same as FALLOC_FL_PUNCH_HOLE. It give users false impression that we support pre-allocated blocks.
- Status changed from 12 to Fix Under Review
- Status changed from Fix Under Review to Resolved
- Component(FS) kceph added
Also available in: Atom
PDF