Storage space partition
Nair, Murlidharan T
mnair at iusb.edu
Fri Apr 14 20:09:41 UTC 2006
-----Original Message-----
From: redhat-install-list-bounces at redhat.com
[mailto:redhat-install-list-bounces at redhat.com] On Behalf Of Bob McClure
Jr
Sent: Friday, April 14, 2006 4:03 PM
To: Getting started with Red Hat Linux
Subject: Re: Storage space partition
> > > > <much snippage>
> > > >
> >
> >
> Here is the output of fdisk -l
>
> Disk /dev/sda: 36.3 GB, 36364615680 bytes
> 64 heads, 32 sectors/track, 34680 cylinders
> Units = cylinders of 2048 * 512 = 1048576 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sda1 1 31 31728 de Dell Utility
> /dev/sda2 32 7748 7902208 83 Linux
> /dev/sda3 * 7749 7848 102400 83 Linux
> /dev/sda4 7849 34680 27475968 5 Extended
> /dev/sda5 7849 8872 1048560 83 Linux
> /dev/sda6 8873 10920 2097136 82 Linux swap
> /dev/sda7 10921 14925 4101104 83 Linux
> /dev/sda8 14926 19915 5109744 83 Linux
> /dev/sda9 19916 34630 15068144 83 Linux
>
> Disk /dev/sdb: 700.0 GB, 700079669248 bytes
> 255 heads, 63 sectors/track, 85113 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 1 85113 683670141 8e Linux LVM
>
> Disk /dev/sdc: 700.0 GB, 700079669248 bytes
> 255 heads, 63 sectors/track, 85113 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sdc1 1 85113 683670141 8e Linux LVM
>
> Disk /dev/emcpowera: 700.0 GB, 700079669248 bytes
> 255 heads, 63 sectors/track, 85113 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/emcpowera1 1 85113 683670141 8e Linux
LVM
>
>
> Cheers ../Murli
Okay, I somewhat expected that. Your SAN appears to be showing your
machine multiple variants of the same device. I don't know what your
SAN hardware is, but my sole experience is with HP's MSA-1500 with
MSA-20 and MSA-30 shelves. On it, we had to go into "Selective
Storage Presentation" to keep linux from seeing 16 or more devices,
most of which were bogus. Otherwise, every time you run "vgscan" or
anything related, it's going to see multiple instances of the real
virtual (?) disk.
Once you get that sorted out, I'd run pvcreate on the partition,
/dev/sdb1, rather than the whole drive /dev/sdb.
Cheers,
--
Bob McClure, Jr. Bobcat Open Systems, Inc.
bob at bobcatos.com http://www.bobcatos.com
The best things in life aren't things.
_______________________________________________
Redhat-install-list mailing list
Redhat-install-list at redhat.com
https://www.redhat.com/mailman/listinfo/redhat-install-list
To Unsubscribe Go To ABOVE URL or send a message to:
redhat-install-list-request at redhat.com
Subject: unsubscribe
If I run pvremove it should put it back to the original state correct?
Here is the output of the test run
[root at bioinformatics /]# pvremove -t -v /dev/emcpowera
Test mode: Metadata will NOT be updated.
/dev/cdrom: open failed: Read-only file system
Found duplicate PV XKollgX4GsBzbFyJsK13JS62S3P4b0Vr: using /dev/sdb
not /dev/emcpowera
Found duplicate PV XKollgX4GsBzbFyJsK13JS62S3P4b0Vr: using /dev/sdc
not /dev/emcpowera
Labels on physical volume "/dev/emcpowera" successfully wiped
Test mode: Wiping internal cache
More information about the Redhat-install-list
mailing list