Bug 751992
Summary: | mount.nfs4: Cannot allocate memory | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Stancek <jstancek> |
Component: | kernel | Assignee: | nfs-maint |
Status: | CLOSED DUPLICATE | QA Contact: | Filesystem QE <fs-qe> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2 | CC: | arozansk, bfields, dhowells, eguan, fhrbata, jburke, jiali, jlayton, kzhang, rvandolson, rwheeler, sprabhu, steved, yanwang |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-03-15 13:48:00 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: | |||
Bug Depends On: | |||
Bug Blocks: | 767187 |
Description
Jan Stancek
2011-11-08 09:20:39 UTC
Looks like struct idmap is about 40k on a 64-bit architecture. I wonder whether it would be possible to make the transition to the new idmapper on rhel6? That would solve a number of problems. (In reply to comment #3) > Looks like struct idmap is about 40k on a 64-bit architecture. > > I wonder whether it would be possible to make the transition to the new > idmapper on rhel6? That would solve a number of problems. I agree... lets how enabling the new idmapper in upstream and rawhide pans out... If well, we should consider enabling the code in 6.3... imho... I believe this is impacting me as well although the triggering process is mount.nfs rather than mount.nfs4. Have opened SR #612178 for the issue with Red Hat Support. Are there any workarounds for this issue currently? If the bug is duplicate with bug 730045? (In reply to comment #7) > If the bug is duplicate with bug 730045? Yeah... *** This bug has been marked as a duplicate of bug 730045 *** Any chance of making bug 730045 public? |