Hi Dale - a quick try at reproducing this here was unsuccessful. This
is what I did:
Create volume group & logical volume:
vgcreate volgroup /dev/sda2 /dev/sda3
lvcreate -L 100M -n logicalvol volgroup
mkfs and mount it:
mkfs.xfs -f /dev/volgroup/logicalvol
mount /dev/volgroup/logicalvol /mnt/lvm/logicalvol
Make a couple snapshots and mount them:
lvcreate --size 16m --snapshot --name snap1 /dev/volgroup/logicalvol
lvcreate --size 16m --snapshot --name snap2 /dev/volgroup/logicalvol
mount -o nouuid,ro,norecovery /dev/volgroup/snap1 /mnt/lvm/snap1
mount -o nouuid,ro,norecovery /dev/volgroup/snap2 /mnt/lvm/snap2
Overflow the snapshots:
cp -vaR /usr/src/linux-2.4.9-13SGI_XFS_1.0.2/ .
Unmount the snapshots:
umount /mnt/lvm/snap1/
umount /mnt/lvm/snap2/
I got no I/O errors or oopses... This is with a fresh CVS checkout from
today.
-Eric
On Mon, 2002-02-25 at 10:44, Stephenson, Dale wrote:
> At Keith Owens' suggestion, I've rerun the oops output using the System Map
> and a more recent ksymoops.
> This oops was generated by filling two mounted LVM snapshots of an XFS
> filesystem, and then umounting them both. Both umounts resulted in I/O
> errors and xfs_force_shutdown calls, and the second umount oopsed. The
> snapshots are a read only device, and they were mounted
> ro,nouuid,norecovery.
--
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc.
|