[Veritas-vx] How to setup 500gb as one file system in solaris 9
Hi All, I have solaris 9 server with Veritas file system.The server is having external EMC storage( DMX 300 ) with 500gb space. I want to have 500gb to be set up as one file system. Can you help me doing this. Thanking you, Milind M.Phanse __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
Re: [Veritas-vx] Vxvm issues with Aix disks
Hi, The disks are readable.Let me explain my setup... The luns are comming from a symmetrix. Whenever I add any of these disks into a Volume Group and run vxdctl enable I am able to see the disks in Vxvm and not otherwise. Is it an issue with AIX Mpio , veritas DMP and symmetrix? If yes is there any way to resolve it. Some googling tells ODM predifined needs to be added... could someone throw some light on this? Thanks, Ashish N Original Message Follows From: Pavel A Tsvetkov [EMAIL PROTECTED] To: ashish madhavan [EMAIL PROTECTED] CC: veritas-vx@mailman.eng.auburn.edu Subject: Re: Re: [Veritas-vx] Vxvm issues with Aix disks Date: Mon, 23 Apr 2007 10:45:58 +0400 Just try to read PVID from the disk itself (not from ODM database) to make sure the disk is readable lquerypv -h /dev/hdisk6 80 10 Check up the pathes to the disk lspath -l hdisk6 and remove all the bad ones if seen Make sure these disks are not special luns like Symmetrix gatekeepers and etc. Hi satish, Thanks for the quick reply. Below is the O/p of lsdev - # lsdev -C -c disk hdisk0 Available 06-08-01-5,0 Other SCSI Disk Drive hdisk1 Available 06-08-01-8,0 16 Bit LVD SCSI Disk Drive hdisk2 Available 07-08-01 MPIO Other FC SCSI Disk Drive hdisk3 Available 07-08-01 MPIO Other FC SCSI Disk Drive hdisk4 Available 07-08-01 MPIO Other FC SCSI Disk Drive hdisk5 Available 07-08-01 MPIO Other FC SCSI Disk Drive hdisk6 Available 07-08-01 MPIO Other FC SCSI Disk Drive VX sees hdisk1, hdisk5 and hidsk6 but not the other 4 disks. Thanks, Ashish From: Sathish Nayak [EMAIL PROTECTED] To: ashish madhavan [EMAIL PROTECTED],[EMAIL PROTECTED] eng.auburn.edu Subject: RE: [Veritas-vx] Vxvm issues with Aix disks Date: Fri, 20 Apr 2007 14:53:50 -0700 If you don't see the disk in vxdisk list, you cannot initialize it under vxvm. What does lsdev -Cc disk say? VxVM might be excluding these devices for some reason. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ashish madhavan Sent: Friday, April 20, 2007 1:55 PM To: veritas-vx@mailman.eng.auburn.edu Subject: [Veritas-vx] Vxvm issues with Aix disks Hi, I have installed Veritas Storage Foundation Basic 5 on one of my Aix boxes Aix 5.3) # oslevel -qr Known Recommended Maintenance Levels 5300-05 5300-04 5300-03 5300-02 5300-01 5300-00 I had downloaded the software from Symantec site. The install went fine and I created a defaultdf datadg. Now the problem is I am able to see only disks which are in LVM on vxdisk list and it does not show unused disks. Below are the details - # vxdg list NAME STATE ID # vxdg defaultdg datadg # lspv hdisk0 noneNone hdisk1 00cf4bbc3d443bb0rootvg active hdisk2 noneNone hdisk3 00cf4bbccd172174None hdisk4 nbs p;00cf4bbccd174184None hdisk5 00cf4bbccd175f7cvg002 active hdisk6 00cf4bbccd177573vg002 active # vxdisk list DEVICE TYPEDISK GROUPSTATUS hdisk1 auto:LVM--LVM hdisk5 auto:LVM--LVM hdisk6 auto:LVM--LVM i would like to add hdisk3 and hdisk4 to my datadg,but get the below error when i try to initialize - # vxdisk init hdisk3 VxVM vxdisk ERROR V-5-1-5433 Device hdisk3: init failed: Device path not valid Please help... Thanks, Ashish N _ Spice up your IM conversations. New, colorful and animated emoticons. Get chatting! http://server1.msn.co.in/SP05/emoticons/ ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx Spice up your IM conversations. New, colorful and animated emoticons. Get chatting! ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx _ Mega Airfare Sale. Click here Now. http://ss1.richmedia.in/recurl.asp?pid=18 ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
Re: [Veritas-vx] How to setup 500gb as one file system in solaris 9
milind phanse wrote: Hi All, I have solaris 9 server with Veritas file system.The server is having external EMC storage( DMX 300 ) with 500gb space. I want to have 500gb to be set up as one file system. Can you help me doing this. It's very easy, really. Create the Logical unit on the EMC (LUN), make sure your Solaris9 box can see it in 'format', (may require a reconfigure reboot, depending what stage you are at), create a volume using your new logical unit, and create a filesystem using the new volume. The last two steps look something like (but differ in details) vxassist -g emcdg create volume newvol 500g /usr/lib/fs/vxfs/mkfs -F vxfs -o largefiles /dev/vx/rdsk/emcdg/newvol (or you can use the web GUI) ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
Re: [Veritas-vx] fsadm: reorg ioctl returned errno 61441
Searching on 61441 and fsadm yields pretty much only hits on this Veritas bug on HP-UX: PHKL_22121: ( SR: 8606135462 CR: JAGad04596 ) VxFS 3.3 write(2) may return incorrect error value 61441 to applications on error. As it says, this is not a real error return code value. Cheers, - Mike Myers, mike.myers at nwdc.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leon Koll Sent: Sunday, April 22, 2007 8:05 AM To: veritas-vx@mailman.eng.auburn.edu Subject: [Veritas-vx] fsadm: reorg ioctl returned errno 61441 Hello, what does errno 61441 mean ? I am getting it during the fsadm reorg run : # fsadm -v -e -d -p 2 /myfs UX:vxfs fsadm: INFO: V-3-20287: using device /dev/rdsk/c2t001738010155000Cd0s0 UX:vxfs fsadm: INFO: V-3-20223: directory reorganization complete UX:vxfs fsadm: INFO: V-3-20261: extent reorg pass 1 choosing exclusion zones for AUs: aun 3758 tfree 24637 sfree 5 fset 999 scanning ino0 fset 999 scanning ino 10 ... fset 999 scanning ino 140 fset 999 scanning ino 150 UX:vxfs fsadm: ERROR: V-3-24364: reorg failed for fset 999 ino 1536248 UX:vxfs fsadm: ERROR: V-3-20274: reorg ioctl returned errno 61441 UX:vxfs fsadm: ERROR: V-3-24364: reorg failed for fset 999 ino 1571979 UX:vxfs fsadm: ERROR: V-3-20274: reorg ioctl returned errno 61441 fset 999 scanning ino 160 fset 999 scanning ino 170 UX:vxfs fsadm: ERROR: V-3-24364: reorg failed for fset 999 ino 1721286 UX:vxfs fsadm: ERROR: V-3-20274: reorg ioctl returned errno 61441 fset 999 scanning ino 180 fset 999 scanning ino 190 ... Thanks, -- Leon ___ 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
[Veritas-vx] Weritas 4.1 uninstall problems
Having problems getting a clean uninstall of Veritas 4.1 on Solaris 10. We have 3 V440 Sun boxes, each running Solaris 10, and each running (I thought at least) identical versions of Veritas vxvm/vxfs 4.1. I went to uninstall 4.1 on these machines. 2 completed fine, rebooted, no veritas to be found. On the third machine I still get some vx processes ( like vxesd ) starting up and kernel messages. pkginfo shows no packages with VRTS or vx in the name related to Veritas. running vxddladm stop eventsource shuts everything down, but I'm still concerned that I can't get the software unistalled properly. Has anyone run into this, or know of a good way to fix this? Heck I'd even settle for someone telling me how programs from an unistalled package can still run on boot... Jeff -- Jeffrey Collyer ITC/CMS Admin University of Virginia ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
Re: [Veritas-vx] removing devices
what kind of output do you get with? # cfgadm -o show_FCP_dev -al -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jarkko Airaksinen Sent: Thursday, April 12, 2007 4:12 AM To: Veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] removing devices 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 there's not much action in the server I've tried disabling all paths for the other of the two adapters with cfgadm but the paths stay regardless. Long time ago means a few months ago but during this uptime. -j- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Dunham Sent: miércoles, 11 de abril de 2007 20:03 To: Veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] removing devices I suppose this is because the device paths don't get cleaned even with devfsadm -C. Close. 'devfsadm -C' removes device files if the *device* is gone. However in your case the device is still present (but no longer connected to storage). How a device is handled depends on your storage driver(s). Some can handle removal without a reboot, some can't. Best would be if you could go in with cfgadm and disable the storage. However the devices definitely don't exist anymore. I've deleted the disk from the SAN long time ago. I think the Solaris device does still exist in the kernel and storage driver. Does long time ago mean before or after the last reboot? How would you remove the dangling device entries (without rebooting) if devfsadm -C doesn't clear them? The server has Sol8 + VxVM5.0. You have to ask the device driver to do it, and there's no global way of asking. 'cfgadm disable ...' would be the usual way for a recent Sun-supplied san driver. -- 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 __ La información incluida en el presente correo electrónico es CONFIDENCIAL, siendo para el uso exclusivo del/os destinatario/s arriba mencionado/s. Si usted recibe y lee este correo electrónico y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida cualquier divulgación, distribución, uso o reproducción del mismo, y le rogamos que nos lo notifique inmediatamente respondiendo al mensaje original a la dirección arriba mencionada y eliminando el mensaje a continuación. The information contained in this e-mail is CONFIDENTIAL and is intended only for the use of the addressee named above.If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, or you have received this communication in error, please be aware that any diffusion, distribution or duplication of this communication is strictly forbidden, and please notify us immediately by return to the original message at the address above eliminating it afterwards. ___ 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
