On Mon, Jun 17, 2013 at 06:38:56PM +0400, Vlad Bespalov wrote: > CentOS 6.4 kernel 2.6.32-358.2.1.el6.x86_64 > i`ll try to make a script that can be used out-of-house. > > several requests may have failed (un)conveniently, so we have passed > through setting XLOG_IO_ERROR in xfs_log_force_unmount() and > eventually skipped xlog_wait altogether: > ----------------- > <1>XFS (<device>): metadata I/O error: block 0xa03e1d ("xlog_iodone") > error 5 buf count 1024 > <5>XFS (<device>): xfs_do_force_shutdown(0x2) called from line 1052 of > file fs/xfs/xfs_log.c. Return address = 0xffffffffa0559e51 > <1>XFS (<device>): Log I/O Error Detected. Shutting down filesystem > <1>XFS (<device>): Please umount the filesystem and rectify the problem(s) > <4>XFS (<device>): xfs_log_force: error 5 returned. > <5>XFS (<device>): xfs_do_force_shutdown(0x1) called from line 1063 of > file fs/xfs/linux-2.6/xfs_buf.c. Return address = 0xffffffffa0575 > <4>XFS (<device>): xfs_log_force: error 5 returned. > <4>XFS (<device>): xfs_log_force: error 5 returned. > ... > <1>XFS (mtab~): metadata I/O error: block 0xa03e1b ("xlog_iodone") > error 5 buf count 1024 And the rest of dmesg showing the stack trace of the oops? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs