Free space to LV not showing.

[themoe]

Heya all.

Quick question. I have roughly 36 gigs free space and using wsmstorage I placed 2000MB each to two different lvs I had. I unmounted both directories prior to the update/add of data and I remounted them both after I successfully added the space.

Both are still showing full via df -tk and the wsmstorage interface [even after a reload]

I have not rebooted the machine. Should I?

 

[PSD]

themoe,

Try:

fuser -dV /dev/<lv name>

Cheers
PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP

 

[themoe]

Only responce is a mirror of the command...

/dev/lv05
/dev/lv02

Nothing else.

 

[Yegolev]

if i understand you properly, you increased the size of the lv but you did not do anything to the filesystem. i find it easiest just to add space directly to the fs using `chfs -a size=somenumber /my/fs`, and my knowledge of websm is pretty nonexistent. i suggest adding space to the fs itself, but you did not mention if the total fs capacity increased, just the df output being full.

there is no reason to reboot as long as you can get processes and users out of that filesystem. IBM Certified -- AIX 4.3 Obfuscation

 

[themoe]

Yegolev-

I just tried you chfs idea and it worked wonderfully.

Prior to my changes a df -tk showed %100 percent full on
/my/directory it was around 2.1 gig.

I used wsmstorage to add 2.0 gig to that filesystem [lv02]

Nothing ever happened and after remounting after the &quot;add&quot; my df -tk still showed 2.1 gog and %100 useage even though I visably saw my OVERALL free space drop by 2.0 gig.

Now after just complint a chfs I visably see the difference with a df -tk and my overall free diskspace remains the same...so What I was thinking was that by using wsmstorage I only told the /my/directory how large it could grow to...

Make sense?

 

[bi]

Yes, that makes sense.

One problem of using just the chfs command to increase space in a filesystem is that you have absolutely no control over which disk(s) the filesystem is extended to, unless there is only one or two disks in the volume group. Extending a filesystem onto the &quot;wrong&quot; disk can have performance consequences for a database.

So, if you need to control which disk(s) your filesystem is on, extend the logical volume first, and don't forget to change the filesystem to fill up the extended logical volume. (I always run the lsfs -q <mount point> to see the number of blocks the LV has vs. the number the filesystem has before I run the chfs command. You don't have to do the math for the chfs command!)

 

[Yegolev]

of course, if you are going to follow bi's ideas, which are good ones, you will want to read up on LVM and get a thorough understanding of what you can and should do. lucky me, i can let the EMC frame handle striping and mirroring, so please do not use me as an example of a good admin. IBM Certified -- AIX 4.3 Obfuscation