Ok, I tried adding quota to the mix, and it still doesn't fall down for
me... Do you guys have some other XFS changes in the mix?
-Eric
# This works for me:
# create logical volume
vgcreate volgroup /dev/sda2 /dev/sda3
lvcreate -L 100M -n logicalvol volgroup
# mkfs and mount it:
umount /dev/volgroup/logicalvol
mkfs.xfs -f /dev/volgroup/logicalvol
mount -o quota /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 ro,nouuid,norecovery /dev/volgroup/snap1 /mnt/lvm/snap1
mount -o ro,nouuid,norecovery /dev/volgroup/snap2 /mnt/lvm/snap2
# Overflow the snapshots:
cp -aR /usr/src/linux-2.4.9-13SGI_XFS_1.0.2/ /mnt/lvm/logicalvol
# Unmount the snapshots:
umount /mnt/lvm/snap1/
umount /mnt/lvm/snap2/
On Mon, 2002-02-25 at 14:19, Stephenson, Dale wrote:
> Eric,
>
> I followed your steps and did not get the oops. It seems that the mount
> options on the original xfs source volume matter. I was able to recreate
> the oops with the same steps by mounting with quota support.
>
> mount -o quota /dev/volgroup/logicalvol /mnt/lvm/logicalvol
> or
> mount -o usrquota,grpquota,quota /dev/volgroup/logicalvol
> /mnt/lvm/logicalvol
>
> I also found (accidentally) that after the first snapshot umount goes
> through xfs_force_shutdown(), an oops can be triggered by umounting the
> original source volume--not just umounting its other snapshot. It doesn't
> xfs_force_shutdown the source volume, but oops in the same spot just the
--
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc.
|