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