fef61684b4
currently, we sort chunks by inode when verifying or backing up to tape. we get the inode# by stat'ing each chunk, which may be more expensive than the gains of reading the chunks in order Since that is highly dependent on the underlying storage of the datastore, introduce a tuning option so that the admin can tune that behaviour for each datastore. The default stays the same (sorting by inode) Signed-off-by: Dominik Csapak <d.csapak@proxmox.com> |
||
---|---|---|
.. | ||
tape | ||
acl.rs | ||
common_regex.rs | ||
crypto.rs | ||
datastore.rs | ||
file_restore.rs | ||
human_byte.rs | ||
jobs.rs | ||
key_derivation.rs | ||
lib.rs | ||
network.rs | ||
openid.rs | ||
percent_encoding.rs | ||
remote.rs | ||
traffic_control.rs | ||
user.rs | ||
userid.rs | ||
zfs.rs |