Bug 821081
| Summary: | F17 alpha PPC64: Running fsracer test on NFSv4 mounted file system generated call trace | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | IBM Bug Proxy <bugproxy> | ||||||||||
| Component: | kernel | Assignee: | Jeff Layton <jlayton> | ||||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | low | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 17 | CC: | bfields, braden, gansalmon, graeme.russ, itamar, jherbold, jiali, jkachuck, jlayton, jonathan, kernel-maint, lsof, madhu.chinakonda, ovasik, steved, wgomerin | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | ppc64 | ||||||||||||
| OS: | All | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2013-01-03 13:51:39 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
IBM Bug Proxy
2012-05-11 20:00:41 UTC
Created attachment 583914 [details]
dmesg.txt
Created attachment 583915 [details]
var-log-messages.txt
Created attachment 583916 [details]
more-details-log.txt
Filesystem package has nothing to do with filesystems generally. Let's go with nfs-utils (and Steve Dickson) for further reassignment. hi IBM, could you provide fsracer test? ------- Comment From maknayak.com 2012-05-14 06:47 EDT------- (In reply to comment #12) > hi IBM, > could you provide fsracer test? Hello RedHat, Attached tar ball of racer test named "racer.tar.gz". Thanks... Manas Created attachment 584257 [details]
racer.tar.gz
------- Comment (attachment only) From maknayak.com 2012-05-14 06:48 EDT-------
(In reply to comment #7) > Created attachment 584257 [details] > racer.tar.gz > > > ------- Comment (attachment only) From maknayak.com 2012-05-14 06:48 > EDT------- Thanks very much lijian ------- Comment From kamaleshb.com 2012-05-25 05:58 EDT------- Hi RedHat, Any updates on the bug ? Thanks. Are you seeing any other symptoms? Or just the warning? ------- Comment From maknayak.com 2012-05-29 15:36 EDT------- (In reply to comment #17) > Are you seeing any other symptoms? Or just the warning? I am getting only warnings , did not notice any other issue yet. Thanks... Manas ------- Comment From kamaleshb.com 2012-06-25 13:40 EDT------- == Comment: #21 -Sanjeev Patro <sanpatr1.com> -2012-06-21 03:33:52 == We tested with F17 PPC64 GA build, this issue is still persists. Looks like a sillyrename cleanup raced with an unlink on the server or something. The file got removed and the nlink count on the server went to 0 and the client updated the inode attributes. Later, when we went to clean up the sillyrename we tried to decrement the nlink counter but it was already 0 and we got this warning. The right fix is probably to make the client not use drop_nlink on a delete. Simply mark the attribute cache as needing to be updated afterward. That has implications for how the inode cache is managed though and will need to be considered carefully. *** Bug 854050 has been marked as a duplicate of this bug. *** Resetting the severity to "low". This is not an urgent issue. The warning is harmless, though it might look a little scary... *** Bug 873510 has been marked as a duplicate of this bug. *** *** Bug 881933 has been marked as a duplicate of this bug. *** *** Bug 886775 has been marked as a duplicate of this bug. *** Looks like we may have a fix queueing up for 3.8:
https://patchwork.kernel.org/patch/1880501/
https://patchwork.kernel.org/patch/1880511/
...and somewhat related:
https://patchwork.kernel.org/patch/1881281/
(In reply to comment #19) > Looks like we may have a fix queueing up for 3.8: > > https://patchwork.kernel.org/patch/1880501/ > https://patchwork.kernel.org/patch/1880511/ > > ...and somewhat related: > > https://patchwork.kernel.org/patch/1881281/ None of them appear to be CC'd to stable.... is that something that should happen? This warning is scary-looking and somewhat of a nuisance, but it's mostly harmless. 3.8 seems fine to me... Since this is in 3.8, I'm going to go ahead and close with a resolution of UPSTREAM. |