Need help creating a LARGE mount point

[sbrews]

I have a request from our DBAs to set up a 500g mount point. While I have been able to create a vg with this command:

mkvg -G -s 1024 -y oradata1vg hdiskpower5 (EMC disk array)

I have run into problems with the LV and/or the file system. I dont recall the specific error message, but it was something along the lines of "not enough space to create requested LV/file system".

Has anyone created a mount point this large? If so, can you share with me how you did it - or - point me to some docs that will help me figure it out?

thanks
scott

 

[MoshiachNow]

HI,

It depends on which AIX version you are running.
Have a look at the following docs:

http://www.gruftie.net/ibm/tl/techlib/qna/faxes/html/krn/krn14.htm

Look at chapter 1.5 of:

http://www.redbooks.ibm.com/redbooks/SG245432.html

"Long live king Moshiach !"

http://www.7for70.com/

 

[abutifilmnd]

You can create a filesystem on LV or create it directly.

can you list output of "lsvg oradata1vg" ?

Do you really have 500 gram (lol!) of space avaialble in volume group?

Cut and paste exact error message on this post.

Gook luck to AIX learning.

Bandu
EMC Professional.
484-868-0599

 

[Yegolev]

there are a lot of things which might go wrong here, if you are using smit you can get the error from your smit.log file. could be something as simple as specifying too-big of a lv or fs. i do this sort of thing:

mklv -y ${LV} -tjfs -ae -ex -c1 -wn ${VGNAME} ${PP}
crfs -v jfs -a bf=true -d ${LV} -Ayes -m ${MNTPT}

this avoids me having to figure out how big to make the fs, i just calculate PP when creating the lv.

your mileage may vary.

we find it useful to ignore silly requests from the DBA staff. they are just being lazy so as to avoid making many datafiles. our data fs are mostly 7.5GB fs on same-size hypers, including our TB-sized DBs. trust me, it makes things easier to manage. if i had to deal with two 512GB datafiles i think i would lose my mind.

IBM Certified -- AIX 4.3 Obfuscation

 

[bi]

Yegolev, you are right about DBAs! But besides some laziness, they always seem to want twice the amount of space then they actually need. Then when they want more, you have to tear the big LVs apart to make room for the new one!

Anyway...

Could not specifying enough maximum logical partitions when creating the LV be causing this? The default is 512.