[linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Adam Olsen]

This pretty much sums it up:

imgserv:/storage/# lvscan
  ACTIVE            '/dev/storage/storage' [3.62 TB] inherit
imgserv:/storage/# fdisk /dev/storage/storage

Unable to read /dev/storage/storage

I can't mount it, access it with fdisk.  Here's the lvdisplay output:

imgserv:/storage/# lvdisplay
  --- Logical volume ---
  LV Name                /dev/storage/storage
  VG Name                storage
  LV UUID                Cw8aAr-YHsR-oVfH-7AAx-2ppa-Zm3M-U9z1eA
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                3.62 TB
  Current LE             948962
  Segments               3
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0

This is on debian etch.   This is what I see at the end of dmesg:

cdrom: open failed.
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54

Which I don't think has anything to do with this problem, as hdc is
NOT one of the physical volumes... it's a cdrom drive.

Is there anything I can do to debug this?

-- 
Adam Olsen
SendOutCards.com
http://www.vimtips.org
http://last.fm/user/synic

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Ray Van Dolson]

On Tue, Jul 21, 2009 at 12:55:50PM -0700, Adam Olsen wrote:
> This pretty much sums it up:
> 
> imgserv:/storage/# lvscan
>   ACTIVE            '/dev/storage/storage' [3.62 TB] inherit
> imgserv:/storage/# fdisk /dev/storage/storage
> 
> Unable to read /dev/storage/storage
> 
> I can't mount it, access it with fdisk.  Here's the lvdisplay output:
> 
> imgserv:/storage/# lvdisplay
>   --- Logical volume ---
>   LV Name                /dev/storage/storage
>   VG Name                storage
>   LV UUID                Cw8aAr-YHsR-oVfH-7AAx-2ppa-Zm3M-U9z1eA
>   LV Write Access        read/write
>   LV Status              available
>   # open                 0
>   LV Size                3.62 TB
>   Current LE             948962
>   Segments               3
>   Allocation             inherit
>   Read ahead sectors     auto
>   - currently set to     256
>   Block device           254:0
> 
> This is on debian etch.   This is what I see at the end of dmesg:
> 
> cdrom: open failed.
> hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
> hdc: packet command error: error=0x54
> 
> Which I don't think has anything to do with this problem, as hdc is
> NOT one of the physical volumes... it's a cdrom drive.
> 
> Is there anything I can do to debug this?
> 

You've already done a vgchange -ay on the volgroup?  What's the output
of pvs/pvdisplay?

Ray

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Adam Olsen]

imgserv:/storage/# vgchange -ay
  device-mapper: resume ioctl failed: Invalid argument
  Unable to resume storage-storage (254:0)
  1 logical volume(s) in volume group "storage" now active
imgserv:/storage/# pvs
  PV         VG      Fmt  Attr PSize PFree
  /dev/sda3  storage lvm2 a-   1.44T    0
  /dev/sdb1  storage lvm2 a-   1.09T    0
  /dev/sdc1  storage lvm2 a-   1.09T 4.98G

imgserv:/storage/# pvdisplay
  --- Physical volume ---
  PV Name               /dev/sda3
  VG Name               storage
  PV Size               1.44 TB / not usable 1.51 MB
  Allocatable           yes (but full)
  PE Size (KByte)       4096
  Total PE              378339
  Free PE               0
  Allocated PE          378339
  PV UUID               ddnHh1-BvAl-5zpd-8KFT-YnZ8-MWHp-pQAWs1

  --- Physical volume ---
  PV Name               /dev/sdb1
  VG Name               storage
  PV Size               1.09 TB / not usable 3.73 MB
  Allocatable           yes (but full)
  PE Size (KByte)       4096
  Total PE              285949
  Free PE               0
  Allocated PE          285949
  PV UUID               Qhl3tF-JWTY-ORbb-liI9-XteR-vlY9-wtInW5

  --- Physical volume ---
  PV Name               /dev/sdc1
  VG Name               storage
  PV Size               1.09 TB / not usable 3.73 MB
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              285949
  Free PE               1275
  Allocated PE          284674
  PV UUID               Z6h80h-oZfP-QMPW-iZdt-dGL0-haBJ-r93Ooi

