Re: [Veritas-vx] What are all these msgcnt messages?

[Biju Krishnan]

Hi Par,

Will these messages flash if theres a major I/O failure in the SAN path. We use VxVM 4.0 with FlashSnap enabled on the volumes.

There was one case when the VxVM seemed to dump similiar messages and
the SUN SF6900 then panicked, when we ran the SUN explorer. The
explorer was runf to try and gather stats during a scenario where WIO
on the system was arnd 60.

I will try and get the error messages from office if I can.
On 8/17/06, Par Botes [EMAIL PROTECTED] wrote:
I didn't know the answer to this so I asked someone knowledgeable (okay,I got an answer from two people).They gave me a great answer and I've copied and pasted it in here foryour information.Also for your information the fix was done in VxFS 
3.5MP3-RP2 and alllater releases and patches.But for those interested, here is the reason for why these messages aredisplayed (also, these messages are benign and are not an indication ofproblems with the filesystem).
Here it goes:Before solaris reboots it unmounts all filesystems. At that point alluser processes are killed so in theory there should be no open files andunmount should succeed. But in some cases there can be certain extended
operations pending for a filesystem (such as a checkpoint removal) andthey are handled by kernel threads. These extended operations can causethe umount to fail (although forced umount would succeed). Solaris
ignores the errors from umount and continues the reboot process.Eventually the fs will get i/o errors and you will see messages on theconsole about fs failures. These are benign since no access to theunderlying storage is allowed anymore at this 
point.On reboot vxfs willjust replay the log and the fs is fine. This was fixed in a patch toVxFS 3.5 by disabling the FS on umount if an unmount is issued from areboot.-Par-Original Message-
From: [EMAIL PROTECTED][mailto:[EMAIL PROTECTED]
] On Behalf Of IlyaVoroninSent: Wednesday, August 16, 2006 12:16 PMTo: Tony T.Cc: vxlistSubject: Re: [Veritas-vx] What are all these msgcnt messages?Install latest VxFS maintenance pack.
On 8/16/06, Tony T. [EMAIL PROTECTED] wrote: On 8/16/06, Ilya Voronin [EMAIL PROTECTED]
 wrote:  See http://seer.entsupport.symantec.com/docs/268523.htm That is very interesting and looks like I need that patch.
 Now that big question is, how on earth do I get it?!I followed every link I could find in that tech note but nowhere does it give any indication on just how I can download that patch.Even searching for
 Rolling Patch 2 only brings up links to articles without providing anyway of getting the patch itself. So where do I get this patch?--
Ilya Voronin [EMAIL PROTECTED]http://ivoronin.blogspot.com___Veritas-vx maillist-
Veritas-vx@mailman.eng.auburn.eduhttp://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
___Veritas-vx maillist-Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx-- Regards,PP BIJU KRISHNAN-
B.E/SCSA/BCSD
Navi Mumbai,India
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] To remove a disk that is failing [ ERRORs: V-5-2-440, V-5-1-10127 ] ...

[Biju Krishnan]

Hi Sanjay,

Although not so expereinced, would like to suggest that the rootvol is not
mirrored.

If ur ok with remirroring, then ensure that all your volumes in the rootdg
are mirrored.

vxassist -g rootdg remove mirror rootvol
vxassist -g rootdg remove mirror swapvol
vxassist -g rootdg remove mirror rootdisk3vol

e.t.c.

Then remove the rootdisk from the dg

vxdg -g rootdg rmdisk rootdisk

Add another disk or if u have a spare local disk, add it to rootdg and
mirror the disks.

Meanwhile if the count of errors {hard/soft} have stopped increasing, try
setting the failing flag off.
I dont remember the syntax, but just check man for vxedit -o set failing=off
daname

Regards,
PP BIJU KRISHNAN

On 3/5/07, Sanjay Gowda [EMAIL PROTECTED] wrote:


 Hi,

This should be an easy one for experience VxVM admins out there.

