Once a LUN is presented to the host it really does not matter if it is formated ext2,ext3,xfs,etc...  or if it is an LVM. They should all work.

What does your /etc/fstab look like ?

After the reboot does the LUN show up when you run the command SMdevices ?

-cjtompsett

Yeah, I didn't think it mattered, here is the output of SMdevices:

PowerVault Modular Disk Storage Manager Devices, Version 09.17.A6.01

Built Tue Mar 20 15:31:11 CST 2007

Copyright 2005-2006 Dell Inc. All rights reserved.  Use is subject to license terms

  /dev/sdb (/dev/sg2) [Storage Array SA001, Virtual Disk VD01, LUN 0, Virtual Disk ID <6001ec9000d99785000002ff48871be0>, Preferred Path (Controller-0): In Use]

  /dev/sdc (/dev/sg3) [Storage Array SA001, Virtual Disk Access, LUN 31, Virtual Disk ID <6001ec9000d997850000000000000000>]

I reformatted the drive just XFS this time instead of LVM with XFS on top and it remounts after a reboot.  Is there something about LVM that the MD3000i is not supporting?

The command mount -t xfs /dev/sdb1 /var/lib/mysql/ won't work as the filesystem has been created on the lvol mysql01. Make sure the fstab is correct in that you are mounting /dev/PowerVault3000i/mysql01 and not /dev/sdb1.

Well the strange thing is, when I create the physical volume, /dev/sdb1:

 --- Physical volume ---

  PV Name               /dev/sdb1

  VG Name               PV3000i

  PV Size               930.52 GB / not usable 3.28 MB

  Allocatable           yes 

  PE Size (KByte)       4096

  Total PE              238213

  Free PE               5

  Allocated PE          238208

  PV UUID               x2AEGK-x1vb-9vYN-oYj9-rJTv-I9WJ-A2jp1l

and the volume group:

[root@dev3 ~]# vgdisplay

  --- Volume group ---

  VG Name               PV3000i

  System ID             

  Format                lvm2

  Metadata Areas        1

  Metadata Sequence No  2

  VG Access             read/write

  VG Status             resizable

  MAX LV                0

  Cur LV                1

  Open LV               1

  Max PV                0

  Cur PV                1

  Act PV                1

  VG Size               930.52 GB

  PE Size               4.00 MB

  Total PE              238213

  Alloc PE / Size       238208 / 930.50 GB

  Free  PE / Size       5 / 20.00 MB

  VG UUID               R1M9K1-zHEv-kmjQ-Bt9e-4Fp2-8Kr1-jxuZA7

and the logical volume:

[root@dev3 ~]# lvdisplay

  --- Logical volume ---

  LV Name                /dev/PV3000i/mysql01

  VG Name                PV3000i

  LV UUID                VaozUW-kdTJ-gv1b-hsSx-LFkD-DiMk-eRGln0

  LV Write Access        read/write

  LV Status              available

  # open                 1

  LV Size                930.50 GB

  Current LE             238208

  Segments               1

  Allocation             inherit

  Read ahead sectors     0

  Block device           253:1

It appears in /dev/ as PV3000i, or the path would be /dev/PV3000i/mysql01, and I put that in fstab:

/dev/PV3000i/mysql01    /var/lib/mysql          xfs     noatime         0 0    

everything is fine.  I can format, mount, unmount etc.

But when I reboot, the PV3000i in /dev does not reappear. and if I try to remount after the reboot I get bad superblock so I am probably doing something wrong but it appears that the LVM portion is not sticking after a reboot.  Should I use a different naming scheme for the PV or VG?   Its like the iSCSI portion is not retaining the new mount point in dev with LVM, but retains it with ext3 or XFS.