[linux-lvm] Isolation of volume groups

Bryn M. Reeves bmr at redhat.com
Mon May 28 15:09:24 UTC 2012

Hash: SHA1

On 05/28/2012 03:33 PM, Fredrik Tolf wrote:
> Last night, one of the PVs in datvol had a transient SATA link
> failure and popped in and out of existence for a little while,
> which caused datvol and the LVs on it to fail. No permanent damage
> seems to have occurred, though, so I'm not too worried about that.
> I could bring datvol down and up again to make it work, so I guess
> everything worked as should be expected.

Are the devices for ravol and datvol on the same SATA bus or controller?

> What concerns me a little, however, is that ravol also seems to
> have been oddly affected by the failure of datvol. At times, the
> filesystems on it could hang for seconds, not responding; and while
> it was responding, XFS was intermittently outputting messages like
> May 28 14:58:58 nerv kernel: [30350.996032] 
> xfs_force_shutdown(dm-33,0x1) called from line 335 of file 
> /build/buildd-linux-2.6_2.6.32-38-amd64-bk66e4/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/xfs/xfs_rw.c.
>  Return address = 0xffffffffa01df02c

> May 28 14:51:38 nerv kernel: [29911.468028] Filesystem "dm-33": 
> xfs_log_force: error 5 returned.

Errno 5 is EIO:

/usr/include/asm-generic/errno-base.h:#define	EIO		 5	/* I/O error */

So something below XFS returned EIO. This could happen due to IO
timeouts caused by link reset and error recovery on the other SATA device.

Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


More information about the linux-lvm mailing list