I have a root disk that is failing.  However when I run vxdiskadm option 4
(Remove a disk for replacement) and I choose rootdisk (the failing disk) for
removal, I am getting the following error:

 Select an operation to perform: 4

Remove a disk for replacement
Menu: VolumeManager/Disk/RemoveForReplace
  Use this menu operation to remove a physical disk from a disk
  group, while retaining the disk name.  This changes the state
  for the disk name to a removed disk.  If there are any
  initialized disks that are not part of a disk group, you will be
  given the option of using one of these disks as a replacement.

Enter disk name [disk,list,q,?] rootdisk
  VxVM  ERROR V-5-2-440 Unexpected error: VxVM vxckdiskrm ERROR
V-5-1-10127 disassociating disk-media rootdisk:
Record is associated

Select a different disk? [y,n,q,?] (default: n) n
And here is the disk info:

# vxprint -htg rootdg
DG NAME NCONFIG  NLOG MINORS   GROUP-ID
ST NAME STATEDM_CNT   SPARE_CNT APPVOL_CNT
DM NAME DEVICE   TYPE PRIVLEN  PUBLEN   STATE
RV NAME RLINK_CNTKSTATE   STATEPRIMARY  DATAVOLS  SRL
RL NAME RVG  KSTATE   STATEREM_HOST REM_DGREM_RLNK
CO NAME CACHEVOL KSTATE   STATE
VT NAME NVOLUME  KSTATE   STATE
V  NAME RVG/VSET/CO  KSTATE   STATELENGTH   READPOL   PREFPLEX
UTYPE
PL NAME VOLUME   KSTATE   STATELENGTH   LAYOUTNCOL/WID
MODE
SD NAME PLEX DISK DISKOFFS LENGTH   [COL/]OFF DEVICE
MODE
SV NAME PLEX VOLNAME  NVOLLAYR LENGTH   [COL/]OFF AM/NM
MODE
SC NAME PLEX CACHEDISKOFFS LENGTH   [COL/]OFF DEVICE
MODE
DC NAME PARENTVOLLOGVOL
SP NAME SNAPVOL  DCO
dg rootdg   default  default  980001147876797.6.ustlltb001

dm rootdisk c0t0d0s2 auto 20351143328960 FAILING
dm rootmirr c0t1d0s2 auto 20351143328960 -

v  rootdisk3vol -ENABLED  ACTIVE   40704ROUND -
gen
pl rootdisk3vol-01 rootdisk3vol ENABLED ACTIVE 40704CONCAT-
RW
sd rootdisk-03  rootdisk3vol-01 rootdisk 143288256 40704 0c0t0d0
ENA

v  rootvol  -ENABLED  ACTIVE   109748160 ROUND-
root
pl rootvol-01   rootvol  ENABLED  ACTIVE   109748160 CONCAT   -
RW
sd rootdisk-02  rootvol-01   rootdisk 33540096 109748160 0c0t0d0
ENA

v  swapvol  -ENABLED  ACTIVE   33540096 ROUND -
swap
pl swapvol-01   swapvol  ENABLED  ACTIVE   33540096 CONCAT-
RW
sd rootdisk-01  swapvol-01   rootdisk 033540096 0 c0t0d0
ENA
pl swapvol-02   swapvol  ENABLED  ACTIVE   33540096 CONCAT-
RW
sd rootmirr-01  swapvol-02   rootmirr 033540096 0 c0t1d0
ENA
Would appreciate if somebody has any idea on how I should proceed to
replace this disk.  BTW, I am running VxVM 4.1.

Thanks.

- SG

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx


___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] dmp + driver

[Biju Krishnan]

Hi Darren,

Jarkko seems to have the same HBA's for both tape access and LUN access. He
says that the support informed him about disabling the HBA with tape before
configuring the DMP. Hence he's worried of trying to configure backup
software and test backups on the production server.

In my environment we use different ports for tapes as well storage
connectivity, and hence not in a position to be 100% sure while replying.

I too feel that DMP should not affect the backups since it applies to
devices type=disk only.

Regards,
PP BIJU KRISHNAN

