topic Re: root file system corruption in Operating System - HP-UX

root file system corruption

Manal hassan — Wed, 03 Nov 2010 12:16:33 GMT

hello all,

I have hpux server 10 the problem is :
the application can not be running and after checked i noted root file system reached to 100% and after reducing to 92%the and then removed all files in the lost+found directory the problem still not fixed and during the system rebooting this messages were appeared
- files system(s) Not properly shutdown Beginning file system repair.
- sorry: no space IN lost+found directory
/sbin/fsclean lvol3 not Ok , run fsck.
- unexpected Inconsistency ; run fsck Manually
-Could not fix file system with fsck -p, Run fsck Interactively
loging in As root for Manual fsck , Enter ^D when file system fixed .
please help me what can i do?
thanks a lot
Manal

Re: root file system corruption

SoorajCleris — Thu, 04 Nov 2010 05:11:14 GMT

Hi,

try to do an fsck using recovery DVD/Ignite backup.

If not working , restore the backup.

Regards,
Sooraj

Re: root file system corruption

Dennis Handly — Thu, 04 Nov 2010 07:37:26 GMT

>then removed all files in the lost+found directory

Ack!, how did you do this?
You can't remove the directory, only the content. Otherwise you have to use mklost+found(1M).

But you now may be stuck. :-(

Re: root file system corruption

Manal hassan — Thu, 04 Nov 2010 12:54:32 GMT

i removed all files in lost+found directory and i kept directory as the same and previous messages after i did that .

Re: root file system corruption

Shibin_2 — Fri, 05 Nov 2010 02:22:58 GMT

Can you do further more housekeep and reduce the root file system? Then try to do fsck again, may be with "-o full" option.

If still not working, then you may have to restore from ignite.

Re: root file system corruption

Ismail Azad — Wed, 10 Nov 2010 15:32:59 GMT

Typically as you know root logical volume extents are contiguous and hence you cannot extend the size of the root file system. Looking at the nature of the problem it seems that you can run fsck with the different levels of intent logs option. Possibly this one,
fsck -F vxfs -o full,nolog /
Instead of replaying the intent log, now the fsck will scrutinize the file system in every way , each file system one by one.

Hope this helps you out,

Regards
Ismail Azad