xfs
[Top] [All Lists]

Lockup with LVM snapshot

To: xfs mailing list <linux-xfs@xxxxxxxxxxx>
Subject: Lockup with LVM snapshot
From: Greg Freemyer <freemyer@xxxxxxxxxxxxxxxxx>
Date: Thu, 31 Oct 2002 11:38:35 -0500
Organization: The NorcrossGroup
Sender: linux-xfs-bounce@xxxxxxxxxxx
I have a test machine which has started locking up when I run my backup script.

The script creates a LVM snapshot for each of 3 LVs in turn and then uses 
xfsdump to back them up.

After the lockup, nothing seems to work, but the keyboard lights are flashing.

I'm running a pure CVS kernel from Sept. 6.

My warn.log file has:

Oct 20 01:15:22 TruStore1000 kernel: XFS mounting filesystem lvm(58,4)
Oct 20 01:15:28 TruStore1000 kernel: lvm - lvm_map: ll_rw_blk write for 
readonly LV /dev/TruStore-Data/config_snap
Oct 20 01:15:28 TruStore1000 kernel: I/O error in filesystem ("lvm(58,4)") 
meta-data dev 0x3a04 block 0x1a5c8
Oct 20 01:15:28 TruStore1000 kernel:     ("xlog_iodone") error 5 buf count 2560
Oct 20 01:15:28 TruStore1000 kernel: xfs_force_shutdown(lvm(58,4),0x2) called 
from line 949 of file xfs_log.c.  Return address = 0xc022b827
Oct 20 01:15:28 TruStore1000 kernel: Log I/O Error Detected.  Shutting down 
filesystem: lvm(58,4)
Oct 20 01:15:28 TruStore1000 kernel: Please umount the filesystem, and rectify 
the problem(s)
Oct 20 01:15:29 TruStore1000 kernel: XFS mounting filesystem lvm(58,3)

The filesystem config_snap has already been deleted.

I have not tried to reproduce this, but I suspect I can.  It has happened twice 
so far.

Is it likely a updated CVS kernel would fix this?

Is there more data I can provide?

Thanks,
Greg
=============
Greg Freemyer
Internet Engineer
Deployment and Integration Specialist
Compaq ASE - Tru64 v4, v5
Compaq Master ASE - SAN Architect
The Norcross Group
www.NorcrossGroup.com


<Prev in Thread] Current Thread [Next in Thread>