On 3/20/07, Darren Dunham [EMAIL PROTECTED] wrote:


 Sorry to bother you with the same issue again but nobody (Veritas, HP, =
 QLogic, sunmanagers, veritas-vx) has been able to confirm with me how to
=
 deal with the backups.

 Is there anyone out there who has installed Veritas Volume Manager  DMP
=
 and a HP tape library on the same (Solaris 8) server? Any help / ideas =
 would be appreciated.

I don't remember if it was an HP library, but I've definitely had
VxVM/DMP and tape systems on the same server.

VxVM and DMP don't deal with tapes.  Just ignore those products and
configure the drives directly.

The st.conf should be interacting with your FC drivers to produce tape
nodes (/dev/rmt/Xxxx), which are used by the backup product.

 Well... in that case DMP uses the driver binary directly but I haven't =
 even configured the HBA driver (wwn, device path etc) at all.

Usually you have to configure the HBA driver first.  At least so that
LUNs can be seen.  When they are seen by the OS, then VxVM/DMP can take
over.

 What I'm about to do is to configure the HBA driver for some other =
 multipathing software as well which means that another program (like =
 SAN4.4.x / mpxio) will be accessing the driver  the adapter. However =
 before doing that I thought I'd first ask you whether this hack will =
 break anything. Has anyone done this kind of setup before?

I guess that would depend on what kinf of reconfiguration you're wanting
to do.  Do you have specifics?

--
Darren Dunham   [EMAIL PROTECTED]
Senior Technical Consultant TAOShttp://www.taos.com/
Got some Dr Pepper?   San Francisco, CA bay area
  This line left intentionally blank to confuse you. 
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx





--
Regards,
PP BIJU KRISHNAN
-
B.E/SCSA/BCSD   Navi Mumbai,India
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] recovering lost vxvm private data from vxprint -hvt and vxprint -htg outputs

[Biju Krishnan]

Hi Arjun,

Is there any reason why you cannot encapsulate the root disk one more time??
What caused the problem??

Essentially the reason you need to encapsulate the root disk is to mirror
it. Re-encapsulate, reboot and mirror should work.

The technote for recovering DG's is

http://entkb.symantec.com/security/output/a180321.html

But your is a rootdg, I have never recovered a rootdg using the procedure.

Regards,
PP BIJU KRISHNAN

On 5/17/07, Arjun koneru [EMAIL PROTECTED] wrote:


Hi folks -- I lost my vxvm(3.5)  metadata  on my encapsulated root disk
and hence have booted the system(Solaris 9) without vxvm loaded and the
Filesystems in OS slices as opossed to VxVM objects.(by making appropriate
changes to /etc/system and /etc/vfstab)


Is there any way I can retrieve the lost private data from the saved
outputs(prioir to the disaster struck) of vxprint -htg rootdg ?

Thanks for any hint/help you may offer!

Arjun

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx





--
Regards,
PP BIJU KRISHNAN
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] T2000 Box with Solaris 10 Veritas 4.1(Encapsulation issue)

[Biju Krishnan]

Hi Gowtham,

This seems to be a common issue.

Refer the following technote

http://seer.support.veritas.com/docs/282808.htm

The bottomline is MP1 patch or the workaround mentioned in the doc.

Regards,
PP BIJU KRISHNAN


