Re: [foxboro] /rem/r0 File system error? - Problem resolved

The problem observed with the mount point /rem/r0 on 17AW01 was actually
caused by a problem in another host, 04AW01, when we tried to rmount it
on 17AW01.

To make a long story short, there were a couple of files in
/usr/fox/exten/config on 04AW01 that didn't have the necessary
information for 04AW01 to know which network it should run in. The file
/usr/fox/exten/config/swi_pars.cfg looked like this:

STA_PSAP_ADDRESS=3D
STA_LETTERBUG=3D
CMX_STAND_ALONE%
STA_LOGICAL_MAC_ADDRESS=3D00006c

instead of:

STA_PSAP_ADDRESS=3DI000104
STA_LETTERBUG=3D04AW01
CMX_STAND_ALONE%0
STA_LOGICAL_MAC_ADDRESS=3D00006cC04E22

And these four lines are appended to loadable.cfg in the same directory.

Russ Boulay pointed us to the culprit and it's a simple manual edit to
add the necessary info and reboot to fix the problem.

Why these files were changed thus? I can only speculate, but it appears
the script file /config_IA was run unknowingly several weeks back
without the necessary command line parameters to build the file
swi_pars.cfg. (If only I can determine the knucklehead who did that!)

This script file is not meant to be run manually, but there's nothing to
keep one from doing so. Lesson learned!

Searching through the freelists.org archive I saw David Johnson also ran
across a similar problem back in 2005. So we're not alone in getting
hosed by this trap.

Duc

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of duc.do@xxxxxxxxxxxxxx
Sent: Monday, November 12, 2007 4:29 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] /rem/r0 File system error?

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=3D20
=20


=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

Other related posts: