Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

Which Disk and Filesystem

admin1979
Super Advisor

Which Disk and Filesystem


Hello,

We are using TRU64 Digital UNIX V4.0F system.
I have been seeing the below error since few days and suspect that one of the disk is going to get corrupt.

Here is the error,

----- EVENT INFORMATION -----

EVENT CLASS ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 39935.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Sat Dec 2 00:35:36 2006
OCCURRED ON SYSTEM REPO
SYSTEM ID x00080022
SYSTYPE x00000000

----- UNIT INFORMATION -----

CLASS x0022 DEC SIM
SUBSYSTEM x0000 DISK
BUS # x0003
x00E8 LUN x0
TARGET x5

I am not so comfortable with TRU64 but I can see that the disk having bus 03 Lun 0 and Target 5 is the disk in question.

I also did this,

# scu show edt

CAM Equipment Device Table (EDT) Information:

Device: CRD-8402B Bus: 1, Target: 0, Lun: 0, Type: Read-Only Direct Access
Device: BD009734A3 Bus: 2, Target: 0, Lun: 0, Type: Direct Access
Device: BB00911CA0 Bus: 3, Target: 0, Lun: 0, Type: Direct Access
Device: BD0366774C Bus: 3, Target: 1, Lun: 0, Type: Direct Access
Device: BD0366774C Bus: 3, Target: 2, Lun: 0, Type: Direct Access
Device: BD0366349C Bus: 3, Target: 3, Lun: 0, Type: Direct Access
Device: BD0366349C Bus: 3, Target: 4, Lun: 0, Type: Direct Access
Device: BB01813467 Bus: 3, Target: 5, Lun: 0, Type: Direct Access
Device: TLZ10 Bus: 4, Target: 4, Lun: 0, Type: Sequential Access
Device: TLZ9 Bus: 4, Target: 5, Lun: 1, Type: Medium Changer
Device: TLZ10 Bus: 4, Target: 6, Lun: 0, Type: Sequential Access


So it seems , the disk exists there. But now our question is which is this disk? And which filesystem it is holding on? And how do we prevent any loss of data.

Kindly suggest.


Thanks,
Sac
10 REPLIES
Vladimir Fabecic
Honored Contributor

Re: Which Disk and Filesystem

This is:
Device: BB01813467 Bus: 3, Target: 5, Lun: 0, Type: Direct Access

Please post /etc/fstab
In vino veritas, in VMS cluster
admin1979
Super Advisor

Re: Which Disk and Filesystem


Hello,

Thanks for the reply. Yes it surely is that disk. But which filesystem it has and hwo do we identify it.

Please find the attach for the information you need.
Vladimir Fabecic
Honored Contributor

Re: Which Disk and Filesystem

This disk is rz29 (3*8+5).
You have two domains on rz29:
usr_domain
opt_domain
So, effected file systems are:
/usr (usr_domain#usr)
/var (var_domain#var)
/opt (opt_domain#opt)
And how do we prevent any loss of data?
Backup data using "vdump".
And also post output of:
# disklabel -r rz29
In vino veritas, in VMS cluster
admin1979
Super Advisor

Re: Which Disk and Filesystem


Wow....I didnt know this concept of rz??.
I have no where found this concept in the docs...Can you point me out to any tru64 doc which describes this concept please.

Here is the output you need.

# disklabel -r rz29
# /dev/rrz29a:
type: SCSI
disk: BB018134
label:
flags: dynamic_geometry
bytes/sector: 512
sectors/track: 254
tracks/cylinder: 20
sectors/cylinder: 5080
cylinders: 7001
sectors/unit: 35565080
rpm: 7173
interleave: 1
trackskew: 54
cylinderskew: 54
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0

8 partitions:
# size offset fstype [fsize bsize cpg] # NOTE: values not exact
a: 131072 0 unused 0 0 # (Cyl. 0 - 25*)
b: 262144 131072 unused 0 0 # (Cyl. 25*- 77*)
c: 35565080 0 unused 0 0 # (Cyl. 0 - 7000)
d: 10000000 393216 AdvFS # (Cyl. 77*- 2045*)
e: 25000000 10393216 AdvFS # (Cyl. 2045*- 6967*)
f: 0 0 unused 0 0 # (Cyl. 0 - -1)
g: 17585932 393216 unused 0 0 # (Cyl. 77*- 3539*)
h: 17585932 17979148 unused 0 0 # (Cyl. 3539*- 7000)


I will surely take the vdump of the required filesystems. Anything you would like to add to it??
Anything like mirroring and all?
Vladimir Fabecic
Honored Contributor

Re: Which Disk and Filesystem

Do not think you can do mirroring since you are not using LSM.
Since it is /usr that is affected you will need OS installation CD for data restore.
So check is everithing OK with your CD drive and OS instalation CD.
You will need output of disklabel while creating partitions on new disk.
In vino veritas, in VMS cluster
Stephen_126
Occasional Advisor

Re: Which Disk and Filesystem

That error happeded on :
OCCURRED/LOGGED ON Sat Dec 2 00:35:36 2006

It's a 199 scsi error years ago. This could be as simple as a scsi reset causing it.

(BTW: upgrade if you can.)
To track disks to mounts...

hwmgr -v d | grep disk <== will show disks with first active scsi path

hwmgr -show scsi [ -full [ -id ### ]] | more <== will show scsi mappings/paths

ls -l /etc/fdmns/*/* <== will show advfs domain to disk mapping. So will showfdmn/showfset commands but thisis quicker although the ls will show abandoned domains.

df -h (or showfdmn) will show AdvFS domain to Fset relationships (look for pound sign in df "device" field. (first field)
admin1979
Super Advisor

Re: Which Disk and Filesystem

Thanks Stephen for the info.
But the hwmgr commands will not work in V4.0.
so any other alternative to get this info in V4.0?


- Sac
admin1979
Super Advisor

Re: Which Disk and Filesystem


Still hoping for the reply.

Thanks,
Sac
DCBrown(2)
Occasional Visitor

Re: Which Disk and Filesystem

Could try scu

# scu
scu> show edt

Probably the closest thing to hwmgr in V4 stream.

bud
Khairy
Esteemed Contributor

Re: Which Disk and Filesystem

i think others have pointed out which disk is failling in your system.

Another way to check where is your fs is residing is via showfdmns

# cd /etc/fdmns
# showfdmn * | more

Rgds