[TriLUG] LVM on Ubuntu failure after dist upgrade

[Jeffery Painter]

No, I apologize... it didn't come through and I couldn't remember
which account I had registered under.

Anyway... I found the solution:

  vgmknodes  recreated the /dev entries from an existing LVM group

Sorry for the double post.

--
Jeff

On Fri, Sep 30, 2011 at 12:36 PM, William Sutton <william at trilug.org> wrote:
> was the double post under different titles from different email accounts
> necessary?
>
> William Sutton
>
> On Fri, 30 Sep 2011, Jeffery Painter wrote:
>
>> Hello Triluggers,
>>
>> I need some help from those more experienced with LVM management than
>> myself, or at least point me to the right terms to google.
>>
>> I just upgraded my Ubuntu box from 9.04 all the way up to 11.10.
>> Everything went fine until the last reboot.
>>
>> /etc/fstab had an entry for...
>> /dev/backups/share     /backups        ext3    rw,noatime      0       0
>>
>> however, /dev/backups/share has disappeared as a device. How do I
>> recreate it without destroying the data on the LVM itself?
>>
>> I can still see the volume group:
>> root at stgdb:~# vgdisplay
>> File descriptor 3 (pipe:[10728]) leaked on vgdisplay invocation.
>> Parent PID 2164: -su
>> --- Volume group ---
>> VG Name               backups
>> System ID
>> Format                lvm2
>> Metadata Areas        3
>> Metadata Sequence No  4
>> VG Access             read/write
>> VG Status             resizable
>> MAX LV                0
>> Cur LV                1
>> Open LV               0
>> Max PV                0
>> Cur PV                3
>> Act PV                3
>> VG Size               1.41 TiB
>> PE Size               4.00 MiB
>> Total PE              369624
>> Alloc PE / Size       307200 / 1.17 TiB
>> Free  PE / Size       62424 / 243.84 GiB
>> VG UUID               OG1HUA-t86u-rBoc-0iK3-3Kmi-mtCZ-E1mN7S
>>
>>
>> and lvscan reports:
>>
>> root at stgdb:~# lvscan
>> File descriptor 3 (pipe:[10728]) leaked on lvscan invocation. Parent
>> PID 2164: -su
>> ACTIVE            '/dev/backups/share' [1.17 TiB] inherit
>>
>>
>> The physical layout of the LVM was created from:
>> /dev/sdb1
>> /dev/sdc1
>> /dev/sdd1
>>
>> The drives seem to be fully functional.. fdisk reports that all the
>> partitions are still there and of type LVM
>>
>> dmesg says...
>>
>> [    3.597896]  sdb: sdb1
>> [    3.598367] sd 1:0:0:0: [sdb] Attached SCSI disk
>> [    4.073100] sd 2:0:0:0: Attached scsi generic sg2 type 0
>> [    4.073614] sd 2:0:0:0: [sdc] 781422768 512-byte logical blocks:
>> (400 GB/372 GiB)
>> [    4.073707] sd 2:0:0:0: [sdc] Write Protect is off
>> [    4.073712] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
>> [    4.073749] sd 2:0:0:0: [sdc] Write cache: enabled, read cache:
>> enabled, doesn't support DPO or FUA
>> [    4.091543]  sdc: sdc1
>> [    4.091977] sd 2:0:0:0: [sdc] Attached SCSI disk
>> [    4.589078] sd 3:0:0:0: Attached scsi generic sg3 type 0
>> [    4.589343] sd 3:0:0:0: [sdd] 781422768 512-byte logical blocks:
>> (400 GB/372 GiB)
>> [    4.589437] sd 3:0:0:0: [sdd] Write Protect is off
>> [    4.589442] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
>> [    4.589481] sd 3:0:0:0: [sdd] Write cache: enabled, read cache:
>> enabled, doesn't support DPO or FUA
>> [    4.601957]  sdd: sdd1
>> [    4.602404] sd 3:0:0:0: [sdd] Attached SCSI disk
>>
>>
>> I could recreate from scratch if I had to, but I'd rather not have to
>> copy all the data back over if I can help it.
>> That would take several hours of moving data over the network :-(
>>
>> Thanks,
>> Jeff Painter
>> --
>> This message was sent to: William <william at trilug.org>
>> To unsubscribe, send a blank message to trilug-leave at trilug.org from that
>> address.
>> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
>> Unsubscribe or edit options on the web  :
>> http://www.trilug.org/mailman/options/trilug/william%40trilug.org
>> TriLUG FAQ          :
>> http://www.trilug.org/wiki/Frequently_Asked_Questions
>>
> --
> This message was sent to: Jeffery Painter <jlpaint2 at ncsu.edu>
> To unsubscribe, send a blank message to trilug-leave at trilug.org from that
> address.
> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
> Unsubscribe or edit options on the web  :
> http://www.trilug.org/mailman/options/trilug/jlpaint2%40ncsu.edu
> TriLUG FAQ          : http://www.trilug.org/wiki/Frequently_Asked_Questions
>