extendfs

[Oliver Schmitz]

Dear all,

I started a thread and gave points for your nice answers in http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1056402

However, this thread is not yet finnished bacause I can not extend the file system.

First my problem was that I could not unmount /home. I found after your helpfull answers that other NFS were mounted inside home. After unmounting them it runs fine.

Then I used SAM to increase the available disk space for the lvol of /home. Subsequently I performed

$extendfs -F hfs /home and it gives: extendfs hfs: error: character special file required.

The special file is on the right place in /dev/vgraid. Does anyone sees a reason why this error occurs or does anyone have an idea what could be the problem?

Thanks for further help. I need our /home back!

BR,
Oliver

[Luk Vandenbussche · Accepted solution]

Oliver,

The command is

extendfs -F hfs /dev/vg00/rlvolX

X = number off the logical volume of /home
You can check this in /etc/fstab

[Yang Qin_1]

Hi, Oliver,

Make sure your /home FS type is "hfs" but not "vxfs". If you use a wrong FS Type, even you run "extendfs -F hfs /dev/vg00/rlvolx" it will not work.

To check FS Type, run "cat /etc/fstab | grep home"

Regards,
Yang

[Oliver Schmitz]

Dear Luk,

in /etc/fstab I found the device special file /dev/vgraid/lvol_home for my /home fs.

I did extend -F hfs /dev/vgraid/lvol_home and got again the message that a character special file is required.

I tried the same with the lvol of /opt (special file /dev/vg00/lvol16) and it doesn't work either.

Any additional idea?

Thanks and regs,
Oliver

[Victor BERRIDGE]

Hi Oliver,

There is a thing I dont understand here, if you have inceased the size of your logical volume using SAM, then SAM automaticaly has extended your filesystem for you... (so the error would be : It is already this size...)

Now the error character device special file required means you have entered the block device: ~/vgXX/lvolyy id block

~/vgXX/rlvolyy is character (notice the "r" in front of lvol?

All the best
Victor

[MarkSyder]

Oliver,

Read Luk's answer again: it's not the lvol file, it's the rlvol file.

Mark Syder (like the drink but spelt different)

[Luk Vandenbussche]

Like Marc said

extend -F hfs /dev/vgraid/rlvol_home

[Oliver Schmitz]

Folks,

thanks really a lot for your advices. Certainly I had to take the raw device file. extendfs run with that at least to some point. Then I got a different error:

extended size to 64000 MB (from 20000)

extendfs -F hfs /dev/vg00/rlvol_home

starts to run and shows a lot of numbers ...
stops at ...., 65535152,
read error: 943063040
rdfs:No such device or adress


Do you have any ides by what this might be caused?

Thanks for help, I am lost...
Oliver

[IT_2007]

So are you trying to extend from 20GB to 60GB?

Do you have enough free space on that filesystem? Also check /tmp isn't filled out.

once you unmount /home and then you need to run the following commands:

umount /home
lvextend -L /dev/vgXX/lvolYY
extendfs -F vxfs /dev/vgXX/lvolYY


Remember that "hfs" is only for /stand and not for /home. You need to change to vxfs in the extendfs command.

[Oliver Schmitz]

Dear IT-2007,

the existing file system is hfs. What will happen if I extend now with vxfs?

Thanks for confirmation,
Oliver

[IT_2007]

Don't think you would be able to run extendfs. Feel there might be size limitation. You need to check with HP.

[Oliver Schmitz]

Hi again,

there is enough space on the FS (almost 800 GB). However, I would like to make a sufficient user space management. Unfortunately I run into this kind of very strange problems with basic system functoins. I really argue on that...

I hope you or anyone else have another idea. It really makes the system unusable.

With whom at HP could I check?

BR,
Oliver

[Pete Randall]

Just to confirm the file system type - run the fstyp command:

fstyp /dev/vgraid/lvol_home

It should return either hfs or vxfs.


Pete

[Yang Qin_1]

Hi, Oliver,

To be able to help you, would you please provide us the output of commands:

cat /etc/fstab | grep home
and
lvdisplay /dev/vg00/lvol_home

Regards,
Yang

[Jonathan Fife]

HFS filesystems can be up to 256GB (http://docs.hp.com/en/B2355-60105/mkfs_hfs.1M.html?jumpid=reg_R1002_USEN), so the problem is probably that the logical volume hasn't been extended yet.

If you do an lvdisplay /dev/vg00/lvol_home it should give you the size of the lvol and how many free extents there are.

As for the vxfs vs. hfs comments -- it shouldn't matter if you are using HFS. If it actually becomes a problem there is a tool (vxfsconvert) that can convert a filesystem from hfs to vxfs. Like I said, though, that shouldn't be an issue.

[Victor BERRIDGE]

Hi again,
>"here is enough space on the FS (almost 800 GB). However, I would like to make a sufficient user space management. Unfortunately I run into this kind of very strange problems with basic system functoins. I really argue on that..."

I suppose you ment volume group...
My concern here is you are in HFS well there are some limitations such as size:128GB
and more specificaly you must unmount to extend , after a crash the time to do fsck is exponential with size (so very big takes ages... I remembered staying up very late once the system took 5 hours...) and has a limited number of inodes per file system...

I see only one solution: create a vxfs filesystem and restore/copy /home in it then mount this new vxfs filesystem on /home...


All the best
Victor

[Victor BERRIDGE]

Hi Jonathan,

I see the limit has been raized then? or is it specific to 11iv2?
I just realised we are discusssing of an issue not knowing anything of the OS nor architecture, which could help us understand a bit better (patching etc...)

[Victor BERRIDGE]

I just found a doc that says 128GB (just for info...)
http://docs.hp.com/en/5971-2383/5971-2383.pdf


All the best
Victor

[Jonathan Fife]

Victor,

Very curious -- I guess this note says it all: "Although it may be possible to create files or file systems larger than these documented limits, HP does not support such files and file systems, and the results of using them may be unpredictable."

I'm glad I use VxFS for everything but /stand, then :)

In any case, all of this is academic as Oliver is only trying to extend to 64GB, which is well under both the supported and unsupported size limits.

[Oliver Schmitz]

Dear all,

I really appreciate this great help of all of you. However, I couldn't yet solve the problem.
Therefore I collected the information which some of you requested to have a better insight.

1.)
I did
$fstyp /dev/vgraid/lvol_home and it says that I have hfs


2.) The output of
$ cat /etc/fstab |grep home is posted in the attached file fstab_home.txt

