LVM on SAN

[Constantine_1]

Hi this my first post

Is there a different procedure
For creating file systems and LUNs on SAN
Than on regular diskarrays

Thanks

[Alzhy · Accepted solution]

If you mean -- getting luns (aka "disks") into LVM, carving it into lvols or stripes... The answer is no.. it is no different that dealing with JBODS or ordinary disk arrays..

On a SAN, you can raise your IO power some bit - if your paths are redundant, you can additionally "stripe" these already RAIDed LUNS accross controllers (or HBA's) or even RAID5 them... perforance and ultra-high reliability...

Or take a serious look at Veritas Volume Manager is you've ever used it on other patforms... skills sets are exactly the same...

[Jeff Schussele]

Hi,

Nope - no difference.
Whomever carves out the LUNs & zones them should present 1 or more (if you have alt links or paths) disk devices for every LUN made visible to the system.
LVM will treat them just as if they were regular disks. LVM knows not, nor cares, whether they're Raid 5/0/1/10.
Just treat them as standalone disks when you add them to VGs.

Rgds,
Jeff

[Mark Greene_1]

Who's your SAN Vendor? HP? EMC? IBM? some other?

Your vendor ought to have a documentation of a prefered method (mostly centered around a correct order of events to get all the pieces to play together) for creating LVM's and file systems. This may include loading software agents for the SAN management software, loadbalancing software, using the PVLinks feature of LVM to establish alternate hardware paths to the SAN, and may or may not include naming convention recommendations.

mark

[Constantine_1]

StorageTek
D280

Thank you
Everyone