[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
This was fixed in the latest 4.15 kernels (linux-hwe 4.15.0-60.67) ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Released ** Changed in: linux-hwe (Ubuntu) Status: New => Fix Released ** Changed in: linux-hwe (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-hwe (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802585 Title: NFS v4.0: Stale data after file is renamed while another process has an open file handle Status in linux package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Status in linux-hwe source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-hwe source package in Bionic: Invalid Status in linux source package in Cosmic: Won't Fix Status in linux-hwe source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-hwe source package in Disco: Won't Fix Bug description: NOTE: This bug has been fixed in the upstream mainline kernel via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1 and merged in the latest NFS client patches in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13. The full patchset is here: https://marc.info/?l=linux- nfs=153816500525563=2 I'm repeating the report I sent to the NFS maintainers on the mailing list: On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where stale data is shown if a file remains open on one machine, and the file is overwritten via a rename() on another. Here's my test: 1. On node A, create two different files on a shared NFS mount: "test1.txt" and "test2.txt". 2. On node B, continuously show the contents of the first file: "while true; do cat test1.txt; done" 3. On node B, run a process that keeps "test1.txt" open. For example, with Python, run: f = open('/nfs-mount/test1.txt', 'r') 4. Rename test2.txt via "mv -f test2.txt test1.txt" On node B, I see the contents of the original test1.txt indefinitely, even after I disabled attribute caching and the lookup cache. I can make the while loop in step 2 show the new content if I perform one of these actions: 1. Run "ls /nfs-mount" 2. Close the open file in step 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
My reproducer for Disco+ is a different bug. I get input/output errors very quickly once specifying nfs vers=4.0. If you don't specify it, it works fine. ** Changed in: linux (Ubuntu Disco) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802585 Title: NFS v4.0: Stale data after file is renamed while another process has an open file handle Status in linux package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in linux-hwe source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: New Status in linux source package in Cosmic: Won't Fix Status in linux-hwe source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-hwe source package in Disco: Won't Fix Bug description: NOTE: This bug has been fixed in the upstream mainline kernel via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1 and merged in the latest NFS client patches in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13. The full patchset is here: https://marc.info/?l=linux- nfs=153816500525563=2 I'm repeating the report I sent to the NFS maintainers on the mailing list: On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where stale data is shown if a file remains open on one machine, and the file is overwritten via a rename() on another. Here's my test: 1. On node A, create two different files on a shared NFS mount: "test1.txt" and "test2.txt". 2. On node B, continuously show the contents of the first file: "while true; do cat test1.txt; done" 3. On node B, run a process that keeps "test1.txt" open. For example, with Python, run: f = open('/nfs-mount/test1.txt', 'r') 4. Rename test2.txt via "mv -f test2.txt test1.txt" On node B, I see the contents of the original test1.txt indefinitely, even after I disabled attribute caching and the lookup cache. I can make the while loop in step 2 show the new content if I perform one of these actions: 1. Run "ls /nfs-mount" 2. Close the open file in step 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
** Also affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu Cosmic) Status: New => Won't Fix ** Changed in: linux-hwe (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802585 Title: NFS v4.0: Stale data after file is renamed while another process has an open file handle Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in linux-hwe source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: New Status in linux source package in Cosmic: Won't Fix Status in linux-hwe source package in Cosmic: Won't Fix Status in linux source package in Disco: Confirmed Status in linux-hwe source package in Disco: Won't Fix Bug description: NOTE: This bug has been fixed in the upstream mainline kernel via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1 and merged in the latest NFS client patches in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13. The full patchset is here: https://marc.info/?l=linux- nfs=153816500525563=2 I'm repeating the report I sent to the NFS maintainers on the mailing list: On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where stale data is shown if a file remains open on one machine, and the file is overwritten via a rename() on another. Here's my test: 1. On node A, create two different files on a shared NFS mount: "test1.txt" and "test2.txt". 2. On node B, continuously show the contents of the first file: "while true; do cat test1.txt; done" 3. On node B, run a process that keeps "test1.txt" open. For example, with Python, run: f = open('/nfs-mount/test1.txt', 'r') 4. Rename test2.txt via "mv -f test2.txt test1.txt" On node B, I see the contents of the original test1.txt indefinitely, even after I disabled attribute caching and the lookup cache. I can make the while loop in step 2 show the new content if I perform one of these actions: 1. Run "ls /nfs-mount" 2. Close the open file in step 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
I was also able to reproduce this on Eoan by specifying vers=4.0 - where I thought it should be fixed. I was able to confirm that the -proposed 4.15 kernel (I tested xenial HWE version) does have the fix and it works:https://lists.ubuntu.com/archives/xenial- changes/2019-August/025318.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802585 Title: NFS v4.0: Stale data after file is renamed while another process has an open file handle Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Confirmed Bug description: NOTE: This bug has been fixed in the upstream mainline kernel via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1 and merged in the latest NFS client patches in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13. The full patchset is here: https://marc.info/?l=linux- nfs=153816500525563=2 I'm repeating the report I sent to the NFS maintainers on the mailing list: On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where stale data is shown if a file remains open on one machine, and the file is overwritten via a rename() on another. Here's my test: 1. On node A, create two different files on a shared NFS mount: "test1.txt" and "test2.txt". 2. On node B, continuously show the contents of the first file: "while true; do cat test1.txt; done" 3. On node B, run a process that keeps "test1.txt" open. For example, with Python, run: f = open('/nfs-mount/test1.txt', 'r') 4. Rename test2.txt via "mv -f test2.txt test1.txt" On node B, I see the contents of the original test1.txt indefinitely, even after I disabled attribute caching and the lookup cache. I can make the while loop in step 2 show the new content if I perform one of these actions: 1. Run "ls /nfs-mount" 2. Close the open file in step 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
I was able to reproduce this. Minor note, that you need to specify vers=4.0 in the mount options, nfs 4.1+ appears to not be affected by this. ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802585 Title: NFS v4.0: Stale data after file is renamed while another process has an open file handle Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Confirmed Bug description: NOTE: This bug has been fixed in the upstream mainline kernel via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1 and merged in the latest NFS client patches in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13. The full patchset is here: https://marc.info/?l=linux- nfs=153816500525563=2 I'm repeating the report I sent to the NFS maintainers on the mailing list: On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where stale data is shown if a file remains open on one machine, and the file is overwritten via a rename() on another. Here's my test: 1. On node A, create two different files on a shared NFS mount: "test1.txt" and "test2.txt". 2. On node B, continuously show the contents of the first file: "while true; do cat test1.txt; done" 3. On node B, run a process that keeps "test1.txt" open. For example, with Python, run: f = open('/nfs-mount/test1.txt', 'r') 4. Rename test2.txt via "mv -f test2.txt test1.txt" On node B, I see the contents of the original test1.txt indefinitely, even after I disabled attribute caching and the lookup cache. I can make the while loop in step 2 show the new content if I perform one of these actions: 1. Run "ls /nfs-mount" 2. Close the open file in step 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802585 Title: NFS v4.0: Stale data after file is renamed while another process has an open file handle Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: NOTE: This bug has been fixed in the upstream mainline kernel via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1 and merged in the latest NFS client patches in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13. The full patchset is here: https://marc.info/?l=linux- nfs=153816500525563=2 I'm repeating the report I sent to the NFS maintainers on the mailing list: On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where stale data is shown if a file remains open on one machine, and the file is overwritten via a rename() on another. Here's my test: 1. On node A, create two different files on a shared NFS mount: "test1.txt" and "test2.txt". 2. On node B, continuously show the contents of the first file: "while true; do cat test1.txt; done" 3. On node B, run a process that keeps "test1.txt" open. For example, with Python, run: f = open('/nfs-mount/test1.txt', 'r') 4. Rename test2.txt via "mv -f test2.txt test1.txt" On node B, I see the contents of the original test1.txt indefinitely, even after I disabled attribute caching and the lookup cache. I can make the while loop in step 2 show the new content if I perform one of these actions: 1. Run "ls /nfs-mount" 2. Close the open file in step 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
Looks good to me! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802585 Title: NFS v4.0: Stale data after file is renamed while another process has an open file handle Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: NOTE: This bug has been fixed in the upstream mainline kernel via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1 and merged in the latest NFS client patches in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13. The full patchset is here: https://marc.info/?l=linux- nfs=153816500525563=2 I'm repeating the report I sent to the NFS maintainers on the mailing list: On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where stale data is shown if a file remains open on one machine, and the file is overwritten via a rename() on another. Here's my test: 1. On node A, create two different files on a shared NFS mount: "test1.txt" and "test2.txt". 2. On node B, continuously show the contents of the first file: "while true; do cat test1.txt; done" 3. On node B, run a process that keeps "test1.txt" open. For example, with Python, run: f = open('/nfs-mount/test1.txt', 'r') 4. Rename test2.txt via "mv -f test2.txt test1.txt" On node B, I see the contents of the original test1.txt indefinitely, even after I disabled attribute caching and the lookup cache. I can make the while loop in step 2 show the new content if I perform one of these actions: 1. Run "ls /nfs-mount" 2. Close the open file in step 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Xenial) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Bionic) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Cosmic) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Disco) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802585 Title: NFS v4.0: Stale data after file is renamed while another process has an open file handle Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: NOTE: This bug has been fixed in the upstream mainline kernel via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1 and merged in the latest NFS client patches in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13. The full patchset is here: https://marc.info/?l=linux- nfs=153816500525563=2 I'm repeating the report I sent to the NFS maintainers on the mailing list: On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where stale data is shown if a file remains open on one machine, and the file is overwritten via a rename() on another. Here's my test: 1. On node A, create two different files on a shared NFS mount: "test1.txt" and "test2.txt". 2. On node B, continuously show the contents of the first file: "while true; do cat test1.txt; done" 3. On node B, run a process that keeps "test1.txt" open. For example, with Python, run: f = open('/nfs-mount/test1.txt', 'r') 4. Rename test2.txt via "mv -f test2.txt test1.txt" On node B, I see the contents of the original test1.txt indefinitely, even after I disabled attribute caching and the lookup cache. I can make the while loop in step 2 show the new content if I perform one of these actions: 1. Run "ls /nfs-mount" 2. Close the open file in step 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
I built a test kernel with commit be189f7e7f03. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1802585 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802585 Title: NFS v4.0: Stale data after file is renamed while another process has an open file handle Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: NOTE: This bug has been fixed in the upstream mainline kernel via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1 and merged in the latest NFS client patches in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13. The full patchset is here: https://marc.info/?l=linux- nfs=153816500525563=2 I'm repeating the report I sent to the NFS maintainers on the mailing list: On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where stale data is shown if a file remains open on one machine, and the file is overwritten via a rename() on another. Here's my test: 1. On node A, create two different files on a shared NFS mount: "test1.txt" and "test2.txt". 2. On node B, continuously show the contents of the first file: "while true; do cat test1.txt; done" 3. On node B, run a process that keeps "test1.txt" open. For example, with Python, run: f = open('/nfs-mount/test1.txt', 'r') 4. Rename test2.txt via "mv -f test2.txt test1.txt" On node B, I see the contents of the original test1.txt indefinitely, even after I disabled attribute caching and the lookup cache. I can make the while loop in step 2 show the new content if I perform one of these actions: 1. Run "ls /nfs-mount" 2. Close the open file in step 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: Confirmed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Disco) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Disco) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802585 Title: NFS v4.0: Stale data after file is renamed while another process has an open file handle Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: NOTE: This bug has been fixed in the upstream mainline kernel via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1 and merged in the latest NFS client patches in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13. The full patchset is here: https://marc.info/?l=linux- nfs=153816500525563=2 I'm repeating the report I sent to the NFS maintainers on the mailing list: On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where stale data is shown if a file remains open on one machine, and the file is overwritten via a rename() on another. Here's my test: 1. On node A, create two different files on a shared NFS mount: "test1.txt" and "test2.txt". 2. On node B, continuously show the contents of the first file: "while true; do cat test1.txt; done" 3. On node B, run a process that keeps "test1.txt" open. For example, with Python, run: f = open('/nfs-mount/test1.txt', 'r') 4. Rename test2.txt via "mv -f test2.txt test1.txt" On node B, I see the contents of the original test1.txt indefinitely, even after I disabled attribute caching and the lookup cache. I can make the while loop in step 2 show the new content if I perform one of these actions: 1. Run "ls /nfs-mount" 2. Close the open file in step 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802585 Title: NFS v4.0: Stale data after file is renamed while another process has an open file handle Status in linux package in Ubuntu: Confirmed Bug description: NOTE: This bug has been fixed in the upstream mainline kernel via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1 and merged in the latest NFS client patches in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13. The full patchset is here: https://marc.info/?l=linux- nfs=153816500525563=2 I'm repeating the report I sent to the NFS maintainers on the mailing list: On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where stale data is shown if a file remains open on one machine, and the file is overwritten via a rename() on another. Here's my test: 1. On node A, create two different files on a shared NFS mount: "test1.txt" and "test2.txt". 2. On node B, continuously show the contents of the first file: "while true; do cat test1.txt; done" 3. On node B, run a process that keeps "test1.txt" open. For example, with Python, run: f = open('/nfs-mount/test1.txt', 'r') 4. Rename test2.txt via "mv -f test2.txt test1.txt" On node B, I see the contents of the original test1.txt indefinitely, even after I disabled attribute caching and the lookup cache. I can make the while loop in step 2 show the new content if I perform one of these actions: 1. Run "ls /nfs-mount" 2. Close the open file in step 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
** Attachment added: "apport.linux.PkXffd.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+attachment/5210974/+files/apport.linux.PkXffd.apport ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802585 Title: NFS v4.0: Stale data after file is renamed while another process has an open file handle Status in linux package in Ubuntu: Confirmed Bug description: NOTE: This bug has been fixed in the upstream mainline kernel via https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1 and merged in the latest NFS client patches in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13. The full patchset is here: https://marc.info/?l=linux- nfs=153816500525563=2 I'm repeating the report I sent to the NFS maintainers on the mailing list: On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where stale data is shown if a file remains open on one machine, and the file is overwritten via a rename() on another. Here's my test: 1. On node A, create two different files on a shared NFS mount: "test1.txt" and "test2.txt". 2. On node B, continuously show the contents of the first file: "while true; do cat test1.txt; done" 3. On node B, run a process that keeps "test1.txt" open. For example, with Python, run: f = open('/nfs-mount/test1.txt', 'r') 4. Rename test2.txt via "mv -f test2.txt test1.txt" On node B, I see the contents of the original test1.txt indefinitely, even after I disabled attribute caching and the lookup cache. I can make the while loop in step 2 show the new content if I perform one of these actions: 1. Run "ls /nfs-mount" 2. Close the open file in step 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp