since emerge --sync several days ago cache update fails and any attempt to use emerge is broken. The original error showed IOerror [error5] now it shows OSerror [error5] >>> Updating Portage cache: Traceback (most recent call last): File "/usr/bin/emerge", line 5289, in ? retval = emerge_main() File "/usr/bin/emerge", line 5246, in emerge_main action_sync(settings, trees, mtimedb, myopts, myaction) File "/usr/bin/emerge", line 3986, in action_sync action_metadata(settings, portdb, myopts) File "/usr/bin/emerge", line 4081, in action_metadata eclass_cache=ec, verbose_instance=noise_maker) File "/usr/lib/portage/pym/cache/util.py", line 22, in mirror_cache dead_nodes = dict.fromkeys(trg_cache.keys()) File "/usr/lib/portage/pym/cache/template.py", line 95, in keys return tuple(self.iterkeys()) File "/usr/lib/portage/pym/cache/flat_hash.py", line 110, in iterkeys for l in os.listdir(dirs[0]): OSError: [Errno 5] Input/output error: '/var/cache/edb/dep/usr/portage/new/net-a nalyzer' the appearance of "new" in that path suggests to me the breakage is due to a hardcoded use or /usr/portage somewhere. My PORTAGE_DIR=/usr/portage/new seems to be exposing a bug in portage. I currently have 2.1.2 installed. I cannot update to r9 since emerge is broken by the failed cache update. thx. Reproducible: Always
Check your filesystem and/or HDD, this is not a portage bug.
beg your pardon this was indeed an fs error.
