Re: [foxboro] /rem/r0 File system error?
- From: "tjvandew@xxxxxxxxx" <tjvandew@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Mon, 12 Nov 2007 20:39:46 -1000
Duc,
Since rem/r0 is normally used as a remote mount point for other file
systems I'm curious to know what you get if you type in rmount.
Does anything show up for /rem/r0 ? I remember back in AP-20 days when
something was hosed with rmount and it trashed the mount point. Even if
rmount returns nothing for /rem/r0 try rumount /rem/r0 and see if that
helps anything. You've probably already done all of this but I thought
I'd see if my fading memory could still be of some assistance to your
more youthful, (and useful), brain. Let all of us know the final
outcome please. Worst case, the hard drive is going flaky and you are
about to get more experience rebuilding one for that box. BTW, I
noticed before I left that 17AW01 was installed upside down. Flip it
over and see if the problem switches to /rem/r1 ;<)
Cheers,
Tom
duc.do@xxxxxxxxxxxxxx wrote:
> Hi list,
>
> I got an AW-51B box that went flaky on me and it's got me perplexed.
> Seems like /rem/r0 is corrupted per these responses:
>
> 17AW01# cd /rem
> 17AW01# ls -lad r*
> r0: Bad file number
> drwxrwxr-x 2 root staff 512 Jun 8 1999 r1
>
> 17AW01# rm -r r0
> r0: Bad file number
>
> 17AW01# rm -r ./r0
> ./r0: Bad file number
>
> 17AW01# mv ./r0 ./r00
> mv: cannot access ./r0
>
> There's no problem with /rem/r1:
>
> 17AW01# rm -r r1
> 17AW01# mkdir r1
>
> 17AW01# ls -ld r1
> drwxr--r-- 2 root other 512 Nov 12 16:27 r1
>
> I shut it down to single user and ran fsck. Nothing is flagged as wrong
> or corrupted (aside from the usual "FILE SYSTEM STATE IN SUPERBLOCK IS
> WRONG; FIX?" message).
>
> I've also rebooted it completely (-i6) without any improvment.
>
> Pertinent information:
>
> AW-51B running V6.2.1 (Solaris 2.5.1). Plenty of disk space:
>
> 17AW01# df -kt
> Filesystem kbytes used avail capacity Mounted on
> /dev/md/dsk/d0 49855 15539 29336 35% /
> /dev/md/dsk/d4 822151 274368 465573 38% /usr
> /proc 0 0 0 0% /proc
> fd 0 0 0 0% /dev/fd
> /dev/md/dsk/d2 37927 13949 20188 41% /var
> swap 231976 84 231892 1% /tmp
> /dev/md/dsk/d5 2719925 692877 1755058 29% /opt
>
> Any idea? Thanks!
>
>
> Duc
>
> --=20
> DCS Group
> Carrollton Plant
> Dow Corning Corp
> Carrollton, KY, US=20
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list: http://www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
>
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: http://www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
- References:
- [foxboro] /rem/r0 File system error?
- From: duc.do
Other related posts:
- » Re: [foxboro] /rem/r0 File system error?
- » Re: [foxboro] /rem/r0 File system error?
- » Re: [foxboro] /rem/r0 File system error?
- » Re: [foxboro] /rem/r0 File system error?
- » Re: [foxboro] /rem/r0 File system error?
- » Re: [foxboro] /rem/r0 File system error?
- » Re: [foxboro] /rem/r0 File system error?
- [foxboro] /rem/r0 File system error?
- From: duc.do