Skip to contentSkip to conversation

sporadic generic/154 failure

DISCUSSION J. Bruce Fields 2 participants 3 messages Aug 23, 2021

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

I'm seeing generic/154 failing sometimes.

It does a "cp --reflink" (which uses FI_CLONE, which results in a ->remap_file_range call that NFS maps to the CLONE operation), then overwriting parts of the fire, and checking free blocks (with "stat -f /path -c "%f") at various points, and failing when the number of free blocks is outside an expected range.

I don't know if it might be some caching issue, or something about how NFS reports free blocks.

Honestly it looks unlikely to be critical, so for now I'm ignoring it....

--b.

#1 lore raw
Quoted 8 lines · J. Bruce Fields

I'm seeing generic/154 failing sometimes.

It does a "cp --reflink" (which uses FI_CLONE, which results in a ->remap_file_range call that NFS maps to the CLONE operation), then overwriting parts of the fire, and checking free blocks (with "stat -f /path -c "%f") at various points, and failing when the number of free blocks is outside an expected range.

Quoted 6 lines

I don't know if it might be some caching issue, or something about how NFS reports free blocks.

Honestly it looks unlikely to be critical, so for now I'm ignoring it....

XFS backend? It could be speculative preallocation. The fact that NFS can defer closing the file (either due to delegations or due to the NFSv3 file cache) typically results in it taking longer for XFS to free up the blocks it preallocated. That again means it takes longer for the 'space used' to settle to the correct final value.

https://linux-xfs.oss.sgi.narkive.com/jjjfnyI1/faq-xfs-speculative-preallocation

Signature · 3 lines
Trond Myklebust
Linux NFS client maintainer, Hammerspace
[email protected]
#2 lore raw
Quoted 9 lines · Trond Myklebust
Quoted 8 lines · J. Bruce Fields

I'm seeing generic/154 failing sometimes.

It does a "cp --reflink" (which uses FI_CLONE, which results in a ->remap_file_range call that NFS maps to the CLONE operation), then overwriting parts of the fire, and checking free blocks (with "stat -f /path -c "%f") at various points, and failing when the number of free blocks is outside an expected range.

Quoted 8 lines
Quoted 6 lines

I don't know if it might be some caching issue, or something about how NFS reports free blocks.

Honestly it looks unlikely to be critical, so for now I'm ignoring it....

XFS backend?

Yes.

Quoted 7 lines

It could be speculative preallocation. The fact that NFS
can defer closing the file (either due to delegations or due to the NFSv3 file cache) typically results in it taking longer for XFS to free up the blocks it preallocated. That again means it takes longer for the 'space used' to settle to the correct final value.

https://linux-xfs.oss.sgi.narkive.com/jjjfnyI1/faq-xfs-speculative-preallocation

That sounds plausible.

--b.