and the output of
$lvdisplay /dev/vgraid/lvol_home is posted in the attached file lvdisplay.out

I hope this helps some of you to resolve inconsistencies (meanwhile I treid to come to 70 GB).

Meanwhile I come to the conclusion that there is something very strange and therefore I am thinking on creating a new lvol for /home (maybe with vxfs) and copy all the stuff to this new home. I have two questions concerning this:
- How can I copy everything with keeping all permissions unchanged?
- What will (most likely) happen with the other lvol. I don't want to loose the discspace. Any idea how I could clean this up and use it again?

Thanks again for your help. I hope to get into work with this WS soon. It is really disapointing!

Oliver

[Oliver Schmitz]

Dear all,

I really appreciate this great help of all of you. However, I couldn't yet solve the problem.
Therefore I collected the information which some of you requested to have a better insight.

1.)
I did
$fstyp /dev/vgraid/lvol_home and it says that I have hfs


2.) The output of
$ cat /etc/fstab |grep home gives

/dev/vgraid/lvol_home /home hfs rw,suid,nolargefiles 0 2
/dev/vgraid/lvol_olidat /home/schmitzo/auswertungen/database hfs rw,suid,nolargefiles 0 2
ipp049:/home/pph105/textor/ /TEXTOR_DATA/save_ipp049_vxidata nfs rw 0 2
ipp049:/home/pph105/textor/rud/raw_data /TEXTOR_DATA/vxipsi_data/rud_data nfs rw 0 2
ipp049:/home/cbusch/prg_c /home/cbusch/cprogs nfs rw 0 2


and
$lvdisplay /dev/vgraid/lvol_home gives:

--- Logical volumes ---
LV Name /dev/vgraid/lvol_home
VG Name /dev/vgraid
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 70000
Current LE 4375
Allocated PE 4375
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default


I hope this helps some of you to resolve inconsistencies (meanwhile I treid to come to 70 GB).

Meanwhile I come to the conclusion that there is something very strange and therefore I am thinking on creating a new lvol for /home (maybe with vxfs) and copy all the stuff to this new home. I have two questions concerning this:
- How can I copy everything with keeping all permissions unchanged?
- What will (most likely) happen with the other lvol. I don't want to loose the discspace. Any idea how I could clean this up and use it again?

Thanks again for your help. I hope to get into work with this WS soon. It is really disapointing!

Oliver

[Yang Qin_1]

Hi, Oliver,

use tar to make a backup of home

cd /home
tar -cfv /var/adm/crash/home.tar *

create a new lvol, unmount old /home and mount /home with newly created lvol. Modify /etc/fstab accordingly (use vxfs instead of hfs).

cd /home

tar xfv /var/adm/crash/home.tar

I hope /var/adm/crash is big enough for home.tar. If not, you may use a tape:

tar cfv /dev/rmt/*mn

After you verify /home and make sure everything is OK, you can run lvremove to remove lvol used by old /home and in this way, you will not lose your diskspace.

Regards,
Yang

[Victor BERRIDGE]

Hi again,
Since it is not enabled for large files,I would suggest you create your new filesystem, mount it lets say on /tmpmnt then use cpio:
cd /home;
find . -print|cpio -pdmulv /tmpmnt


All the best
Victor

[Victor BERRIDGE]

And of course ( I forgot to add -but quite sure you guessed...)
umount /home/whatever els is mounted
umount /home
umount /tmpmnt
mount /dev/vgYY/lvolYY /home # your new lvol you mounted on /tmpmnt
mount the rest
update /etc/fstab

All the best
Victor