lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 13 Jun 2008 00:27:09 +0200 From: Miquel van Smoorenburg <mikevs@...all.net> To: Oliver Pinter <oliver.pntr@...il.com> Cc: lists@...gbr.de, linux-kernel@...r.kernel.org, Christoph Hellwig <hch@...radead.org>, xfs@....sgi.com, xfs-masters@....sgi.com, mikevs@...all.net Subject: Re: XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c On Thu, 2008-06-12 at 16:33 +0200, Oliver Pinter wrote: > add CC's > > On 6/12/08, lists@...gbr.de <lists@...gbr.de> wrote: > > Hi! > > > > Today morning my server at home bailed out two times (reboot between): > > Jun 12 07:23:40 zappa > > Jun 12 07:23:40 zappa xfs_force_shutdown(sda7,0x8) called from line > > 1164 of file fs/xfs/xfs_trans.c. Return address = 0xffffffff802f4d8a > > Jun 12 07:23:40 zappa Filesystem "sda7": Corruption of in-memory data > > detected. Shutting down filesystem: sda7 > > Jun 12 07:23:40 zappa Please umount the filesystem, and rectify the > > problem(s) Hmm, interesting. I'm seeing the same thing on one of my servers since I upgraded from 2.6.ancient (14 or so) to 2.6.25, while XFS otherwise has been very stable for me over the years: Linux transit5.news.xs4all.nl 2.6.25.6 #1 SMP Wed Jun 11 10:59:10 CEST 2008 x86_64 GNU/Linux Filesystem "sda4": XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c. Caller 0xffffffff880f1315 Pid: 3402, comm: diablo Not tainted 2.6.25.6 #1 Call Trace: [<ffffffff880f1315>] :xfs:xfs_create+0x1e5/0x520 [<ffffffff880ea4a6>] :xfs:xfs_trans_cancel+0x126/0x150 [<ffffffff880f1315>] :xfs:xfs_create+0x1e5/0x520 [<ffffffff880fcb79>] :xfs:xfs_vn_mknod+0x1d9/0x320 [<ffffffff8028811c>] vfs_create+0xac/0xf0 [<ffffffff8028b6bd>] open_namei+0x61d/0x6c0 [<ffffffff802448c0>] autoremove_wake_function+0x0/0x30 [<ffffffff8027da0c>] do_filp_open+0x1c/0x50 [<ffffffff8027d6e9>] get_unused_fd_flags+0x79/0x120 [<ffffffff8027da9a>] do_sys_open+0x5a/0xf0 [<ffffffff8020b2bb>] system_call_after_swapgs+0x7b/0x80 xfs_force_shutdown(sda4,0x8) called from line 1164 of file fs/xfs/xfs_trans.c. Return address = 0xffffffff880ea4bf Filesystem "sda4": Corruption of in-memory data detected. Shutting down filesystem: sda4 Please umount the filesystem, and rectify the problem(s) After a reboot, xfs_repair didn't find anything wrong with the fs. It has happened 3 times over the last few days already. FS is on a local SCSI raid (dpt_i2o), not SATA. Mike. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists