AIX - How to add LUN to a server

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

I believe its a directly attached server...correct?

root@server[/]# prtconf -L
LPAR Info: 1 00-7777H
root@server[/]#

No, it's an LPAR, otherwise prtconf would have returned "-1" or NULL or both.

But this has nothing to do with directly attached LUNs or LUNs over VIOS,
since you can well have FC adapters attached to an LPAR.

So please run

lsdev -Cc adapter |grep fcs

Do you see fcs0 (fcs1, fcs2,...) ?

ASKER

Yes, I do see fsc0,1, and 2.

root@server[/]# lsdev -Cc adapter |grep fcs
fcs0 Available 01-08 FC Adapter
fcs1 Available 05-08 FC Adapter
fcs2 Available 09-08 FC Adapter
root@server[/]#

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

The SAN admin is doing his part either tonight or early tomrrow morning, and it should be ready for me in the late AM. I will update my post once the SAN admin has completed his part.

ASKER

Yes, there are new ones.

hdiskpower66 none None
hdiskpower67 none None
hdiskpower68 none None

The SAN admin gave me 3 x 200G of SAN.

I need to create a new vg called dbvg03 and a new fs called dbdata03 and allocate all 600G (3x200G of SAN) to the new fs dbdata03. Please assist

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

There were a couple of vgnames with 128 and some with 1024. I went ahead and used the scalable option you provided above and created dbvg03 successfully.

hdiskpower66 0006924d40de9e17 dbvg03 active
hdiskpower67 0006924d40da5fad dbvg03 active
hdiskpower68 0006924d40e55c65 dbvg03 active

We use either option, but I would like to leave the LV naming to LVM.

I'm not sure about the Inline Logging or the standard external logging. How do I check that?

I don't believe we have a naming convention for log volumes.

I dont know if we use one logvolume for all FS in a VG, or one logvolume per FS. How do I check that?

I already have a FS named dbdata01 that I could use to model off of...if that helps...

Yes, issue

mount | grep dbdata01

(if it's mounted).

Look for the LV name (/dev/xxxxxxx), the mountpoint and the logvolume (log=/dev/xxxxxx)

and post the result.

ASKER

root@server[/]# mount | grep dbdata01
/dev/vg19lv01 /dbdata01 jfs2 Nov 18 21:29 rw,cio,log=/dev/vg19loglv00
root@server[/]#

ASKER CERTIFIED SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

I need to get the FS to 600G, but it fails..please see below.

root@server[/]# df -g /dbdata03
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/vg03lv01 512.00 511.92 1% 4 1% /dbdata03

root@server[/]# chfs -a size=600G /dbdata03
0516-404 allocp: This system cannot fulfill the allocation request.
There are not enough free partitions or not enough physical volumes
to keep strictness and satisfy allocation requests. The command
should be retried with different allocation characteristics.

Which value (in Megabytes) do you see beneath " FREE PPs: " in the output of "lsvg dbvg03"?

That's the maximum you can add, let's call it "mmmm"

chfs -a size=+mmmmM

3 * 200 GB disk size do not result in 600 GB usable LV size under LVM - there's some overhead!