[Bug 276002] nfscl: data corruption using both copy_file_range and mmap'd I/O
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 01 Jan 2024 22:06:37 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276002 --- 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 reported 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 written 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 :-) -- You are receiving this mail because: You are the assignee for the bug.