topic Re: LVM in Operating System - HP-UX

LVM

nightwich — Wed, 03 Mar 2010 16:09:14 GMT

Hi,

I have a rp7420 with 11iv3 ( B.11.31.0909 HP-UX Virtual Server Operating Environment)

I have SG and oracle installed.

I can see some stranges files under /dev/disk :

brw-r----- 1 bin sys 1 0x000000 Jan 13 13:48 disk64
cr-------- 1 root root 11 0x000000 Jan 15 16:21 disk64.pt
brw-r----- 1 bin sys 1 0x000001 Jan 13 13:48 disk65

brw-r----- 1 bin sys 1 0x000019 Jan 13 13:48 disk87
cr-------- 1 root root 11 0x000019 Jan 15 16:21 disk87.pt
brw-r----- 1 bin sys 1 0x00001a Jan 13 13:48 disk88

brw-r----- 1 bin sys 1 0x000026 Jan 13 18:20 disk98
cr-------- 1 root root 11 0x000026 Jan 15 16:21 disk98.pt

Any idea what are the files d*.pt ????

Thanks.

Re: LVM

Turgay Cavdar — Wed, 03 Mar 2010 17:00:16 GMT

"cr-------- 1 root root 11 0x000026 Jan 15 16:21 disk98.pt" they are character device files, which normally resides in /dev/rdisk directory. Any possibility for some administrator create them with manually with mknod command?

Re: LVM

nightwich — Wed, 03 Mar 2010 17:18:37 GMT

Hi turgay

I don't think so.
But let suppose yes, it is safelly to remove then ?

Two of those 3 disks are local disks were it is installed vg00 ( with mirror ).

I never see this tipe of files in none of other hpux machines.

Regards

Re: LVM

Turgay Cavdar — Wed, 03 Mar 2010 17:40:34 GMT

Hi,
I also have never seen files like that: disk*.pt

When you run "ioscan -m dsf" you should also see these devices "/dev/disk/disk98.pt" (if the major number 11 belongs to esdisk driver.) If you are not using raw device files with the name "/dev/disk/disk98.pt" then i dont think it is used by your system.(As you statet that they belong to vg00).

Device files created in Jan 15 16:21 , it may be good the activities on this day.

Re: LVM

nightwich — Wed, 03 Mar 2010 18:00:28 GMT

Hi again

When I run ioscan -m dsf, I don't get any the disk64.pt disk87.pt or disk98.pt.

If i do a vgdisplay -v vg00, I don't see any reference to those disks:

--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 4384
VGDA 4
PE Size (Mbytes) 16
Total PE 8750
Alloc PE 6904
Free PE 1846
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 1096g
VG Max Extents 70144

--- Physical volumes ---
PV Name /dev/disk/disk64
PV Status available
Total PE 4375
Free PE 923
Autoswitch On
Proactive Polling On

PV Name /dev/disk/disk98
PV Status available
Total PE 4375
Free PE 923
Autoswitch On
Proactive Polling On

It seems that is not used by my system. Although I think is best not remove the files. It's a productive system :S ..

After I close the threath I will assigned some points.

Regards.

Re: LVM

Turgay Cavdar — Wed, 03 Mar 2010 18:10:06 GMT

Hi,
Can you check with "lsdev", to see number 11 is belonged to which driver? (For character...)

Yes it is the safest way to not remove ...

Re: LVM

nightwich — Wed, 03 Mar 2010 18:14:29 GMT

The Output of lsdev:

Character Block Driver Class
0 -1 cn pseudo
1 -1 asio0 tty
2 -1 arp pseudo
3 -1 mm pseudo
4 -1 c8xx ext_bus
5 -1 ciss ext_bus
6 -1 dev_olar olar
7 -1 devkrs pseudo
8 -1 ehci usb
10 -1 eschgr autoch
11 -1 esctl ctl
12 1 esdisk disk

Any ideas !!?

Re: LVM

Turgay Cavdar — Wed, 03 Mar 2010 19:04:00 GMT

> 11 -1 esctl ctl

So your devices files are not "disk device files", they are controller device files.
What is "scsimgr get_info -D /dev/disk/disk64.pt" and "ioscan -m lun -d esctl" returning?

Re: LVM

nightwich — Thu, 04 Mar 2010 09:36:48 GMT

They return this:

scsimgr get_info -D /dev/disk/disk64.pt
SCSI services internal state = ONLINE
Device type = Direct_Access
EVPD page 0x83 description code = 1
EVPD page 0x83 description association = 0
EVPD page 0x83 description type = 2
World Wide Identifier (WWID) = 0x00000e1100d0f530
Serial number = "X1025532 0629"
Vendor id = "HP 73.4G"
Product id = "MAX3073NC "
Product revision = "HPC1"
Other properties = ""
SPC protocol revision = 3
Open count (includes chr/blk/pass-thru/class) = 1
Raw open count (includes class/pass-thru) = 0
Pass-thru opens = 0
LUN path count = 1
Active LUN paths = 1
Standby LUN paths = 0
Failed LUN paths = 0
Maximum I/O size allowed = 1048576
Preferred I/O size = 1048576
Outstanding I/Os = 0
I/O load balance policy = round_robin
Path fail threshold time period = 0
Transient time period = 120
Tracing buffer size = 1024
LUN Path used when policy is path_lockdown = NA
LUN access type = NA
Asymmetric logical unit access supported = No
Asymmetric states supported = NA
Preferred paths reported by device = No
Preferred LUN paths = 0

Driver esdisk Status Information :

Capacity in number of blocks = NA
Block size in bytes = NA
Number of active IOs = 0
Special properties =
Maximum number of IO retries = 45
IO transfer timeout in secs = 30
FORMAT command timeout in secs = 86400
START UNIT command timeout in secs = 60
Timeout in secs before starting failing IO = 120
IO infinite retries = false

ioscan -m lun -d esctl
Class I Lun H/W Path Driver S/W State H/W Type Health Description
=====================================================================
ctl 2 64000/0xfa00/0x3 esctl CLAIMED DEVICE online DGC CX3-20
1/0/6/1/0.0x5006016841e01da4.0x0
1/0/14/1/0.0x5006016041e01da4.0x0
/dev/pt/pt2

This means ?

Tahks for your cooperation.

Re: LVM

Turgay Cavdar — Fri, 05 Mar 2010 07:58:40 GMT

Hi,
disk87.pt has a mojor nubmber of 11 which belongs to esctl so this is not a disk device file. As you can see from the scsimgr get_info output:
Capacity in number of blocks = NA
Block size in bytes = NA

Probably you won't get normal results for "diskinfo /dev/disk/disk68.pt". You can not use this device file for io. So we can say that your system probably not using it.
Lets wait someone on the forum may comment on the issue.