{"version":"2.1.181","anchor":"graceful-handling-of-fchmod-fsync-on-restricted-filesystems","canonical_anchor":"graceful-handling-of-fchmod-fsync-on-restricted-filesystems","heading":"Graceful Handling of fchmod \/ fsync on Restricted Filesystems","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.181\/e\/graceful-handling-of-fchmod-fsync-on-restricted-filesystems","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.181","markdown":"### Graceful Handling of `fchmod`\/`fsync` on Restricted Filesystems\n\nThe atomic file-write path now catches `EINVAL`, `ENOTSUP`, `EPERM`, and `ENOSYS` errors from `fchmod` and `fsync` calls and continues rather than aborting. This resolves hard write failures on certain network filesystems and Docker-mounted volumes that don't support those syscalls.\n\nPreviously, a `fchmod` error on a file that had just been written would leave the file in an inconsistent state. Now Claude Code logs the limitation (e.g. `\"fchmod unsupported on this filesystem\"`) and continues normally.\n\n**Evidence**\n\nGraceful syscall error handling (search for `\"fchmod unsupported on this filesystem:\"`) \u2014 `uze()` helper at line ~55344; sync path at line ~55365"}