* mount: fence a dropped handle only when it holds unpublished content
dirtyMetadata is also set by chmod, xattr and fallocate, so a failed
metadata-only close refused every later write of the inode.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* mount: fence the inode before its last handle leaves the handle map
A reopen between the map removal and the fence could publish at the
stale kernel EOF.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* mount: fence a failed metadata flush only when the handle holds content
A refused synchronous flush or an abandoned writeback metadata flush of a
handle with only chmod, xattr or fallocate changes fenced the inode, so
later writes were refused until FORGET.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* mount: count a size change on an open handle as unpublished content
A truncate or extend through an open handle changes the entry's size and
chunks, but it set only dirtyMetadata. A failed close then skipped the
final-release fence, so a reopen before FORGET could publish against the
untruncated entry.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* mount: mark copied content dirty before each page of a streaming copy
A copy that failed or was cancelled after earlier pages were accepted left
dirtyContent false, so the final-release fence skipped that content.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* mount: mark copied content dirty only after a page is accepted
A copy whose first page is rejected leaves the destination unchanged and
the kernel EOF where it was, so fencing the inode on release only blocked
later writes until FORGET.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* mount: skip the server-side copy while the destination holds unpublished content
A whole-file server copy clears dirtyContent when it commits, so a page a
cancelled streaming copy left behind would lose its release fence. Fall
back to the streaming copy instead.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* mount: skip the server-side copy while the source holds unpublished content
The filer copies the stored source, so pages still pending on the source
handle would be missing from the destination. The streaming copy reads
them through the dirty pages.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* mount: check the publication fence before a server-side whole-file copy
The filer copy publishes the destination without going through the
flush-time guard, so a fenced writeback inode could still take new
content before FORGET. Fall back to the streaming copy, whose flush is
guarded.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Concurrent writers to one file from different mounts require -dlm; without it, a conflicting write fails with EIO and the file may refuse further appends until reopened after the cache drops.
