evilninja
2004-Mar-22 04:09 UTC
Assertion failure in ext3_put_super() at fs/ext3/super.c:412
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, today i re-organized my data, lots of "mv" and "cp". then, upon unmounting a ext3 partition the following was shown on the console: (the leading "Mar 22 02:40:04 sheep kernel:" is cut here) - ------------------------------- ~ sb orphan head is 940994 ~ sb_info orphan list: ~ inode sdd4:940994 at cf852874: mode 40755, nlink 0, next 486721 ~ inode sdd4:486721 at cfce8674: mode 40755, nlink 0, next 551857 ~ inode sdd4:551857 at cfce80d4: mode 40755, nlink 0, next 0 ~ Assertion failure in ext3_put_super() at fs/ext3/super.c:412: "list_empty(&sbi->s_orphan)" ~ ------------[ cut here ]------------ ~ kernel BUG at fs/ext3/super.c:412! ~ invalid operand: 0000 [#1] ~ PREEMPT ~ CPU: 0 ~ EIP: 0060:[<c0190de7>] Not tainted ~ EFLAGS: 00010286 ~ EIP is at ext3_put_super+0x137/0x1a0 ~ eax: 0000005e ebx: c138d364 ecx: 00000001 edx: c03255b8 ~ esi: c138d2e0 edi: cf8e5400 ebp: c1fb6000 esp: c1fb7f10 ~ ds: 007b es: 007b ss: 0068 ~ Process umount (pid: 21926, threadinfo=c1fb6000 task=cfa20c00) ~ Stack: c02f9d80 c02e82eb c02f702e 0000019c c02f7013 cf8e544c cf8e5400 c0329ca0 ~ c0157526 cf8e5400 cf8e5400 cf824060 c0329e20 c015811d cf8e5400 0804d218 ~ cf8e5400 c1fb6000 c015725f cf8e5400 c03bfee0 00000000 c1fb7f7c 0804d218 ~ Call Trace: ~ [<c0157526>] generic_shutdown_super+0x176/0x190 ~ [<c015811d>] kill_block_super+0x1d/0x40 ~ [<c015725f>] deactivate_super+0x5f/0xc0 ~ [<c016d4af>] sys_umount+0x3f/0xa0 ~ [<c016d525>] sys_oldumount+0x15/0x20 ~ [<c010908b>] syscall_call+0x7/0xb ~ Code: 0f 0b 9c 01 2e 70 2f c0 e9 60 ff ff ff 89 74 24 04 89 3c 24 - ------------------------------- the filesystem here was existing for a year now, passed regular checks and did not show any corruptions. it has never shown anything similar in the logs and i was not able to reproduce it. i have to add, that i did something strange before unmounting. the partition was mounted under "/data", but "umount /data" failed (busy). "lsof" has shown some files locked by the apache webserver marked "deleted". it was true, i mv'ed files to another place, apache was still running and apparently locking files. i then killed the apache process, no locked files any more, so i was able to "umount /data" --> then the error shown above happened. after the error i was not able to "/bin/sync" nor to SYSRQ+S, i had to reboot. probably not a bug, but i found it worth to report. this all happend with a vanilla 2.6.4 (not tainted), compiled with gcc-3.3.3 on i386 (Pentium3), IBM-ESXS disks. Thanks, Christian. - -- BOFH excuse #87: Password is too complex to decrypt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAXmbwC/PVm5+NVoYRApOyAJ45VhXeIS/FFTrF+lxTOs1mhGgzHQCfc2vY pOeQTaJKs9pPRjhuDGLSdXM=sZpV -----END PGP SIGNATURE-----
Stephen C. Tweedie
2004-Mar-31 12:45 UTC
Assertion failure in ext3_put_super() at fs/ext3/super.c:412
Hi, On Mon, 2004-03-22 at 04:09, evilninja wrote:> today i re-organized my data, lots of "mv" and "cp". > then, upon unmounting a ext3 partition the following was shown on the > console:> ~ Assertion failure in ext3_put_super() at fs/ext3/super.c:412: > "list_empty(&sbi->s_orphan)"There's a bug we've been chasing recently regarding a race between link/rename and unlink. We know what's going wrong, it's just a matter of determining what the right fix is (there's a workaround in a couple of filesystems but it doesn't seem to be quite the right fix.) It could well be the cause of your problem, as the symptoms on ext3 normally manifest as orphan list corruption. --Stephen