Hi folks I am having probs tryin 1

[KOG]

Hi folks

I am having probs trying to create file system /backup on already created logical volume lv01 (pp size = 64 mg and it has 135 PPs).

COMMAND STATUS

Command: failed stdout: yes stderr: no

Before command completion, additional instructions may appear below.

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.
0516-822 mklv: Unable to create logical volume.
crfs: 0506-902 Cannot create logical volume.

Any idea why?

Thanking you all in advance.

Regards

Katherine

 

[DSMARWAY]

You normally get this error , if the MAX number of physical Volumes in the LV is not set
e.g. you created a LV called sid which is 10 GIG
in the LV section youi only specify one disk which is 8 GIG
( the parmater max number of physixal volumes )

its worth checking this parameter , even though you said this has already been created ?

When creating filesystem , are you using large filesystems?

post your lvol settings

 

[Guest_imported]

KOG,

most likely, you're running out of disk space for a specific PV or within a VG. you can try checking the following:

1. physical volume

lspv - displays info about Physical Volume w/in Volume Group

lspv <hdisk#> - check for free Physical partitions (PPs); where # = disk number

2. logical volume

lsvg - list info about volume group/s

*** you can select VG's that can still accommodate additional filesystem after creating a logical volume (LV).

 

[KOG]

Hi,

Here's the outputs of vg and lv.

$ lsvg backup
VOLUME GROUP: backup VG IDENTIFIER: 00016001a8daafb5
VG STATE: active PP SIZE: 64 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 135 (8640 megabytes)
MAX LVs: 256 FREE PPs: 0 (0 megabytes)
LVs: 1 USED PPs: 135 (8640 megabytes)
OPEN LVs: 0 QUORUM: 2
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per PV: 2032 MAX PVs: 16
$ lspv -l hdisk3
hdisk3:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
lv01 135 135 27..27..27..27..27 N/A

$ lspv hdisk3
PHYSICAL VOLUME: hdisk3 VOLUME GROUP: backup
PV IDENTIFIER: 00016001a8d88a2b VG IDENTIFIER 00016001a8daafb5
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 64 megabyte(s) LOGICAL VOLUMES: 1
TOTAL PPs: 135 (8640 megabytes) VG DESCRIPTORS: 2
FREE PPs: 0 (0 megabytes)
USED PPs: 135 (8640 megabytes)
FREE DISTRIBUTION: 00..00..00..00..00
USED DISTRIBUTION: 27..27..27..27..27
$

I dont understand what is going on, there should be enough space on backup vg. I only created one logical volume lv01 and I would like to create filesystem within that logical volume.

There is no data on this disk which is rather odd, is there something I am not doing right?

 

[Guest_imported]

KOG,

system readings shows you have no more disk space available (FREE PPs=0 megabytes). if possible, try to remove the LV you created and check again.

 

[bi]

What command did you use to create your filesystem? Your lsvg shows that there is one logical volume on this disk. Now you have to create the filesystem (/backup) for the logical volume to mount to.

I recommend using smit or smitty to create the FS. It's easier.

 

[AIXSPadmin]

The problem is that you are trying to create a filesystem that is larger than the given LPs. The largest your filesystem can be is 135LPs x 64MB. Make sure that you do not exceed this limit by even 1K or it will give you an error.

