Summary: | Emerge failing with Input/output error | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Mike Wood <mwoodj> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mike Wood
2013-05-30 16:30:57 UTC
This is a hardware problem not a portage issue I am getting it too, on a raidz2 setup with six disks that are all reported online with no failures; additionally smart also reports there is no error. This also occured with me, more than once, during a long emerge run. It certainy is not a hardware issue; a zfs scrub reports there are no failures, and raidz2 allows two disks to fail. My machine has plenty of RAM and thus I suspect that the error must be caused by something in portage. (In reply to mwoodj@knology.net from comment #0) > In my system I have 1 SSD and 2 HDD's that are configured in a RAID1 > configuration (mdadm). My partition layout is: > > / on SSD > /var on HDD RAID1 > /tmp on tmpfs What filesystem do you use on /var ? ext4 I was also getting this error every time I tried to update Firefox to version 21. Happened twice. I then tried to use equery to find my portage version (it's 2.1.12.2) so I could comment on this bug, and it gave me an error about gentoolkit not being found. I rebuilt gentoolkit, and then Firefox I have a 16 GiB tmpfs mounted to /var/tmp, and my main hard disk is a 512 GB SSD. (In reply to Mark W. Gabby II from comment #5) > being found. I rebuilt gentoolkit, and then Firefox That should be "Firefox built successfully" after I updated gentoolkit. Important information is missing here. If it turns out not to be a filesystem error, then at least it is the filesystem driver that is at fault (like an -ENOENT where it should return an -EAGAIN) and there is little we can do about it unless we see more specific information. Also, I am not convinced that comment #2 and comment #5 are reports of the same issue, since "OSError: [Errno 5] Input/output error" actually doesn't tell us enough about what is going on. It could be a problem in the IPC code in sys-apps/portage or it could be something else. It's got nothing to do with your filesystem unless you're redirecting stdout to a file like `emerge > output.log`. People in bug 459674 have been reporting this issue when stdout is a tty. *** This bug has been marked as a duplicate of bug 459674 *** |