On Tue, Jul 21, 2009 at 1:58 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> On Tue, Jul 21, 2009 at 12:55:50PM -0700, Adam Olsen wrote:
>> This pretty much sums it up:
>>
>> imgserv:/storage/# lvscan
>> � ACTIVE � � � � � �'/dev/storage/storage' [3.62 TB] inherit
>> imgserv:/storage/# fdisk /dev/storage/storage
>>
>> Unable to read /dev/storage/storage
>>
>> I can't mount it, access it with fdisk. �Here's the lvdisplay output:
>>
>> imgserv:/storage/# lvdisplay
>> � --- Logical volume ---
>> � LV Name � � � � � � � �/dev/storage/storage
>> � VG Name � � � � � � � �storage
>> � LV UUID � � � � � � � �Cw8aAr-YHsR-oVfH-7AAx-2ppa-Zm3M-U9z1eA
>> � LV Write Access � � � �read/write
>> � LV Status � � � � � � �available
>> � # open � � � � � � � � 0
>> � LV Size � � � � � � � �3.62 TB
>> � Current LE � � � � � � 948962
>> � Segments � � � � � � � 3
>> � Allocation � � � � � � inherit
>> � Read ahead sectors � � auto
>> � - currently set to � � 256
>> � Block device � � � � � 254:0
>>
>> This is on debian etch. � This is what I see at the end of dmesg:
>>
>> cdrom: open failed.
>> hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
>> hdc: packet command error: error=0x54
>>
>> Which I don't think has anything to do with this problem, as hdc is
>> NOT one of the physical volumes... it's a cdrom drive.
>>
>> Is there anything I can do to debug this?
>>
>
> You've already done a vgchange -ay on the volgroup? �What's the output
> of pvs/pvdisplay?
>
> Ray
>
> _______________________________________________
> 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/
>



-- 
Adam Olsen
SendOutCards.com
http://www.vimtips.org
http://last.fm/user/synic

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Ray Van Dolson]

On Tue, Jul 21, 2009 at 01:01:39PM -0700, Adam Olsen wrote:
> imgserv:/storage/# vgchange -ay
>   device-mapper: resume ioctl failed: Invalid argument
>   Unable to resume storage-storage (254:0)
>   1 logical volume(s) in volume group "storage" now active

Hmm... can you do an fdisk on your LV now?  That error doesn't look
good though.

Are you able to run fdisk on each of the member physical volumes
successfully?

> imgserv:/storage/# pvs
>   PV         VG      Fmt  Attr PSize PFree
>   /dev/sda3  storage lvm2 a-   1.44T    0
>   /dev/sdb1  storage lvm2 a-   1.09T    0
>   /dev/sdc1  storage lvm2 a-   1.09T 4.98G
> 
> imgserv:/storage/# pvdisplay
>   --- Physical volume ---
>   PV Name               /dev/sda3
>   VG Name               storage
>   PV Size               1.44 TB / not usable 1.51 MB
>   Allocatable           yes (but full)
>   PE Size (KByte)       4096
>   Total PE              378339
>   Free PE               0
>   Allocated PE          378339
>   PV UUID               ddnHh1-BvAl-5zpd-8KFT-YnZ8-MWHp-pQAWs1
> 
>   --- Physical volume ---
>   PV Name               /dev/sdb1
>   VG Name               storage
>   PV Size               1.09 TB / not usable 3.73 MB
>   Allocatable           yes (but full)
>   PE Size (KByte)       4096
>   Total PE              285949
>   Free PE               0
>   Allocated PE          285949
>   PV UUID               Qhl3tF-JWTY-ORbb-liI9-XteR-vlY9-wtInW5
> 
>   --- Physical volume ---
>   PV Name               /dev/sdc1
>   VG Name               storage
>   PV Size               1.09 TB / not usable 3.73 MB
>   Allocatable           yes
>   PE Size (KByte)       4096
>   Total PE              285949
>   Free PE               1275
>   Allocated PE          284674
>   PV UUID               Z6h80h-oZfP-QMPW-iZdt-dGL0-haBJ-r93Ooi

Ray

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Adam Olsen]

On Tue, Jul 21, 2009 at 2:07 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> Hmm... can you do an fdisk on your LV now? �That error doesn't look
> good though.

Nope, still says "unable to read"

> Are you able to run fdisk on each of the member physical volumes
> successfully?

I'm not sure how to do that.  For example:

