|
Red Hat Bugzilla – Full Text Bug Listing |
| Summary: | NFSv4 regression: kernel write()'s status EACCES instead of 0 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Meflah Abdelkader <meflah_kader> | ||||||
| Component: | nfs-utils | Assignee: | Steve Dickson <steved> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 8 | CC: | jlayton | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i386 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-01-09 01:24:59 EST | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | ||||||||
| Attachments: |
|
||||||||
|
Description
Meflah Abdelkader
2008-04-23 12:00:00 EDT
Created attachment 303520 [details]
log of the test on client
I realize writing a reproducer should be trivial, but if you could post the one your using, it would start us on the same page... Our test uses a server supporting CIFS and NFSv4. The test uses a simulated CIFS client (samba). The first lock is got by a CIFS client. The read/write IOs are done by an NFS client. If your server supports CIFS and NFS then I will send you the test. So you need to set some variables in the scripts Yes, I have server that will support both CIFS and NFSv4, so please go ahead an post your test. tia... Created attachment 303966 [details]
3 files: shell to mount/umount FSs, shell to start test and main linux binary
already commented
Here is joined a zipped tar file tests.tar.zip
The directory contains 3 files:
mountUmount.sh: shell to mount/umount FSs
lock.csh: shell to start test
locktest: Linux test binary called by previous lock.csh
1/ fill the 4 CIFS variables flaged by xxxxx
2/ mountUmount.sh {<unixServerName> <unixFsName> <shareName> | umount }
3/ lock.csh "14(2)"
Question: does the CIFS server have to be the same box? It appears so... I think so, since we want the same file be exported to both protocols. PS: I'll be out of office from 15 to 30 May Does this still happen with the latest F8 kernel? it still happens with F9 kernel (2.6.25.11-97.fc9.i686) This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. 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 WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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 please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |