Actions
Feature #54280
closedsupport truncation sequences in sparse reads
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
backport_processed
Backport:
quincy
Reviewed:
Description
I've been working on sparse read support in the kclient, and got something working today, only to notice that after truncating a file, I would often get back -EINVAL when trying to read it. The problem seems to be this in PrimaryLogPG::do_sparse_read() :
if (op.extent.truncate_seq) { dout(0) << "sparse_read does not support truncation sequence " << dendl; return -EINVAL; }
Would it be possible to support sparse reads against objects that have a non-zero truncate_seq?
Actions