imgserv:/storage/# fsck /dev/sda3
fsck 1.41.3 (12-Oct-2008)
fsck: fsck.lvm2pv: not found
fsck: Error 2 while executing fsck.lvm2pv for /dev/sda3

Though, it looks like fsck.lvm2pv is not something that has actually
been created yet.

-- 
Adam Olsen
SendOutCards.com
http://www.vimtips.org
http://last.fm/user/synic

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Ray Van Dolson]

On Tue, Jul 21, 2009 at 01:29:23PM -0700, Adam Olsen wrote:
> On Tue, Jul 21, 2009 at 2:07 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> > Hmm... can you do an fdisk on your LV now? �That error doesn't look
> > good though.
> 
> Nope, still says "unable to read"
> 
> > Are you able to run fdisk on each of the member physical volumes
> > successfully?
> 
> I'm not sure how to do that.  For example:
> 
> imgserv:/storage/# fsck /dev/sda3
> fsck 1.41.3 (12-Oct-2008)
> fsck: fsck.lvm2pv: not found
> fsck: Error 2 while executing fsck.lvm2pv for /dev/sda3
> 
> Though, it looks like fsck.lvm2pv is not something that has actually
> been created yet.

Nono, don't do that... fsck is for filesystems :)  Just run fdisk
/dev/sda, run 'p' (for print) and see if you can see your LVM
partition.

Just a poor man's way to check that /dev/sda is OK.  Do this for the
other PV members.

Do not run fsck on it, that'll hose the data (if it even runs at all).

Ray

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Sven Eschenberg]

Ray Van Dolson schrieb:
> On Tue, Jul 21, 2009 at 01:29:23PM -0700, Adam Olsen wrote:
>> On Tue, Jul 21, 2009 at 2:07 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
>>> Hmm... can you do an fdisk on your LV now?  That error doesn't look
>>> good though.
>> Nope, still says "unable to read"
>>
>>> Are you able to run fdisk on each of the member physical volumes
>>> successfully?
>> I'm not sure how to do that.  For example:
>>
>> imgserv:/storage/# fsck /dev/sda3
>> fsck 1.41.3 (12-Oct-2008)
>> fsck: fsck.lvm2pv: not found
>> fsck: Error 2 while executing fsck.lvm2pv for /dev/sda3
>>
>> Though, it looks like fsck.lvm2pv is not something that has actually
>> been created yet.
> 
> Nono, don't do that... fsck is for filesystems :)  Just run fdisk
> /dev/sda, run 'p' (for print) and see if you can see your LVM
> partition.
> 
> Just a poor man's way to check that /dev/sda is OK.  Do this for the
> other PV members.
> 
> Do not run fsck on it, that'll hose the data (if it even runs at all).
> 
> Ray
> 

fdisk -l /dev/...

Should do the job aswell, if it's only about printing the partition table

-Sven

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Adam Olsen]

On Tue, Jul 21, 2009 at 2:35 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> Just a poor man's way to check that /dev/sda is OK. �Do this for the
> other PV members.

Oh, yes.  I can run fdisk and see that all the partitions are there.
Each physical volume *looks* ok.

-- 
Adam Olsen
SendOutCards.com
http://www.vimtips.org
http://last.fm/user/synic

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Ray Van Dolson]

On Tue, Jul 21, 2009 at 01:47:01PM -0700, Adam Olsen wrote:
> On Tue, Jul 21, 2009 at 2:35 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> > Just a poor man's way to check that /dev/sda is OK. �Do this for the
> > other PV members.
> 
> Oh, yes.  I can run fdisk and see that all the partitions are there.
> Each physical volume *looks* ok.

Very strange... a few more commands:

vgs -P -o +devices
lvs -P -a -o +devices

You also might want to take a look at the files under /etc/lvm to make
sure everything looks intact.

If you want, post the lvmdump tarball somewhere...

When did this start happening?

Ray

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Adam Olsen]

On Tue, Jul 21, 2009 at 3:07 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> Very strange... a few more commands:
>
> vgs -P -o +devices
> lvs -P -a -o +devices

imgserv:/storage/# vgs -P -o +devices
  Partial mode. Incomplete volume groups will be activated read-only.
  VG      #PV #LV #SN Attr   VSize VFree Devices
  storage   3   1   0 wz--n- 3.62T 4.98G /dev/sda3(0)
  storage   3   1   0 wz--n- 3.62T 4.98G /dev/sdb1(0)
  storage   3   1   0 wz--n- 3.62T 4.98G /dev/sdc1(0)
imgserv:/storage/# lvs -P -a -o +devices
  Partial mode. Incomplete volume groups will be activated read-only.
  LV      VG      Attr   LSize Origin Snap%  Move Log Copy%  Convert
Devices
  storage storage -wi-i- 3.62T
/dev/sda3(0)
  storage storage -wi-i- 3.62T
/dev/sdb1(0)
  storage storage -wi-i- 3.62T
/dev/sdc1(0)

> If you want, post the lvmdump tarball somewhere...

http://www.exaile.org/lvmdump.tar.gz

> When did this start happening?

This morning.  5am MST.

-- 
Adam Olsen
SendOutCards.com
http://www.vimtips.org
http://last.fm/user/synic

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Ray Van Dolson]

On Tue, Jul 21, 2009 at 02:24:26PM -0700, Adam Olsen wrote:
> On Tue, Jul 21, 2009 at 3:07 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> > Very strange... a few more commands:
> >
> > vgs -P -o +devices
> > lvs -P -a -o +devices
> 
> imgserv:/storage/# vgs -P -o +devices
>   Partial mode. Incomplete volume groups will be activated read-only.
>   VG      #PV #LV #SN Attr   VSize VFree Devices
>   storage   3   1   0 wz--n- 3.62T 4.98G /dev/sda3(0)
>   storage   3   1   0 wz--n- 3.62T 4.98G /dev/sdb1(0)
>   storage   3   1   0 wz--n- 3.62T 4.98G /dev/sdc1(0)
> imgserv:/storage/# lvs -P -a -o +devices
>   Partial mode. Incomplete volume groups will be activated read-only.
>   LV      VG      Attr   LSize Origin Snap%  Move Log Copy%  Convert
> Devices
>   storage storage -wi-i- 3.62T
> /dev/sda3(0)
>   storage storage -wi-i- 3.62T
> /dev/sdb1(0)
>   storage storage -wi-i- 3.62T
> /dev/sdc1(0)
> 
> > If you want, post the lvmdump tarball somewhere...
> 
> http://www.exaile.org/lvmdump.tar.gz

Maybe someone else could take a look as well.  Some of the LVM metadata
files in the archive directory appear to be missing logical_volumes {}
sections.

I wonder if this could be fixed with a simple 

  vgcfgrestore -f /etc/lvm/backup/storage storage
  vgscan
  vgchange -ay storage

Also it looks like some of the older archived versions would be valid
as well.

  vgcfgrestore -l storage

Should give a list...

> 
> > When did this start happening?
> 
> This morning.  5am MST.

Ray

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Adam Olsen]

On Tue, Jul 21, 2009 at 3:59 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> �vgcfgrestore -l storage

Hrmm, getting a lot of this:

  File:		/etc/lvm/archive/storage_00033.vg
  Couldn't find device with uuid 'MSeHHn-Tcol-GROd-541H-8wcS-3cqv-QBqL4m'.
  Couldn't find device with uuid 'WtsE6d-UpqB-l3vo-um3o-0qO9-k4xl-HcJ0eM'.
  Couldn't find device with uuid 'zVilO7-5ioi-6c9W-ZEnp-uXpP-p1rR-WiwE3M'.
  VG name:    	storage
  Description:	Created *before* executing 'vgscan'
  Backup Time:	Tue Jul 21 13:19:21 2009

What is this stuff about can't find device with uuid?


-- 
Adam Olsen
SendOutCards.com
http://www.vimtips.org
http://last.fm/user/synic

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Ray Van Dolson]

On Tue, Jul 21, 2009 at 03:09:27PM -0700, Adam Olsen wrote:
> On Tue, Jul 21, 2009 at 3:59 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> > �vgcfgrestore -l storage
> 
> Hrmm, getting a lot of this:
> 
>   File:		/etc/lvm/archive/storage_00033.vg
>   Couldn't find device with uuid 'MSeHHn-Tcol-GROd-541H-8wcS-3cqv-QBqL4m'.
>   Couldn't find device with uuid 'WtsE6d-UpqB-l3vo-um3o-0qO9-k4xl-HcJ0eM'.
>   Couldn't find device with uuid 'zVilO7-5ioi-6c9W-ZEnp-uXpP-p1rR-WiwE3M'.
>   VG name:    	storage
>   Description:	Created *before* executing 'vgscan'
>   Backup Time:	Tue Jul 21 13:19:21 2009
> 
> What is this stuff about can't find device with uuid?
> 

It appears that sometime during the 33 and 34 files in archive/ the
UUID's on your PV's changed.

Do you see the above errors for storage_00034.vg?

What about for vgcfgrestore -l -f /etc/lvm/backup/storage storage ?

I'm not sure which one of these backup files I'd use to restore to.
You can also re-run pvcreate with the --uuid and --restorefile argument
if you want to recreate a "lost" uuid...

Still wondering how in the world this happened :)

Ray

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Adam Olsen]

On Tue, Jul 21, 2009 at 4:21 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> I'm not sure which one of these backup files I'd use to restore to.
> You can also re-run pvcreate with the --uuid and --restorefile argument
> if you want to recreate a "lost" uuid...

How can I see the difference between what uuid's it's looking for and
what is currently set on the devices?

(neither of the vgcfgrestore commands helped, either for
storage_00034.vg or /etc/lvm/backup/storage)

-- 
Adam Olsen
SendOutCards.com
http://www.vimtips.org
http://last.fm/user/synic

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Ray Van Dolson]

On Tue, Jul 21, 2009 at 03:43:58PM -0700, Adam Olsen wrote:
> On Tue, Jul 21, 2009 at 4:21 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> > I'm not sure which one of these backup files I'd use to restore to.
> > You can also re-run pvcreate with the --uuid and --restorefile argument
> > if you want to recreate a "lost" uuid...
> 
> How can I see the difference between what uuid's it's looking for and
> what is currently set on the devices?

pvdisplay should show the UUID's currently on your physical devices.
You can look at the contents of the file to compare.

> (neither of the vgcfgrestore commands helped, either for
> storage_00034.vg or /etc/lvm/backup/storage)

I am kinda stumped at this point.

Ray

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Bryn M. Reeves]

On Tue, 2009-07-21 at 16:09 -0600, Adam Olsen wrote:
> On Tue, Jul 21, 2009 at 3:59 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> >  vgcfgrestore -l storage
> 
> Hrmm, getting a lot of this:
> 
>   File:		/etc/lvm/archive/storage_00033.vg
>   Couldn't find device with uuid 'MSeHHn-Tcol-GROd-541H-8wcS-3cqv-QBqL4m'.
>   Couldn't find device with uuid 'WtsE6d-UpqB-l3vo-um3o-0qO9-k4xl-HcJ0eM'.
>   Couldn't find device with uuid 'zVilO7-5ioi-6c9W-ZEnp-uXpP-p1rR-WiwE3M'.
>   VG name:    	storage
>   Description:	Created *before* executing 'vgscan'
>   Backup Time:	Tue Jul 21 13:19:21 2009
> 
> What is this stuff about can't find device with uuid?

Do you get those messages when running other commands or just when
looking at archived metadata?

The message in this case is telling you that the named metadata archive
includes references to PV UUIDs that could not be found on the system at
this time.

You can view all PVs and their UUIDs by running:

pvs -o+uuid

Regards,
Bryn.

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Ron Johnson]

On 2009-07-21 17:09, Adam Olsen wrote:
> On Tue, Jul 21, 2009 at 3:59 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
>>  vgcfgrestore -l storage
> 
> Hrmm, getting a lot of this:
> 
>   File:		/etc/lvm/archive/storage_00033.vg
>   Couldn't find device with uuid 'MSeHHn-Tcol-GROd-541H-8wcS-3cqv-QBqL4m'.
>   Couldn't find device with uuid 'WtsE6d-UpqB-l3vo-um3o-0qO9-k4xl-HcJ0eM'.
>   Couldn't find device with uuid 'zVilO7-5ioi-6c9W-ZEnp-uXpP-p1rR-WiwE3M'.
>   VG name:    	storage
>   Description:	Created *before* executing 'vgscan'
>   Backup Time:	Tue Jul 21 13:19:21 2009
> 
> What is this stuff about can't find device with uuid?

I got that today with a new mobo that didn't originally see all my 
hard drives.  A little BIOS fiddling, a reboot and all back to normal.

That's probably not your problem, though...

-- 
Scooty Puff, Sr
The Doom-Bringer

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Bryn M. Reeves]

On Tue, 2009-07-21 at 14:01 -0600, Adam Olsen wrote:
> imgserv:/storage/# vgchange -ay
>   device-mapper: resume ioctl failed: Invalid argument
>   Unable to resume storage-storage (254:0)
>   1 logical volume(s) in volume group "storage" now active

Did something appear in dmesg right after the tools printed this
message? The failed ioctl should have left some more information about
the problem in the logs.

Before you ran this command did you notice any other error messages or
warning from the lvm2 tools about suspended devices?

Regards,
Bryn.

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Ron Johnson]

On 2009-07-21 14:58, Ray Van Dolson wrote:
> On Tue, Jul 21, 2009 at 12:55:50PM -0700, Adam Olsen wrote:
>> This pretty much sums it up:
>>
>> imgserv:/storage/# lvscan
>>   ACTIVE            '/dev/storage/storage' [3.62 TB] inherit
>> imgserv:/storage/# fdisk /dev/storage/storage
>>

But doesn't fdisk only work on *physical* block devices?

IOW, why fdisk an lv ?

-- 
Scooty Puff, Sr
The Doom-Bringer

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Adam Olsen]

On Tue, Jul 21, 2009 at 11:26 PM, Ron Johnson<ron.l.johnson@cox.net> wrote:
> But doesn't fdisk only work on *physical* block devices?
>
> IOW, why fdisk an lv ?

No, it works on logical volumes too.  You still need to create
partitions even on the logical ones.

-- 
Adam Olsen
SendOutCards.com
http://www.vimtips.org
http://last.fm/user/synic

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Ron Johnson]

On 2009-07-22 00:41, Adam Olsen wrote:
> On Tue, Jul 21, 2009 at 11:26 PM, Ron Johnson<ron.l.johnson@cox.net> wrote:
>> But doesn't fdisk only work on *physical* block devices?
>>
>> IOW, why fdisk an lv ?
> 
> No, it works on logical volumes too.  You still need to create
> partitions even on the logical ones.
> 

Why didn't I have to?  This has always worked for me:

# mkfs.${TYPE} /dev/some_vg/some_lv

-- 
Scooty Puff, Sr
The Doom-Bringer

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Adam Olsen]

On Tue, Jul 21, 2009 at 11:49 PM, Ron Johnson<ron.l.johnson@cox.net> wrote:
> Why didn't I have to? �This has always worked for me:
>
> # mkfs.${TYPE} /dev/some_vg/some_lv

Perhaps you're not required to.  I just always assumed you did, so I
always have.  It does work, and works how you'd expect it to.

-- 
Adam Olsen
SendOutCards.com
http://www.vimtips.org
http://last.fm/user/synic

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Sven Eschenberg]

All 'logical' block devices behave pretty much like physical ones.

So you are free to put partition tables on top of lvs or dmcrypt block 
devices, you can aswell put each other on top of each other. It just 
adds possible layers of failure and or overhead.

Since LVs give you the opportunity to be created in whatever size you 
wish, in many usage cases it is perfectly normal and straight forward to 
put a filesystem ontop of an LV instead of a partition table.

To the other guy: Whenever you export some LV as LUN or Blockdevice via 
network as example, you will end up with a partition table on top of the 
logical blockdevice, which is prefectly normal and okay. i.e. if you'd 
want to export some LV via iSCSI to a windows box, you are pretty much 
required to have either a partition table ontop of the lv, or some other 
disk slicing scheme (EFI Partitions, dynamic volume signatures, whatsoever).

Just for your Information.

Adam, there is a blkid command coming with the e2fsprogs, it will print 
all UUIDs+type of all your physical and logical volumes.

I.E.: /dev/mdXXX: UUID="<yourUUID" TYPE="LVM2_member"

Just another option to get an overview of the current situation maybe, 
if you cannot find the UUIDs otherwise.

Regards

-Sven


Adam Olsen schrieb:
> On Tue, Jul 21, 2009 at 11:49 PM, Ron Johnson<ron.l.johnson@cox.net> wrote:
>> Why didn't I have to?  This has always worked for me:
>>
>> # mkfs.${TYPE} /dev/some_vg/some_lv
> 
> Perhaps you're not required to.  I just always assumed you did, so I
> always have.  It does work, and works how you'd expect it to.
> 

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Bryn M. Reeves]

