File System Problem

I am running SCo Open server release 5.
One of my filesystems has become beyond full and will no longer mount.
when fsck is run, I get the following error on phase 1
DANGER: Filesystem being checked is larger than the device in which it is stored(/dev/usr40). The filesystem is 59472K while the device is 58476K. Backup filesystem and recreate as soon as possible.

My questions are:
1) How do I back it up if I cannot mount it?
2) How has this error occured?

Please could somebody answer this as soon as possible as it is imperitive to my current project deadlines.

Is there just an easy fix?

Thanks in advance
andyjmAsked:
Who is Participating?
 
liuaihuiConnect With a Mentor Commented:
This error occured because your filesystem has damaged when system crashed.
you can use "fsck -ofull /dev/usr40" command to fix this problem,if it not work,you can use "fsdb" utility to correct filesystem error,but using fsdb must be at good at knowledge of filesystem disk layout,or you may be damage your filesystem.
I think you can follow this steps:
1>into single user mode;
2>#fsdb /dev/usr40
see s_fzise=58476, or s_fsize=59472 ?
if s_fsize=58476, then quit;
if s_fsize=59472,then
512B.p0e (this is fsdb command)
to see disk address 001004 if equal 59472;
001004   (this is fsdb command)
=58476     (this is fsdb command)
q        (this is fsdb command)
3>#fsck -ofull /dev/usr40

Note: before you do this, you must reference man page for "fsdb" utility.

    Good luck to you!
0
 
jlmsCommented:
I am not SCO expert, but here are some thoughts:

In Solaris you can backup filesystems that are not mounted. Maybe it could be the case in SCO. Read carefully the man page of your bachup command (no tar or cpio, but somethiung specifically designed to take care of filesystems).

 
0
 
andyjmAuthor Commented:
jlms
Have you any idea why this could have happened?
I'll try your suggestion
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
jlmsCommented:
No idea! If your machine crashed it could be that the i-node table of your filesystem was corrupted, but since I don't have any SCO experience in reality is very difficult to say ...
0
 
liuaihuiCommented:
Before using fsdb, you can use "Ghosts" utility to make a copy of your disk.
0
 
andyjmAuthor Commented:
liuaihui.

I managed to fix the problem by using dd to copy the raw data to another partition. Then running fsck /dev/usr60.
This then made the 300MB usr60 partition into a 59MB partition.
Rebuilt the usr40 partition with an extra 100MB, and copied the files using tar accross to usr40.

All works fine now.

Thanks for your answer. It was probably the only way I could have fixed it if I had not had enough space elsewhere.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.