topic Re: SAM Error in Operating System - HP-UX

SAM Error

remonsamir — Sun, 25 Dec 2011 12:56:54 GMT

i have a problem with SAM , when i tried to add new free lun to vg02 I have nots that the old lvols that in vg02 is now not active and when run bdf command it respond with

bdf: /backup1: I/O error
bdf: /backup2: I/O error
bdf: /backup3: I/O error

after reboot i cant see nuther vg02 nor lvols

I tried to creat another vg02 with full space but disks after reboot indicate that is unusd (IBM shark)

i have now these error when i tried to recreat vg02 or lvols

>>>>

The Logical Volume Manager shows this device file, /dev/dsk/vpath1,
with hardware path, , as belonging to Volume Group, vg02. SAM has
determined that this hardware path is not currently active because either the device is disconnected, or this is not the primary path to a multiple path physical volume. This results in incorrect disk
utilization information in the Disk Devices and Volume Group lists

>>>>

SAM now recognizes RAM discs. For more information on RAM discs see: │
    ramutil(1M) and ramdisc(7).
     WARNING: Data on RAM discs is not persistent across reboot. HP
     recommends not to have an FSTAB entry for FileSystems configured on
     RAM Disks (use the Modify Defaults option to uncheck "Mount at every
    system boot" checkbox).

conclusion ::

i create the vg02 and lvols and after reboot the disks marked as unused

os v: HP-UX v2 11.23

thanks for your time

Re: SAM Error

Dennis Handly — Sun, 25 Dec 2011 23:13:25 GMT

What does the /etc/fstab entries show for /backup1 /backup2 & /backup3?

Or did it never get entered? Because Mount at every system boot checkbox wasn't done?

Re: SAM Error

remonsamir — Mon, 26 Dec 2011 09:03:37 GMT

the /etc/fstab entries show

/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand vxfs tranflush 0 1
/dev/vg00/lvol5 /opt vxfs delaylog 0 2
/dev/vg00/lvol6 /tmp vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2
/dev/vg00/lvol4 /home vxfs delaylog,datainlog,largefiles,rw,suid 0 2
/dev/vg02/lvol0 /backup1 vxfs delaylog,datainlog,largefiles,rw,suid 0 2
/dev/vg02/lvol1 /backup2 vxfs delaylog,datainlog,largefiles,rw,suid 0 2
/dev/vg02/lvol2 /backup3 vxfs delaylog,datainlog,largefiles,rw,suid 0 2

but SAM still have this notification for the IBM shark disk

Hardware Number Volume Total │
│ Path of Paths Use Group Mbytes Desc

0/7/1/0/4/1.104.9.0.8.0.1 2 Unused -- 512000 IBM
0/7/1/0/4/1.104.9.0.8.0.3 2 Unused -- 512000 IBM