Here is a chart that I use for creating LVs/Filesystems (unfortunately it doesn't go up to 64MB partitions but you could easily calculate them); use the 512blk column for filesystem size:
GB MB KB 512blk 4MB-PP 8MB-PP 16MB-PP 32MB-PP
0.125 128 131072 262144 32 16 8 4
0.25 256 262144 524288 64 32 16 8
0.375 384 393216 786432 96 48 24 12
0.5 512 524288 1048576 128 64 32 16
0.625 640 655360 1310720 160 80 40 20
0.75 768 786432 1572864 192 96 48 24
0.875 896 917504 1835008 224 112 58 28
1 1024 1048576 2097152 256 128 64 32
1.125 1152 1179648 2359296 288 144 72 36
1.25 1280 1310720 2621440 320 160 80 40
1.375 1408 1441792 2883584 352 176 88 44
1.5 1536 1572864 3145728 384 192 96 48
1.625 1664 1703936 3407872 416 208 104 52
1.75 1792 1835008 3670016 448 224 112 56
1.875 1920 1966080 3932160 480 240 120 60
2 2048 2097152 4194304 512 256 128 64
2.125 2176 2228224 4456448 544 272 136 68
2.25 2304 2359296 4718592 576 288 144 72
2.375 2432 2490368 4980736 608 304 152 76
2.5 2560 2621440 5242880 640 320 160 80
2.625 2688 2752512 5505024 672 336 168 84
2.75 2816 2883584 5767168 704 352 176 88
2.875 2944 3014656 6029312 736 368 184 92
3 3072 3145728 6291456 768 384 192 96
3.125 3200 3276800 6553600 800 400 200 100
3.25 3328 3407872 6815744 832 416 208 104
3.375 3456 3538944 7077888 864 432 216 108
3.5 3584 3670016 7340032 896 448 224 112
3.625 3712 3801088 7602176 928 464 232 116
3.75 3840 3932160 7864320 960 480 240 120
3.875 3968 4063232 8126464 992 496 248 124
4 4096 4194304 8388608 1024 512 256 128

 

[KOG]

Hi folks

Many thanks for all your help and inputs, I will try creating filesystem first thing tomw morning.

Regards

Katherine

 

[AIXSPadmin]

I don't know how you are creating your filesystem, however, if you use the smit path:
storage management/filesystems/add change show/journaled filesystems/add to a previously defined logical volume/add a large file enabled filesystem

Then when you select your LV you will not be prompted for size and it will make the filesystem the size of the number of LPs allocated.

 

[Yegolev]

Star for AIXSPadmin, I think he noticed KOG was getting an error from mklv rather than crfs. That tells me that you did not use the smit path (what he said) about already-defined lv. I usually use that path, since I create the lv first and size it to my liking before putting a fs on top of it. Only because I prefer to calculate size in PP. IBM Certified -- AIX 4.3 Obfuscation

 

[KOG]

Hi,

I created LV first through smitty and then I followed the steps AIXSPadmin mentioned above except that I did not use this last command for creating filesystem

add a large file enabled filesystem

would that have made a difference?

I am new to AIX so I rely on smit to create Vgs, Lvs Fs etc.

At the mo I have a hard disk the size of 9gb and configured it to the following command

mkvg -s 64 -t 2 -y oracledata hdisk1

that generated 64mg PPs.

What size should the LV be or the filesystem for this vg?

Is it poss to create filesystem without creating LVs?

Thanking you all in advance.

Regards

Katherine

 

[AIXSPadmin]

On extremely large disks one would need to have a larger physical partition size because the number of logical partitions are limited on a physical volume, so if you had a 9GB disk and used 4MB PPs you would not use the entire disk 1016LPs x 4MB.

Logical volumes are necessary because the filesystem sits on top of the LV. LVs can span multiple Pvs. There is an option on the smit panel to create a filesystem without creating the LV first and doing this will generate an LV, say lv01 by the system. Using this method you need to know the size of the filesystem in 512 blocks when you create it.

 

[bi]

KOG, regarding the Large File Enabled Filesystem: If you think your filesystem is going to have files more than 2 GB, you should choose this kind of filesystem when you create it. If you don't and then you find you do have a file that is larger than 2 GB, you have to rebuild the filesystem. I learned this the hard way.

 

[KOG]

Hi bi,

I think you have solved my problem, will give it another try. Basically I am trying to create a LV for oracle backups only and that means using up most of the space on the 9gb disk.

Many thanks to all of your for your help.

Much appreciated.

Regards

Katherine

 

[AIXSPadmin]

Large file enabled filesystems are created if you will have any one file which will be from 2GB to 64GB in size (4.3.3) the limit grows for 5.1. If the filesystem is already created it will have to be recreated because this setting is made at FS creation time and cannot be changed later. I meant to address that in my posting before, but I am glad that 'bi' addressed the issue for you.

 

[KOG]

Hi folks,

I find the issue of LV and fs so confusing, and I am still stuck with this same problem over again (decided to have a break from it for few days and concentrate on oracle).

Now I have removed LV which frees some space on backup vg. Then I recreated one LV with the following characteristics,


LOGICAL VOLUME: lv01 VOLUME GROUP: backup
LV IDENTIFIER: 00016001a8daafb5.1 PERMISSION: read/write
VG STATE: active/complete LV STATE: closed/syncd
TYPE: jfs WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 64 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 135 PPs: 135
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: N/A LABEL: None
MIRROR WRITE CONSISTENCY: on
EACH LP COPY ON A SEPARATE PV ?: yes

I am trying to create one large filesystem within this LV. And I have followed the steps given by AIXSPadmin. But it failed?

# lspv hdisk3
PHYSICAL VOLUME: hdisk3 VOLUME GROUP: backup
PV IDENTIFIER: 00016001a8d88a2b VG IDENTIFIER 00016001a8daafb5
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 64 megabyte(s) LOGICAL VOLUMES: 1
TOTAL PPs: 135 (8640 megabytes) VG DESCRIPTORS: 2
FREE PPs: 0 (0 megabytes)
USED PPs: 135 (8640 megabytes)
FREE DISTRIBUTION: 00..00..00..00..00
USED DISTRIBUTION: 27..27..27..27..27

What is the best thing to do now? Remove LV and just create one large fs?

Thanking you all in advance.

Katherine

 

[Yegolev]

You look like you made the LV fine, it is 135 LP and not mirrored, 135PPx64MB=8.6GB. That is fine, you can mirror later. You then do `smit crfs` and pick the second option &quot;Add a Journaled File System on a Previously Defined Logical Volume&quot;. From there the 3rd option is &quot;Add a Large File Enabled Journaled File System&quot;. You then use F4 to pick your target lv from the list, specify your mount point, toggle &quot;Mount AUTOMATICALLY at system restart?&quot; to yes, if you want that. The rest should be fine at deafult. Let it cook for a while and when you get finished mount your fs.

If you want to pick through all of the LVM options you can do `smit lvm`. IBM Certified -- AIX 4.3 Obfuscation

 

[Batesy]

Remember you will need space for the jfslog, ideally this should be created first, but if not, it will be created when you create the first filesystem in the lv. You must leave some space for it though, 1pp is enough.

 

[KOG]

HI Yeg,

This is the exactly same method I used to create fs and it failed that is why I was so confused.

So at the end I removed LV and created fs alone and it worked !

Now I am having probs trying to create directories within /backup filesystem (when does probs ever end ! I seem to work better with Oracle.)

I have set the filesystem with read/write permissions but it does not make any difference. Any idea why?

# lslv lv01
LOGICAL VOLUME: lv01 VOLUME GROUP: backup
LV IDENTIFIER: 00016001a8daafb5.2 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: jfs WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 64 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 8 PPs: 8
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: /backup LABEL: /backup
MIRROR WRITE CONSISTENCY: on
EACH LP COPY ON A SEPARATE PV ?: yes
# lsfs /backup
Name Nodename Mount Pt VFS Size Options Auto
Accounting
/dev/lv01 -- /backup jfs 1048576 rw yes
no

PROBLEM !

# cd /backup
# ls
lost+found
# mkdir physical
mkdir: 0653-358 Cannot create physical.
physical: The file system has read permission only.
#

Thanking you all in advance.

Regards

Katherine

 

[Yegolev]

Make sure you have permission to write to the dir.

cd /
ls -l | grep backup
whoami

Make sure you are owner or in the group, and that you have write to /backup. Probably owned by root.system right now.

Just FYI, when you see a directory in ls, you are actually looking at a special file that contains a list of file/dir names and inode numbers. When you make a new file or dir &quot;inside&quot; that dir, the special directory file must be updated with the new file/dir and its inode, therfore you must have write permission on the dir to create either files or directories, even though you may be able to modify pre-existing files since that does not need a change to the dir special file. IBM Certified -- AIX 4.3 Obfuscation