| 1 |
On Monday 08 February 2010 01:02:39 Alex Schuster wrote: |
| 2 |
> Walt Rarus writes: |
| 3 |
> > WALRUS ~ # whoami |
| 4 |
> > root |
| 5 |
> > WALRUS ~ # ls -l /usr/portage/x11-misc/icesndcfg/ |
| 6 |
> > ls: cannot access /usr/portage/x11-misc/icesndcfg/icesndcfg-1.3.ebuild: |
| 7 |
> > Permission denied |
| 8 |
> > total 12 |
| 9 |
> > -rw-r--r-- 1 root root 2675 2008-05-09 09:37 ChangeLog |
| 10 |
> > -rw-r--r-- 1 root root 771 2008-05-09 09:37 Manifest |
| 11 |
> > ?????????? ? ? ? ? ? icesndcfg-1.3.ebuild |
| 12 |
> > -rw-r--r-- 1 portage portage 224 2003-07-07 09:54 metadata.xml |
| 13 |
> > |
| 14 |
> > The situation with icesndcfg-1.3.ebuild above is disallowing a complete |
| 15 |
> > "emerge --sync". |
| 16 |
> > I don't know how to resolve the problem since even root can't |
| 17 |
> > access/overwrite this (bogus?) file. Any help available? |
| 18 |
> |
| 19 |
> Looks like a corrupted file system. A fsck might fix this. You can force |
| 20 |
> one by 'shutdown -Fr now'. Sync your portage tree after this to make sure |
| 21 |
> it is in a clean state. |
| 22 |
|
| 23 |
In my experience, fsck consistently detects file systems corruption, and |
| 24 |
consistently fails to do anything useful about it. |
| 25 |
|
| 26 |
However, it's pretty common for users to have made a separate volume for the |
| 27 |
portage tree (i.e. something mounted at /usr/portage). If so, just trash the |
| 28 |
thing, download a new-ish tarball of the tree, resync and you're back in |
| 29 |
business. |
| 30 |
|
| 31 |
-- |
| 32 |
alan dot mckinnon at gmail dot com |
Archives