Getting the volume active is a pain I found that you have to reboot the system and when it comes back you need to create a link your volume group directory for the snapshot you create, atleast after the reboot the snapshot device showup in /dev/mapper which is a start right. link it into your VG device home directory and then you can remove the snapshot, once you got the snapshot out of the way you can run lvchange -a y <lvname> to bring your original LV back online. Hope this makes sense. Daz ============================================================================== Darren Miller Senior Systems Support Engineer Microsoft Certified Professional SCO Advanced Certified Engineer Infomation Systems Department (Core Server Support) Philips Semiconductors,Milbrook Industrial Estate,Southampton,SO15 0DJ,England Direct Dial In: +44 (0) 2380 312681 <table width=100%> <tr valign=top> <td> <td> Rich Turner <rich@storix.com> Sent by: linux-lvm-bounces@redhat.com 23/03/2004 23:33 Please respond to LVM general discussion and development <td> To: LVM general discussion and development <linux-lvm@redhat.com> cc: (bcc: Darren Miller/SOU/SC/PHILIPS) Subject: [linux-lvm] snapshots and 2.6 kernel Classification: </table> i understand from numerous posts on this list and many others that snapshots in the 2.6 kernel is not yet supported. the lvm commands allow you to create the snapshot but do nothing with it. even worse, i am unable to remove the snapshot or get the original logical volume active. is there any progress in the 2.6 kernel supporting snapshots? is there any way to know if the snapshot will be valid before creating the snapshot (other than 'uname -r')? which is the culprit: device-mapper, lvm? _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/