Linux

Ask something
Discussion Locked

SCO Error code 28

0 helpful
9 replies

by bloggerdigest

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

With SCO OpenServer Enterprise 5.0.4 installed in IBM Netfinity server, it has been hang for few times. nothing display on the screen (blank screen).
After rebooting, the following messages display:
fsstat:/dev/u needs checking
mount:possible damage file system, mount failed
No space left on device (error 28)
/dev/u
HTFS file system : Volume
No partial Transaction pending
File system state set to OK
10360 files 2202075 blocks 2751446 free
***file system was modified***
mounted /u file system

Appreciated for advise.

9 replies

by cpfeiffe

It looks like your /u file system is getting full. Is this file system used for swap? Please reply to my alias with what this file system is being used for so I can further assist. It is likely that if it is swap all of your problems are caused by it just filling up. If not, there may be two problems with the file system. Either way it shouldn't be too hard to figure out. You should set up a cron job to routinely check the space available in /u and store it in a file or if possible email it to an account that is not local to the server in question.

Charles

by cpfeiffe

I don't know if you got my email responses. They were quarantined at your mail server. I emailed the postmaster, but I'm not sure that it got through. Basically I think you are out of swap space. 7 MB is not a lot of free swap. Typically, your screen locks up blank because you have no swap. The paging process loses its control over memory functions and you don't have enough of the Xserver in RAM to maintain the display. What happens next is you power cycle the machine to get it back up. That is damaging the /u filesystem and thus you see the output you are getting. Unix filesystems load their Super Blocks (headers) into RAM. They are changed there, but not always written back to disk immediately. Mismatches cause errors and fsckusually fixes it. I believe fsck is automatically fixing it when your system boots and thus /u mounts. You should create an additional swap file. A good formula for calculating swap in Unix is RAM + 1GB / 2 or RAM + 100MB whichever is greater. You know how much space you have available so bump this up the best you can. Good luck.

by roger.gibson

You might want to give the /u filesystem a check by using fsck -ofull This will repair any damage in the /u filesystem.

You can check for the precentage used in the /u filesystem by doing a df -v or you can search for large files by using a find command such as:

find /u -size +5000 -print

The you can see if you have any extreme files you can purge.

Good luck

by patubb

What is likely to be happening is a rouge process or program with a bug is filling all available space then crashing the system console. Note that fsck reports almost 1 1/2 GB free when it finishes.

It could also happen while trying to move largefiles around within /u. IE if you have 500 MB left free and try to mv a 600 MB file from, say, /u/abc to /u/def, then it will run out of space, since it will in effect copy the file 1st then delete the old version.

Swap space is unlikely to be involved here, *unless* someone has used 'marry' to attach a regular file under /u to the swap partition to increase available swap space.

This discussion is closed to new replies.