SCO Server: /u file system missing

UNIX SCO
1

Hello All,

I have a SCO Unix server and when I do the command

"df -kP" I get the following:

Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/root 2048000 934936 1113064 46% /
/dev/boot 15360 6419 8941 42% /stand

It should say

Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/root 2048000 862141 1185859 43% /
/dev/boot 15360 6097 9263 40% /stand
/dev/u 32957302 1569442 31387860 5% /u

In other words I am missing my /u filesystem.

Now funny thing is I can cd /u and "ls -l" the directory.

xxxxxxx(mikep9) /u% ls -l
total 12
drwx------ 3 informix informix 512 Jul 25 2006 db_scripts
drwxrwxrwx 64 root sys 1536 Dec 22 17:10 home
drwx------ 5 root informix 512 Apr 8 2005 optifacts
drwx------ 3 root sys 512 Aug 14 2008 root
drwxrwxrwx 7 informix informix 512 Feb 17 13:07 tmp

So /u exist but is not mounted for use. I don't know how it become unmounted.

My question is can I do a "mountall" command to remount the /u directory or do I have to use the Filesystem manager to remount the directory?

xxxxxxx(mikep9) /u% uname -a
SCO_SV usf0550 3.2 5.0.6 i386

thanks

2

The /u directory should be empty, so that /dev/u may be mounted.
When you have entries in /u, mounting /dev/u on /u will make the entries in /u disappear.
To solve this problem, with /dev/u not mounted, move all the contents of /u somewhere, then do mountall.
If mountall fails, run fsck /dev/u and try to mount again.
Then decide if you need the files that you saved.

If /dev/u is a second hard drive, there is the possibility that it has died.

3

thanks jgt.

>When you have entries in /u, mounting /dev/u on /u will make the entries in /u disappear.

Are you able to explain the theory on why the entries in /u will disappear in /dev/u if mounted?

4

I might be guessing here, but I think the theory is that /u was unmounted but stuff was written to the /u _directory_. YOu need to clear that directory, and remount /u and then if you want the files you cleared out, then copy them back in.

5

you might want to look at /usr/adm/messages, which is a record of bootup hardware stuff since the system was built or the file was last pruned. You should see an attempt to attach the 2nd drive or 2nd file system, whichever you have.

From your description, you may have attempted a data restore to /u when /u file system was not mounted, leading to stuff being dumped into the directory on the root filesystem. But this isn't a recent thing or the blocks used in root would be the total of the previous blocks used on root plus the blocks used on /u.

From root you could do a "l (L) /dev/hd* and see what hard drive device entries you have and if there is a second hard drive divvy one of the hardware entries to see what divisions are on the drive.