| Summary: | Unhandled IO error in NFS on Solaris: IOError: [Errno 46] No record locks available | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Richard Yao (RETIRED) <ryao> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | prefix |
| Priority: | Normal | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Solaris | ||
| URL: | http://docs.oracle.com/cd/E19455-01/806-1075/msgs-1784/index.html | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 462382 | ||
| Attachments: | Failure from one of the affected ebuilds | ||
Handle ENOLCK with loop: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=22846f84ec1a8daf6873c67224d78186be1ecce5 Prefix portage with fix committed This is fixed in 2.1.11.59 and 2.2.0_alpha170. |
Created attachment 342910 [details] Failure from one of the affected ebuilds I was rebuilding world with --jobs on Solaris when several builds failed because of an IOError. Oracle's documentation says: Perhaps a process called fcntl(2) with the F_SETLK or F_SETLKW option, and the system maximum was exceeded. The system contains several different locking subsystems, including fcntl(2), the NFS lock daemon, and mail locking. All subsystems can produce this error. EPREFIX was on NFS while PORTAGE_TMPDIR was on UFS.