| Summary: | fuse-bridge.c error | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Joe Julian <joej> | ||||||||
| Component: | unclassified | Assignee: | Vijay Bellur <vbellur> | ||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | |||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 2.0.2 | CC: | aavati, csaba, gluster-bugs, joej, vijay | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | Type: | --- | |||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
Running Fedora 11 kernel 2.6.30.8-64.fc11.x86_64 stock fuse. Using the attached vol file. My log is filling with: [2009-10-14 10:01:57] W [fuse-bridge.c:2278:fuse_setlk_cbk] glusterfs-fuse: 5740974: ERR => -1 (Resource temporarily unavailable) Another Fedora 4 box has the same volume mounted and has not produced this error. Created attachment 84 [details]
patch to make tmpwatch support --ctime
(In reply to comment #0) > Created an attachment (id=81) [details] > Vol file > > Running Fedora 11 kernel 2.6.30.8-64.fc11.x86_64 stock fuse. > > Using the attached vol file. > > My log is filling with: > [2009-10-14 10:01:57] W [fuse-bridge.c:2278:fuse_setlk_cbk] glusterfs-fuse: > 5740974: ERR => -1 (Resource temporarily unavailable) > > Another Fedora 4 box has the same volume mounted and has not produced this > error. Can you please provide the version of fuse that you are using with Fedora 4? Thanks, Vijay (In reply to comment #3) > (In reply to comment #0) > > Can you please provide the version of fuse that you are using with Fedora 4? > > Thanks, > Vijay I did make a mistake and the working machine was actually Fedora 6. Fuse version is fuse-2.7.0-6.fc6 Aha. This is actually a server side issue. Unfortunately, I wasn't able to track down any more details than that. A deadlock on the F6 client prompted me to restart all the servers and this error went away. I think this error message is incomplete. There needs to be enough information to recognize the source of the error. (In reply to comment #5) > Aha. This is actually a server side issue. Unfortunately, I wasn't able to > track down any more details than that. Yes, it looks like the error message appears in fuse but it's just forwarded on from other xlators. Csaba (In reply to comment #5) Hi Julian, Are you hitting this issue again? If yes, can you please provide us the client and server log files? Also, can you please try with a new release like 2.0.8? We have had some fixes in locks which may alleviate the situation. Thanks, Vijay This bug can be reopened when somebody is able to reproduce it. At this time, it is not reproducible by anybody. |
Created attachment 82 [details] Patch which adds a missing \n\