Date: Mon, 24 Apr 2023 21:44:12 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 270810] munmap does not always sync the underlying file Message-ID: <bug-270810-227-Xok0Wmy7Ea@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-270810-227@https.bugs.freebsd.org/bugzilla/> References: <bug-270810-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270810 --- Comment #8 from geoffrey@dommett.com --- How is this not a bug ? Under the circumstances described the pages are not written to the nfs serv= er EVER. the written data is permanently lost. This is not an issue of a local cache since reading back the file on the machine that wrote it gives the same corruption. This seems to be an interaction with nfsv3. When the nfs server is mounted using nfsv2, the application goes into a sta= te of nfsio when it exits, and written pages are updated. when the nfs server is mounted nfsv3, if the application quits, the page updating ceases, and any unwritten data is permanently lost. msync (if called) returns without writing the pages, at least when nfsv3 is used I have not properly tested nfsv4 yet, I will post further comment with the result on this --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-270810-227-Xok0Wmy7Ea>