| Summary: | $PKGDIR needs locking | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Robin Johnson <robbat2> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
*bump* patch? :) Is this urgent need for locking still the case in 2013? Has this been implemented in another way? Do we still need this to happen? This is one of the five oldest untouched open bugs, therefore please review this bug; thank you! :) Symlinks are no longer used, so maybe locking is no longer needed either? |
$PKGDIR urgently needs locking added to it. When mv is moving the file between devices, it is nessicarily atomic. For large binpkgs, this is significent as the window can be quite large. We need to acquire a lock for $PKGDIR/All/${PF}.tbz2 right before we try to move, and release it after we have created the symlink. I've run into this with a $PKGDIR shared via NFS for a large cluster.