I am very confused about this bug and don't know if it is bug of portage or xfs. today successfuly upgraded many packages, (also kde and kernel-sources and got no problems) but have problem with portage, when trying to emerge it got this: emerge portage Calculating dependencies... done! >>> Emerging (1 of 1) sys-apps/portage-2.1.2_pre3-r4 to / * portage-2.1.2_pre3.tar.bz2 MD5 ;-) ... [ ok ] * portage-2.1.2_pre3.tar.bz2 RMD160 ;-) ... [ ok ] * portage-2.1.2_pre3.tar.bz2 SHA1 ;-) ... [ ok ] * portage-2.1.2_pre3.tar.bz2 SHA256 ;-) ... [ ok ] * portage-2.1.2_pre3.tar.bz2 size ;-) ... [ ok ] * portage-2.1.2_pre3-r4.patch.bz2 MD5 ;-) ... [ ok ] * portage-2.1.2_pre3-r4.patch.bz2 RMD160 ;-) ... [ ok ] * portage-2.1.2_pre3-r4.patch.bz2 SHA1 ;-) ... [ ok ] * portage-2.1.2_pre3-r4.patch.bz2 SHA256 ;-) ... [ ok ] * portage-2.1.2_pre3-r4.patch.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking portage-2.1.2_pre3.tar.bz2 ;-) ... [ ok ] * checking portage-2.1.2_pre3-r4.patch.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking portage-2.1.2_pre3.tar.bz2 to /usr/portage/tmp/portage/sys-apps/portage-2.1.2_pre3-r4/work >>> Unpacking portage-2.1.2_pre3-r4.patch.bz2 to /usr/portage/tmp/portage/sys-apps/portage-2.1.2_pre3-r4/work * Applying portage-2.1.2_pre3-r4.patch ... [ ok ] * Setting portage.VERSION to 2.1.2_pre3-r4 ... [ ok ] >>> Source unpacked. >>> Compiling source in /usr/portage/tmp/portage/sys-apps/portage-2.1.2_pre3-r4/work/portage-2.1.2_pre3 ... >>> Source compiled. >>> Test phase [not enabled]: sys-apps/portage-2.1.2_pre3-r4 >>> Install portage-2.1.2_pre3-r4 into /usr/portage/tmp/portage/sys-apps/portage-2.1.2_pre3-r4/image/ category sys-apps patching file make.conf >>> Completed installing portage-2.1.2_pre3-r4 into /usr/portage/tmp/portage/sys-apps/portage-2.1.2_pre3-r4/image/ man: gzipping man page: quickpkg.1 gzipping man page: emaint.1 gzipping man page: emerge.1 gzipping man page: repoman.1 gzipping man page: env-update.1 gzipping man page: dispatch-conf.1 gzipping man page: ebuild.1 gzipping man page: etc-update.1 gzipping man page: portage.5 gzipping man page: make.conf.5 gzipping man page: ebuild.5 strip: i686-pc-linux-gnu-strip --strip-unneeded usr/lib/portage/bin/tbz2tool >>> Merging sys-apps/portage-2.1.2_pre3-r4 to / --- /etc/ >>> /etc/make.globals --- /etc/env.d/ >>> /etc/env.d/05portage.envd >>> /etc/etc-update.conf >>> /etc/dispatch-conf.conf >>> /etc/make.conf.example --- /etc/portage/ >>> /etc/portage/.keep_sys-apps_portage-0 --- /usr/ --- /usr/bin/ !!! 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 ******and in dmesg got this: xfs_da_do_buf: bno 16777216 dir: inode 12606381 Filesystem "hda6": XFS internal error xfs_da_do_buf(1) at line 1992 of file fs/xfs/xfs_da_btree.c. Caller 0xc018934a [<c0188f85>] xfs_da_do_buf+0x34f/0x6b7 [<c018934a>] xfs_da_read_buf+0x19/0x1e [<c0191ecc>] xfs_dir2_leafn_lookup_int+0x2b9/0x448 [<c018dba7>] xfs_dir2_data_log_unused+0x42/0x49 [<c018934a>] xfs_da_read_buf+0x19/0x1e [<c0190877>] xfs_dir2_node_removename+0x266/0x463 [<c0190877>] xfs_dir2_node_removename+0x266/0x463 [<c018bcee>] xfs_dir_removename+0xce/0xd5 [<c01a3a34>] xfs_log_reserve+0x493/0x4cc [<c01b6cd0>] kmem_zone_zalloc+0x1f/0x41 [<c01b43ea>] xfs_remove+0x235/0x39b [<c01bc49e>] xfs_vn_unlink+0x17/0x3b [<c014919a>] sys_lstat64+0x1e/0x23 [<c0153a2b>] __d_lookup+0x8d/0xc1 [<c014c752>] may_delete+0x32/0xe3 [<c014cb33>] vfs_unlink+0x42/0x7d [<c014e1fe>] do_unlinkat+0x85/0x113 [<c0102a05>] sysenter_past_esp+0x56/0x79 Filesystem "hda6": XFS internal error xfs_trans_cancel at line 1138 of file fs/xfs/xfs_trans.c. Caller 0xc01b452a [<c01ac85e>] xfs_trans_cancel+0x4d/0xd6 [<c01b452a>] xfs_remove+0x375/0x39b [<c01b452a>] xfs_remove+0x375/0x39b [<c01bc49e>] xfs_vn_unlink+0x17/0x3b [<c014919a>] sys_lstat64+0x1e/0x23 [<c0153a2b>] __d_lookup+0x8d/0xc1 [<c014c752>] may_delete+0x32/0xe3 [<c014cb33>] vfs_unlink+0x42/0x7d [<c014e1fe>] do_unlinkat+0x85/0x113 [<c0102a05>] sysenter_past_esp+0x56/0x79 xfs_force_shutdown(hda6,0x8) called from line 1139 of file fs/xfs/xfs_trans.c. Return address = 0xc01bed48 Filesystem "hda6": Corruption of in-memory data detected. Shutting down filesystem: hda6 Please umount the filesystem, and rectify the problem(s)
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.
