Hello,
I have an eva qlogic23xx hbas as well.
In (quite) a few cases, after unpresenting removing a disk I've had to use
luxadm to remove the c#t#d#s2 device paths in os level so that the rest can be
cleared with devfsadm -C. Here's a clip from some document I got from another
sol vvm
restarting it, and another vxdctl
enable.
Any ideas how to proceed? Rebooting (if it would even help) is the last option
as this is a live server.
Thanks,
Jarkko Airaksinen
-Original Message-
From: veritas-vx-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@mailman.eng.auburn.edu
the EVA as A/P (alua?)
instead of A/A.
How could I make vxdmp understand that the array is an A/A array?
Thanks,
Jarkko Airaksinen
___
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
Hello,
I'm moving stuff from a subdisk to another with vxassist move. I had
to abort the move once because it seemed that rman + vxassist move
killed our san box.
Now the target subdisk is 89% full, so I get this.
# vxassist -g cd_backup01_tbsdg move BACKUP01_TBS \!cd_backup01_tbsdg01
Hello,
I'm running SF 5.0 on two identical servers. Last week in the other
server the VEA somehow stopped working. I can connect to the servers
with the VEA client but on the other server there are no subelements at
all (no actionagent, storageagent, vailagent).
The processes running on
Hello,
I've never needed to reboot my SunOS server 5.8 Generic_117350-44 sun4us sparc
FJSV,GPUZC-M with VxVM 5.0, VxDMP VxFS when adding new (SAN) disks.
If for some reason the new disks don't show in 'vxdisk list' after presenting
them to the server, all I need to do is 'vxdisk scandisks'
. Karr [mailto:[EMAIL PROTECTED]
Sent: jueves, 09 de agosto de 2007 22:42
To: James Slater
Cc: Cronin, John S; Jarkko Airaksinen; Veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] one slice failing
Failing is set when VxVM gets an unrecoverable I/O error from DMP.
If the I/O error
Hello,
The only thing that wasn't automatic in my case was the recognition of the type
of the array, i.e. A-A, A/A-A-HP, A-P etc. In my case (A-A array) I had to
manually enable all paths to the luns. I did it when I changed the multipathing
scheme to adaptive with the 'use_all_paths=yes'
Hello,
After a short connection loss at the SAN I got some write errors and
this:
dg cd_data01dg default default 11175087864.68.mdr-cadmium
dm cd_data01dg01 c3t50001FE15005E90Dd9s2 auto 65536 629047040 NOHOTUSE
dm cd_data01dg02 c3t50001FE15005E90Cd8s2 auto 65536
Hello,
There's something odd going on with one of the 8 paths I use for my FC
disks. It's all the time 100% busy and has huge avg service times.
Here's an output of vsar:
Disk %busy %avg avque await aserv nrd avg nwr avg rd(k)
wr(k)
c5t50001 100.00 100.001.10.0
Hello all Gurus out there,
Is there any way to add specific options when remounting a mounted file
system? Looks like I can remove them but not add.
For example I mount a file system with convosync=direct:
# mount -F vxfs -o convosync=direct /dev/vx/dsk/cd_testdg01/cd_testvol01
Brilliant!
Thank you, Sir!
-jarkko-
-Original Message-
From: Myers, Mike [mailto:[EMAIL PROTECTED]
Sent: miércoles, 25 de abril de 2007 18:06
To: Jarkko Airaksinen; Veritas-vx@mailman.eng.auburn.edu
Subject: RE: [Veritas-vx] remount add parameters
Try it this way:
mount -F
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: lunes, 23 de abril de 2007 23:22
To: Jarkko Airaksinen; Veritas-vx@mailman.eng.auburn.edu
Subject: RE: [Veritas-vx] removing devices
what kind of output do you get with?
# cfgadm -o show_FCP_dev -al
-Original Message-
From
: Re: [Veritas-vx] resizing a device
Jarkko Airaksinen wrote:
Hello,
I see your point. Which is faster, transferring the data between two
separate file systems (i.e. over FC, ~210MB/s), or moving stuff within
the same disk group? I'd imagine that moving data from a LUN to
another
will require
but then this license thing stopped me from moving volumes between
disk groups.
So, not doable (unless I pay for some extra license).
-j-
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jarkko
Airaksinen
Sent: viernes, 13 de abril de 2007 10:26
To: Doug
. However at times
only some (or none) of the paths disappear when I remove the disk.
I'll play with the driver a bit and see if I can disable them manually.
-j-
-Original Message-
From: Myers, Mike [mailto:[EMAIL PROTECTED]
Sent: miércoles, 11 de abril de 2007 18:56
To: Jarkko Airaksinen
Yes, in a way it's present as I don't disconnect the whole SAN :). I just do
the normal device removal process (umount fs, remove volume from the disk group
etc) and finally unpresent it from the SAN.
What makes this odd is that sometimes the removal works just fine.
On a slow day when
Summary!
In case someone else is fighting with the same problems I thought I'd
share my conclusion with you.
I've decided not to resize the LUNS / file systems at all as Solaris 8
is quite restrictive with LUN resizing. I've overcome the need for
resizing them with a bit of thinking.
Given the
the no user impact sounds quite tempting.
-j-
-Original Message-
From: Doug Hughes [mailto:[EMAIL PROTECTED]
Sent: jueves, 12 de abril de 2007 14:49
To: Jarkko Airaksinen
Cc: [EMAIL PROTECTED]
Subject: Re: [Veritas-vx] resizing a device
Jarkko Airaksinen wrote:
Summary!
In case someone else
a device
Jarkko Airaksinen wrote:
Hello,
I see your point. Which is faster, transferring the data between two
separate file systems (i.e. over FC, ~210MB/s), or moving stuff within
the same disk group? I'd imagine that moving data from a LUN to
another
will require the same I/O regardless
Hello,
I've removed some disks from the server but they keep on coming back for
example after vxdisk scandisks':
# vxdisk list
DEVICE TYPEDISK GROUPSTATUS
EVA8_1 auto:cdsdiskpt_dwhdg146_01 pt_dwhdg146 online
nohotuse
EVA8_3
This was meant for the whole world to see (and maybe learn something
from it :)).
-Original Message-
From: Jarkko Airaksinen
Sent: jueves, 29 de marzo de 2007 18:29
To: 'Darren Dunham'
Subject: RE: [Veritas-vx] resizing a device
Yeah but that's already a bit tedious. Also every time you
Hello,
One volume failed in a disk group just a moment ago. On hardware level
everything seems quite; all the paths are ok, the SAN disk is online well and
so on. No logs show a hardware failure.
However now i see this:
# vxdisk list
DEVICE TYPEDISK GROUP
(Solaris 8) server? Any help / ideas would be
appreciated.
Br,
Jarkko Airaksinen
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jarkko Airaksinen
Sent: lunes, 12 de marzo de 2007 19:02
To: veritas-vx@mailman.eng.auburn.edu
Subject: Re
Hello,
As we all know the Veritas DMP can handle almost all FC SANs without
using the HBA driver from the HBA provider.
However our tape drive doesn't work that way. I need to install the HBA
driver to be able to find the tape drives and then take backups through
the FC. The adapter is a
conflicts?
Thanks,
Jarkko Airaksinen
___
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
and scanning disks again
but the datype persists. Then I took the disk completely from the
server's view from EVA, removed it from vvm and redid everything but the
datype still is XP10k..
Would you have any idea why this happens and how to fix it?
Thank you,
Jarkko Airaksinen
27 matches
Mail list logo
