Created attachment 1013568 [details] kernel WARNING stack trace Description of problem: kernel: WARNING: CPU: 0 PID: 68 at fs/nfs/direct.c:132 nfs_direct_good_bytes+0xa1/0xc0 [nfs] Version-Release number of selected component (if applicable): * Client fedora rawhide 4.0.0-0.rc5.git4.1.fc23.x86_64 * Primary Data MDS b630 3.11.9-integration-630-90182a7f How reproducible: Reproduced twice Steps to Reproduce: Reproduced using an internal tool - the following is the test flow outline: 01. Mount flex-files MDS (configured to returns layouts with 2 mirrors) 02. Writing to files to provide data to read later 03. Closing files after writing to them 04. Clearing clients' cache 05. Opening files in read-only mode (O_RDONLY | O_SYNC | O_DIRECT) 06. Performing I/O to trigger LAYOUTGET (is_write: False) 07. Clearing clients' cache 08. Initiating disaster DisasterTypes.NETWORK_PARTITION (Client drops packets goings to DS #0) 09. Performing early main I/O - right after the disaster strikes (is_write: False) 10. Sleeping for 420s 11. Ending disaster condition (unblock IP) 12. Waiting for all the clients to complete I/O Actual results: kernel: WARNING: CPU: 0 PID: 68 at fs/nfs/direct.c:132 nfs_direct_good_bytes+0xa1/0xc0 [nfs] Expected results: * I/O successful * No warnings emitted
Fixing patch: http://www.spinics.net/lists/linux-nfs/msg50655.html
That patch has been sitting uncommented on a for a while now. I poked the upstream thread to see if why. Out of curiosity, did you happen to build a kernel with those and test?
OK, this patch finally went upstream. It should be in the 4.1-rc1 build today.
Fixed in rawhide and in git for F22.
kernel-4.0.1-300.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/kernel-4.0.1-300.fc22
Verified on rawhide running kernel 4.1.0-0.rc1.git0.1.fc23.x86_64
kernel-4.0.1-300.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.