So it looks like I was wrong. When I do du -sk/dev it shows 314. If I understand correctly, the -k means display in kb? In that case, I am far below 60 MB.

the results of df -k is this:

Code:

/dev/dsk/c0t0d0s0     106047 kB   105799 kB 0 avail 100% /
/dev/dsk/c0t0d0s6     587382 kB   387151 kB 141493kB  74%  mounted on /usr
/proc      0kB   0kB    0kB avail  0%  mounted on /proc
fd           0kB   0kB    0kB avail  0% mounted on /dev/fd

the other machine I am managing, which is up and running looks like this with th df -k

Code:

/dev/dsk/c0t0d0s0    106047kB 104249kB 0kB avail 100%  /
/dev/dsk/c0t0d0s6    587382kB 408453kB 120191kB avail mounted on /usr

why does one have a problem and the other not, when both are full? There is a difference of 1.5MB more on the station that I can't login vs the one I can. I guess that can be the difference. You mentioed a couple of other things to look at, which I will try.

thanks.

---------- Post updated at 10:40 AM ---------- Previous update was at 09:51 AM ----------

trying the

Code:

ls -l |grep ^-r |wc -l command

shows

Code:

-r: not found

Is there something I should be looking for when doing the prtconf and prtvtoc? I entered the command prtconf and see devices, with one of three messages after: (driver not attached), instance #0, and insance #1. Prtvtoc shows

Code:

usage: prtvtoc [-fhs] [ -t fstab] [-m mnttab] rawdisk...

I am not sure what to get from that. I feel like such an unschooled newbie!

---------- Post updated at 11:11 AM ---------- Previous update was at 10:40 AM ----------

Another thing. Someone suggested doing the df -k, and finding the full disk, and fsck -y, which I did:

Code:

# fsck –y /dev/dsk/c0t0d0s0
1
2
3
4
5 (I don't remember what this says, but the message after always happens after a reboot.)
 FILE SYSTEM STATE IN SUPERBLOCK IS WRONG.  FIX? YES

I have done the fsck -y command several times, and always after a reboot, it gives the file system state in superblock is wrong. It repairs it. I could type fsck -y again, and it is fine. I will reboot the system, and do fsck -y, and I will receive the same file system state in superbock is wrong, and it repairs it. Once I did not do the fsck -y, and when I went to boot up, I saw a superblock is wrong error. Could this be the cause or result of a problem?

Thanks,

Moderator's Comments:

Please use code tags also on generated output, data, logs etc, thanks.