Summary: | emerging sys-apps/portage-2.1.2_pre3-r4 and xfs crash | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Dmitry <work> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED CANTFIX | ||
Severity: | critical | ||
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dmitry
2006-10-18 10:46:41 UTC
That looks like a kernel side issue. It's possibly a bug in the xfs driver. (In reply to comment #1) > That looks like a kernel side issue. It's possibly a bug in the xfs driver. > but today i upgradet lot of packages, also kdebase, kdelibs and kernel sources, and got no problems, all compiled cleanly. from that, what i got from dmesg, i understand, that problem is in xfs. but, why only with portage ebuild? why all others ebuilds compiled cleanly? how can i provide more info, which information is needed from me to find solution for this bug? sorry, for stupid questions, but i don't have expirince in debugging and development. my /usr partition is xfs with notail 2.6.18-ck1-r1 #1 Wed Oct 18 15:50:01 EEST 2006 i686 AMD Athlon(tm) XP 2800+ AuthenticAMD GNU/Linux gcc (GCC) 4.1.1 (Gentoo 4.1.1-r1) sys-libs/glibc-2.5 sys-apps/portage-2.1.2_pre3-r3 sys-fs/xfsprogs-2.8.11 (In reply to comment #0) > !!! failed to properly create symlink: > !!! /usr/bin/xpak -> ../lib/portage/bin/xpak > !!! [Errno 5] Input/output error: '/usr/bin/xpak' > !!! Failed to move file. > !!! /usr/bin/xpak -> ../lib/portage/bin/xpak The problem is only triggered with the portage ebuild because there is something wrong with the inode for /usr/bin/xpak, specifically. (In reply to comment #2) > which information is needed from me to find > solution for this bug? sorry, for stupid questions, but i don't have expirince > in debugging and development. A good first step would be to try some maintenance tools from the xfsprogs package. |