On 8/17/07, Gowthaman N [EMAIL PROTECTED] wrote:

 Hi,

 I m doing encapusulation on a T2000 server with Veritas 4.1 and during the
 second reboot of the server, it goes to
 maintenance mode

 Below is the error message from console.  Any solutions

 Hostname: 

 WARNING:
 /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL 
 PROTECTED],2/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],

 1 (ssd10):

 offline

 WARNING:
 /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL 
 PROTECTED],2/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],

 2 (ssd9):

 offline

 WARNING:
 /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL 
 PROTECTED],2/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],

 0 (ssd11):

 offline

 WARNING:
 /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL 
 PROTECTED],2/SUNW,[EMAIL PROTECTED],1/[EMAIL PROTECTED],0/[EMAIL PROTECTED]

 3,1 (ssd4):

 offline

 WARNING:
 /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL 
 PROTECTED],2/SUNW,[EMAIL PROTECTED],1/[EMAIL PROTECTED],0/[EMAIL PROTECTED]

 3,2 (ssd3):

 offline

 WARNING:
 /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL 
 PROTECTED],2/SUNW,[EMAIL PROTECTED],1/[EMAIL PROTECTED],0/[EMAIL PROTECTED]

 3,0 (ssd5):

 offline

 NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk

 ERROR: svc:/system/filesystem/usr:default failed to mount / (see 'svcs -x'
 for

 details)

 Aug 16 10:40:46 svc.startd[7]: svc:/system/filesystem/usr:default: Method
 /lib/

 svc/method/fs-usr failed with exit status 95.

 Aug 16 10:40:46 svc.startd[7]: system/filesystem/usr:default failed
 fatally: tra

 nsitioned to maintenance (see 'svcs -xv' for details)

 Requesting System Maintenance Mode

 (See /lib/svc/share/README for more information.)

 Console login service(s) cannot run

 Root password for system maintenance (control-d to bypass):

 single-user privilege assigned to /dev/console.

 Entering System Maintenance Mode





 Thanks  Regards,

 N. Gowthaman

 ___
 Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
 http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx


___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] dg backup on VXVM3.5 connected to solaris 9 , h\w-SunFire V240

[Biju Krishnan]

Hi Reshma,

You can backup disk group information in the earlier versions by using the
vxprint commands

http://seer.support.veritas.com/docs/180321.htm

For example, (if it is VxVM 3.x):

*# vxdisk list  vxdisk_list
# vxdisk -q list | awk '{print $1}' | xargs vxdisk list  vxdisk_list_detail
# vxdisk -q list | awk '{if ($2 != simple) print /dev/rdsk/$1}' | xargs
prtvtoc  prtvtoc_all_disk
# vxprint -g datadg -rhmvps  vxprint_datadg_config*

Read through the entire technote..!
Regards,
PP BIJU KRISHNAN



On 8/24/07, Reshma Syed [EMAIL PROTECTED] wrote:

 Hi ,

 How to take backup for dg backup on VXVM3.5 connected to solaris 9 ,
 h\w-SunFire V240 .

 There is the backup facility on VXVM 4.0 as pasted the command
 # vxconfigbackup-l /anyDir  dgname


 But there is no supporting command itself for backup in VXVM 3.5 ..
 Can any one help me on this...


 Thanks  Regards,
 Reshma Syed



 ___
 Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
 http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx


___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Problem adding news disks on Veritas

[Biju Krishnan]

Hi Tiago,

Check this

[EMAIL PROTECTED] ~]# vxdisk list c2t0d7
Device:c2t0d7s2
devicetag: c2t0d7
type:  auto
*hostid:*

[EMAIL PROTECTED] ~]# vxdisk list c2t0d6
Device:c2t0d6s2
devicetag: c2t0d6
type:  auto
*hostid:oracle-04*

Just run a

vxdisksetup -i c2t0d7

Does it give any error. Do not force a setup.

Another problem with the DAM (HDS) you are using is that it does not give a
list of free luns. Please check if this LUN is already allocated.

Regards,
PP BIJU KRISHNAN

On 10/23/07, Tiago Cruz [EMAIL PROTECTED] wrote:

 Hello guys,

 I'm newbie speaking around Storage/Veritas, and I have one problem like
 this:

 I'm running SunOS 5.8, directly connected at one Hitachi Thunderbird
 9200.

 I'm using HTC-9500V connector (Array Support Library) from package
 HTC-9500V_268512.tar.Z.

 I have 11 LUNs there created, you can see on pictures below:
 http://everlinux.com/9200/array_viewer.png
 http://everlinux.com/9200/lun_configuration.png

 I'm using VEA (Veritas Enterprise Administrator) version 3.2.525.0 for
 management, using VNC to get one graphical interface on Solaris.

 The problem is: I just can do the management of 6/11 disks that I have.
 The problem, I think, is with the 11º disk, how can I see here:
 http://everlinux.com/9200/disk7_path.png
 http://everlinux.com/9200/disk7_control.png

 Each disk have only one 'path' and only one 'control', but this guy
 called 'c2t0d7' have a lot of.

 [EMAIL PROTECTED] ~]# vxdisk list c2t0d6
 Device:c2t0d6s2
 devicetag: c2t0d6
 type:  auto
 hostid:oracle-04
 disk:  name=oracle07 id=1193072400.102.oracle-04
 group: name=oracle id=1193072401.104.oracle-04
 info:  format=cdsdisk,privoffset=256,pubslice=2,privslice=2
 flags: online ready private autoconfig autoimport imported
 pubpaths:  block=/dev/vx/dmp/c2t0d6s2 char=/dev/vx/rdmp/c2t0d6s2
 version:   3.1
 iosize:min=512 (bytes) max=256 (blocks)
 public:slice=2 offset=2304 len=102295296 disk_offset=0
 private:   slice=2 offset=256 len=2048 disk_offset=0
 update:time=1193074579 seqno=0.5
 ssb:   actual_seqno=0.0
 headers:   0 240
 configs:   count=1 len=1280
 logs:  count=1 len=192
 Defined regions:
 config   priv 48-000239[000192]: copy=01 offset=00 disabled
 config   priv 000256-001343[001088]: copy=01 offset=000192 disabled
 log  priv 001344-001535[000192]: copy=01 offset=00 disabled
 lockrgn  priv 001536-001679[000144]: part=00 offset=00
 Multipathing information:
 numpaths:   1
 c2t0d6s2state=enabled


 [EMAIL PROTECTED] ~]# vxdisk list c2t0d7
 Device:c2t0d7s2
 devicetag: c2t0d7
 type:  auto
 hostid:
 disk:  name= id= 1193076958.20.oracle-04
 group: name= id=1193077512.26.oracle-04
 info:  format=cdsdisk,privoffset=256,pubslice=2,privslice=2
 flags: online ready private autoconfig
 pubpaths:  block=/dev/vx/dmp/c2t0d7s2 char=/dev/vx/rdmp/c2t0d7s2
 version:   3.1
 iosize:min=512 (bytes) max=256 (blocks)
 public:slice=2 offset=2304 len=279741696 disk_offset=0
 private:   slice=2 offset=256 len=2048 disk_offset=0
 update:time=1193078658 seqno=0.12
 ssb:   actual_seqno=0.0
 headers:   0 240
 configs:   count=1 len=1280
 logs:  count=1 len=192
 Defined regions:
 config   priv 48-000239[000192]: copy=01 offset=00 enabled
 config   priv 000256-001343[001088]: copy=01 offset=000192 enabled
 log  priv 001344-001535[000192]: copy=01 offset=00 enabled
 lockrgn  priv 001536-001679[000144]: part=00 offset=00
 Multipathing information:
 numpaths:   5
 c2t0d11s2   state=disabled
 c2t0d10s2   state=enabled
 c2t0d8s2state=enabled
 c2t0d7s2state=disabled
 c2t0d9s2state=enabled

 How can I fix this?

 Thanks!
 --
 Tiago Cruz
 http://everlinux.com
 Linux User #282636


 ___
 Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
 http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] steps to configure raw devices in linux

[Biju Krishnan]

Its been long since I worked on VxVMbut if I understand the question
correctly then the solution is simple

vxdisksetup the new disks
use vxassist to create Disk Groups/Volume etc.

DO NOT RUN mkfs on the volume, just hand over the device name (/dev/vx/...)
to the DBA and he will use it for his data or log files.

Regards,
Biju


On 9/15/08, bharat rohera [EMAIL PROTECTED] wrote:

 Pls let me know setp of creation of raw device in VVM4.1 in linux

 Regards
 Bharat Rohera
 ___
 Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
 http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx




-- 
~~
Search for a cause
http://search.scgworld.org
~~~
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx