[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: LVM won't create PV on raid partition
On Wed, Nov 24, 2010 at 12:01 PM, Hugo Silva <hugo%barafranca.com@localhost>
> Just noticed this behaviour on a 5.99.40 system:
> # lvm pvcreate /dev/rvnd0d
> ÂPhysical volume "/dev/rvnd0d" successfully created
> # lvm pvcreate /dev/rraid0h
> ÂDevice /dev/rraid0h not found (or ignored by filtering).
> Âh: Â96468864 Â50331648 Â Â unused Â Â Â0 Â Â 0 Â Â Â Â# (Cyl. Â49152 -
> (Different "problem":)
> While trying to create a PV on vnd0a:
> Â/dev/rvnd0a: write failed after 0 of 2048 at 0: Read-only file system
> Â/dev/rvnd0a not wiped: aborting
> but.. (fstype=4.2BSD)
> # newfs -O2 /dev/rvnd0a
> /dev/rvnd0a: 16.0MB (32768 sectors) block size 4096, fragment size 512
> Â Â Â Âusing 4 cylinder groups of 4.00MB, 1024 blks, 1808 inodes.
> super-block backups (for fsck_ffs -b #) at:
> 144, 8336, 16528, 24720,
> or fstype=unused:
> Â/dev/rvnd0a: open failed: Device not configured
> ÂCan't open /dev/rvnd0a exclusively. ÂMounted filesystem?
> Now I understand why it says 'device not configured' but this seems picky,
> shouldn't it say the same for the 'd' partition too, then?
> Also, according to the manpage:
> Â Â Â pvcreate initializes PhysicalVolume for later use by the Logical
> Â Â Â Manager (LVM). ÂEach PhysicalVolume can Âbe Âa Âdisk Âpartition,
> Â Â Â disk, meta device, or loopback file.
> The question is: Shouldn't creating a PV on raid0h (fstype=unused) work?
Yes it should work I will test it later today.
Main Index |
Thread Index |