On Wed, 2009-07-22 at 17:42 +0200, Sven Eschenberg wrote:
> All 'logical' block devices behave pretty much like physical ones.
> 
> So you are free to put partition tables on top of lvs or dmcrypt block 
> devices, you can aswell put each other on top of each other. It just 
> adds possible layers of failure and or overhead.

Not really; Linux block devices don't have to support partitioning in
the kernel and this is the case for device-mapper devices.

In practice it doesn't make much difference since device-mapper also
allows arbitrary regions of existing devices to be mapped into a new
device. With a tool that can read and interpret partition table metadata
this allows partitioning to be added in user space for those devices
that don't support it natively.

> Since LVs give you the opportunity to be created in whatever size you 
> wish, in many usage cases it is perfectly normal and straight forward to 
> put a filesystem ontop of an LV instead of a partition table.

Yes, this is the typical usage. Partitioning LVs is mostly of use when
you for some reason want to treat the LV as a whole-disk image for a
device that would normally be partitioned, e.g. an image for a
virtualised system.

Regards,
Bryn.

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Adam Olsen]

Thanks for the help guys.  We just ended up pulling from our backup,
so, even though we didn't end up getting this resolved, we're in good
shape.

Anyway, thanks again!

On Wed, Jul 22, 2009 at 10:49 AM, Bryn M. Reeves<bmr@redhat.com> wrote:
> On Wed, 2009-07-22 at 17:42 +0200, Sven Eschenberg wrote:
>> All 'logical' block devices behave pretty much like physical ones.
>>
>> So you are free to put partition tables on top of lvs or dmcrypt block
>> devices, you can aswell put each other on top of each other. It just
>> adds possible layers of failure and or overhead.
>
> Not really; Linux block devices don't have to support partitioning in
> the kernel and this is the case for device-mapper devices.
>
> In practice it doesn't make much difference since device-mapper also
> allows arbitrary regions of existing devices to be mapped into a new
> device. With a tool that can read and interpret partition table metadata
> this allows partitioning to be added in user space for those devices
> that don't support it natively.
>
>> Since LVs give you the opportunity to be created in whatever size you
>> wish, in many usage cases it is perfectly normal and straight forward to
>> put a filesystem ontop of an LV instead of a partition table.
>
> Yes, this is the typical usage. Partitioning LVs is mostly of use when
> you for some reason want to treat the LV as a whole-disk image for a
> device that would normally be partitioned, e.g. an image for a
> virtualised system.
>
> Regards,
> Bryn.
>
>
> _______________________________________________
> 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/
>



-- 
Adam Olsen
SendOutCards.com
http://www.vimtips.org
http://last.fm/user/synic

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Bryn M. Reeves]

On Tue, 2009-07-21 at 23:41 -0600, Adam Olsen wrote:
> On Tue, Jul 21, 2009 at 11:26 PM, Ron Johnson<ron.l.johnson@cox.net> wrote:
> > But doesn't fdisk only work on *physical* block devices?
> >
> > IOW, why fdisk an lv ?
> 
> No, it works on logical volumes too.  You still need to create
> partitions even on the logical ones.
> 

You don't "need" to, but you can if you want (although if you wish to
access the partitions on the host that has the volume group and logical
volumes visible you'll need to use kpartx since device-mapper devices
are not themselves partitionable in the kernel).

Regards,
Bryn.

Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!

[Bryn M. Reeves]

On Wed, 2009-07-22 at 00:26 -0500, Ron Johnson wrote:
> On 2009-07-21 14:58, Ray Van Dolson wrote:
> > On Tue, Jul 21, 2009 at 12:55:50PM -0700, Adam Olsen wrote:
> >> This pretty much sums it up:
> >>
> >> imgserv:/storage/# lvscan
> >>   ACTIVE            '/dev/storage/storage' [3.62 TB] inherit
> >> imgserv:/storage/# fdisk /dev/storage/storage
> >>
> 
> But doesn't fdisk only work on *physical* block devices?
> 
> IOW, why fdisk an lv ?
> 

You're using it as the backing store for a whole-disk image, e.g. for a
virtualised OS instance?

Bryn.