Date: Mon, 01 Jan 2024 22:06:37 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 276002] nfscl: data corruption using both copy_file_range and mmap'd I/O Message-ID: <bug-276002-3630-t9XGOnrDnD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-276002-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-276002-3630@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=3D276002 --- Comment #36 from Lexi Winter <lexi.freebsd@le-fay.org> --- fwiw, my own issue with NFS+mmap() was using net-p2p/rtorrent, which is a fairly widely used application and which (famously) uses mmap() for nearly = all filesystem operations. when running it on NFS, i found it frequently repor= ted data corruption issues with the files it wrote to (i.e., it would write to files using mmap(), but on reading those files later, the data that was wri= tten was not as expected). that said, i am the only person (other than Geoffrey) who i've seen report issues related to this. i couldn't say whether this is because the number = of people who use FreeBSD NFS and mmap() is relatively small, or because the problem was caused by something else. i only mention this at all to add some context to the discussion :-) --=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-276002-3630-t9XGOnrDnD>