In my Fedora NFS(4.2) server I have created sparse files.(Attached packet capture). It contains file with (16 KB data followed by 32 KB hole) & (8 KB data followed by 16 KB hole). After that I have used another Fedora 37 machine as client to do file copy operation using NFS 4.2.(packet capture attached). In this copy operation it exchanges NFS 4.2 SEEK packet. while the response in most of SEEK operation is as per the size with which the file was created, sometimes, I could see that NFS SEEK response has skipped holes. As a result the next READ operation has more data length.(packet no 499,500,501) (1131,1132,1133) can be checked for this. Reproducible: Always Steps to Reproduce: 1. Create two exports in a NFS 4.2 server in Fedora 37. 2.Created a sparse file which contains 16KB data followed by 32KB Hole multiple times in one of the exports. 3.Then mount both exports using NFS 4.2. 4.Start packet capture at server/client and copy file from one export to the other. 5.Check the packet capture for SEEK response and next NFS READ size. Actual Results: It will be visible that few holes are skipped. Expected Results: It should not skip holes sometimes and report correct data in SEEK response.
Created attachment 1973828 [details] capture of sparse file creation in NFS 4.2 mount of Fedora 37 server capture of sparse file creation in NFS 4.2 mount of Fedora 37 server. 10.52.72.77 is the NFS 4.2 Fedora 37 server Kernel version 6.1.6-200.fc37.x86_64
Created attachment 1973829 [details] file copy operation in NFS 4.2 mount in Fedora 37 server file copy operation in NFS 4.2 mount in Fedora 37 server. 10.52.72.77 is the server. 10.52.72.106 is the client (packet no 499,500,501) (1131,1132,1133) can be checked. Multiple similar packet is present later.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.