Change Inode Size

[jhuihuihi]

Dear all,

My inode size of / is full
Is it possible to resize inode by ignite tape ?

Thanks,

Otong

[Jeff Schussele]

Hi,

Yes - but for you to run out of inodes your / filesystem must be HFS. You really should be using VXFS which has an unlimited inode capability. Switching filesystem type is another thing you could and should do during an Ignite restore.

Rgds,
Jeff

[Sundar_7]

Otong,

As mentioned above, you will run out of inodes only on HFS filesystems. VXFS filesystems dynamically create inodes, so you can keep creating files as long as you have enough free space in the fs.

There are options to increase the number of inodes for a HFS filesystem. They are available when you are manually creating the filesystem, but not sure if you will get to change those params while restoring from ignite.

Preferred way would be to restore from the ignite tape and specify the / as a VXFS filesystem.

-- Sundar.

[jhuihuihi]

Dear Jeff & Sundar,

Many thanks for your reply,
but my current O.S is HP-UX 10.20. So is it still possible to convert fs from HFS to VxFs ?

Best regards,

Otong

[Sundar_7 · Accepted solution]

Yes, you can have / as a VXFS filesystem even on 10.20. Only your /stand must be HFS.

I am little skeptical about changing the filesystem type during the restore though for in ignite-ux is going to restore the old /etc/fstab from the archive that is going to have the entry for / as HFS.

How about if you create a new tapee with the modified /etc/fstab to reflect / as VXFS filesystem and convert / while restoring from the tape.

[Bill Hassell]

Are you using standard LVM volumes for your filesystems or do you have one giant / filesystem for everything? If you have standard LVM mountpoints like /var /tmp /opt, etc, then / has been infiltrated with bad files and directories. The / directory is defined as static (almost never changes size) and no more than 50 to 150 megs is needed, with only 25-35 megs occupied (and inodes = 3000 or so). When / fills up, either inodes or occupied space, something has gone wrong and needs to be fixed. The most common problems are misspelled backup sessions (/dev/rmt/om rather than 0m) and bad software installations that do not use /opt or /usr/local or /usr/contrib.

As mentioned, you can reinstall from a make_tape_recovery tape and change the root filesystem from HFS to VxFS. But before you make the tape, change fstab. The order is important:

- change fstab
- make_tape_recovery
- shutdown and bootup the MTR tape
- change the root filesystem type

And all should be OK. But you can save yourself a lot of work and offline time by cleaning / from all the wrong files and directories.