Take volume offline.
update system with lastest cluster patch Jan 27th 2007 , I believe
upgrade veritas volume manager with 3.5 and leave it file system with 3.5
upgrade volume Manager and file system with 4.1MP1 and bring all the volume
online.
3.1 you can not upgrade directly with 4.0 or 4.1. I have done 4.1MP1 around 500
systems.
3.5 will be end of life soon.
Good luck
> From: [EMAIL PROTECTED]> Subject: Veritas-vx Digest, Vol 10, Issue 20> To:
> veritas-vx@mailman.eng.auburn.edu> Date: Wed, 28 Feb 2007 05:27:10 -0600> >
> Send Veritas-vx mailing list submissions to>
> veritas-vx@mailman.eng.auburn.edu> > To subscribe or unsubscribe via the
> World Wide Web, visit>
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx> or, via email,
> send a message with subject or body 'help' to> [EMAIL PROTECTED]> > You can
> reach the person managing the list at> [EMAIL PROTECTED]> > When replying,
> please edit your Subject line so it is more specific> than "Re: Contents of
> Veritas-vx digest..."> > > Today's Topics:> > 1. Veritas and Sun DST patches
> (Ray Ramachandran)> 2. fdatasync makes process 100% cpu (Tharindu Rukshan
> Bamunuarachchi)> 3. Re: [Veritas-ha] fdatasync makes process 100% cpu>
> (Tharindu Rukshan Bamunuarachchi)> 4. Re: [Veritas-ha] fdatasync makes
> process 100% cpu> (Tharindu Rukshan Bamunuarachchi)> 5. shared disk group
> (Asiye Yi?it)> > >
> ----------------------------------------------------------------------> >
> Message: 1> Date: Tue, 27 Feb 2007 16:47:07 -0500> From: "Ray Ramachandran"
> <[EMAIL PROTECTED]>> Subject: [Veritas-vx] Veritas and Sun DST patches> To:
> <veritas-vx@mailman.eng.auburn.edu>> Message-ID:> <[EMAIL PROTECTED]>>
> Content-Type: text/plain; charset="us-ascii"> > Hello,> > > We are trying to
> upgrade a 880 sun server with 10/01 Sol 8 release> version and Veritas Volume
> manger 3.1 and Volume File system 3.5. Can> someone help us with the best
> method to go about upgrading to the latest> kernel version of solaris 8 and
> to the latest veritas volume manger?> > > > Thank you,> Ray>
> __________________________________________________________> > L'information
> apparaissant dans ce message electronique et dans les documents qui y sont
> joints est de nature confidentielle ou privilegiee. Si ce message vous est
> parvenu par erreur et que vous n'en etes pas le destinataire vise, vous etes
> par les presentes avise que toute utilisation, copie ou distribution de ce
> message est strictement interdite. Vous etes donc prie d'en informer
> immediatement l'expediteur et de detruire ce message, ainsi que les documents
> qui y sont joints, le cas echeant.> > The information in this message,
> including in all attachments, is confidential or privileged. In the event you
> have received this message in error and are not the intended recipient, you
> are hereby advised that any use, copying or reproduction of this document is
> strictly forbidden. Please notify immediately the sender of this error and
> destroy this message, including its attachments, as the case may be.>
> __________________________________________________________> --------------
> next part --------------> An HTML attachment was scrubbed...> URL:
> http://mailman.eng.auburn.edu/pipermail/veritas-vx/attachments/20070227/d91b1fb7/attachment.html>
> > ------------------------------> > Message: 2> Date: Wed, 28 Feb 2007
> 11:05:24 +0530> From: "Tharindu Rukshan Bamunuarachchi" <[EMAIL PROTECTED]>>
> Subject: [Veritas-vx] fdatasync makes process 100% cpu> To:
> Veritas-ha@mailman.eng.auburn.edu> Cc: veritas-vx@mailman.eng.auburn.edu>
> Message-ID:> <[EMAIL PROTECTED]>> Content-Type: text/plain;
> charset="iso-8859-1"> > We are using Veritas SFCFS for Linux.> > When our
> program is trying to call fdatasync() to sync file core data with> disk,
> process cpu was increased to 100%.> > Any idea on behavior of fdatasync()
> when used with Veritas cfs.> > I hope Veritas behavior would be differ from
> typical Linux behavior.> > Pls help> > > Thankx> Tharindu> > > -- > Tharindu
> Rukshan Bamunuarachchi> all fabrications are subject to decay> --------------
> next part --------------> An HTML attachment was scrubbed...> URL:
> http://mailman.eng.auburn.edu/pipermail/veritas-vx/attachments/20070228/0a208ef5/attachment-0001.htm>
> > ------------------------------> > Message: 3> Date: Wed, 28 Feb 2007
> 11:36:37 +0530> From: "Tharindu Rukshan Bamunuarachchi" <[EMAIL PROTECTED]>>
> Subject: Re: [Veritas-vx] [Veritas-ha] fdatasync makes process 100%> cpu> To:
> "Bala Kumaresan" <[EMAIL PROTECTED]>> Cc: veritas-vx@mailman.eng.auburn.edu,>
> Veritas-ha@mailman.eng.auburn.edu> Message-ID:> <[EMAIL PROTECTED]>>
> Content-Type: text/plain; charset="iso-8859-1"> > VRTSvcs-4.1.00.10-GA_RHEL4>
> VRTSvxfs-common-4.1.00.10-GA_RHEL4> > > Apart from that I saw following
> errors on my dmesg out put, any connection> with this ....> > > SCSI error :
> <0 0 0 0> return code = 0x10000> end_request: I/O error, dev sda, sector
> 209905099> SCSI error : <0 0 0 0> return code = 0x10000> VxVM vxdmp V-5-0-112
> disabled path 8/0x0 belonging to the dmpnode 201/0x40> SCSI error : <1 0 1 0>
> return code = 0x10000> end_request: I/O error, dev sdm, sector 209780228>
> SCSI error : <1 0 1 0> return code = 0x10000> VxVM vxdmp V-5-0-112 disabled
> path 8/0xc0 belonging to the dmpnode 201/0x40> SCSI error : <1 0 1 0> return
> code = 0x10000> SCSI error : <0 0 0 0> return code = 0x10000> SCSI error : <1
> 0 1 0> return code = 0x10000> SCSI error : <0 0 0 0> return code = 0x10000>
> VxVM vxdmp V-5-0-148 enabled path 8/0xc0 belonging to the dmpnode 201/0x40>
> VxVM vxdmp V-5-0-148 enabled path 8/0x0 belonging to the dmpnode 201/0x40> >
> > > On 2/28/07, Bala Kumaresan <[EMAIL PROTECTED]> wrote:> >> > which release
> of SFCFS are you using ?> >> > Bala> >> > ------------------------------> >
> *From:* [EMAIL PROTECTED] [mailto:> > [EMAIL PROTECTED] *On Behalf Of
> *Tharindu Rukshan> > Bamunuarachchi> > *Sent:* Tuesday, February 27, 2007
> 9:35 PM> > *To:* Veritas-ha@mailman.eng.auburn.edu> > *Cc:*
> veritas-vx@mailman.eng.auburn.edu> > *Subject:* [Veritas-ha] fdatasync makes
> process 100% cpu> >> > We are using Veritas SFCFS for Linux.> >> > When our
> program is trying to call fdatasync() to sync file core data with> > disk,
> process cpu was increased to 100%.> >> > Any idea on behavior of fdatasync()
> when used with Veritas cfs.> >> > I hope Veritas behavior would be differ
> from typical Linux behavior.> >> > Pls help> >> >> > Thankx> > Tharindu> >>
> >> > --> > Tharindu Rukshan Bamunuarachchi> > all fabrications are subject to
> decay> >> > > > -- > Tharindu Rukshan Bamunuarachchi> all fabrications are
> subject to decay> -------------- next part --------------> An HTML attachment
> was scrubbed...> URL:
> http://mailman.eng.auburn.edu/pipermail/veritas-vx/attachments/20070228/d63b0136/attachment.html>
> > ------------------------------> > Message: 4> Date: Wed, 28 Feb 2007
> 11:38:20 +0530> From: "Tharindu Rukshan Bamunuarachchi" <[EMAIL PROTECTED]>>
> Subject: Re: [Veritas-vx] [Veritas-ha] fdatasync makes process 100%> cpu> To:
> "Bala Kumaresan" <[EMAIL PROTECTED]>> Cc: veritas-vx@mailman.eng.auburn.edu,>
> Veritas-ha@mailman.eng.auburn.edu> Message-ID:> <[EMAIL PROTECTED]>>
> Content-Type: text/plain; charset="iso-8859-1"> > One this more, Are there
> any Veritas log file can I look into ...?> > I have no good idea on what are
> the veritas logs should i Look into ??> > On 2/28/07, Tharindu Rukshan
> Bamunuarachchi <[EMAIL PROTECTED]> wrote:> >> > VRTSvcs-4.1.00.10-GA_RHEL4> >
> VRTSvxfs-common-4.1.00.10-GA_RHEL4> >> >> > Apart from that I saw following
> errors on my dmesg out put, any connection> > with this ....> >> >> > SCSI
> error : <0 0 0 0> return code = 0x10000> > end_request: I/O error, dev sda,
> sector 209905099> > SCSI error : <0 0 0 0> return code = 0x10000> > VxVM
> vxdmp V-5-0-112 disabled path 8/0x0 belonging to the dmpnode 201/0x40> > SCSI
> error : <1 0 1 0> return code = 0x10000> > end_request: I/O error, dev sdm,
> sector 209780228> > SCSI error : <1 0 1 0> return code = 0x10000> > VxVM
> vxdmp V-5-0-112 disabled path 8/0xc0 belonging to the dmpnode> > 201/0x40> >
> SCSI error : <1 0 1 0> return code = 0x10000> > SCSI error : <0 0 0 0> return
> code = 0x10000> > SCSI error : <1 0 1 0> return code = 0x10000> > SCSI error
> : <0 0 0 0> return code = 0x10000> > VxVM vxdmp V-5-0-148 enabled path 8/0xc0
> belonging to the dmpnode 201/0x40> >> > VxVM vxdmp V-5-0-148 enabled path
> 8/0x0 belonging to the dmpnode 201/0x40> >> >> >> > On 2/28/07, Bala
> Kumaresan < [EMAIL PROTECTED]> wrote:> > >> > > which release of SFCFS are
> you using ?> > >> > > Bala> > >> > > ------------------------------> > >
> *From:* [EMAIL PROTECTED] [mailto:> > > [EMAIL PROTECTED] *On Behalf Of
> *Tharindu> > > Rukshan Bamunuarachchi> > > *Sent:* Tuesday, February 27, 2007
> 9:35 PM> > > *To:* Veritas-ha@mailman.eng.auburn.edu> > > *Cc:*
> veritas-vx@mailman.eng.auburn.edu> > > *Subject:* [Veritas-ha] fdatasync
> makes process 100% cpu> > >> > > We are using Veritas SFCFS for Linux.> > >>
> > > When our program is trying to call fdatasync() to sync file core data> >
> > with disk, process cpu was increased to 100%.> > >> > > Any idea on
> behavior of fdatasync() when used with Veritas cfs.> > >> > > I hope Veritas
> behavior would be differ from typical Linux behavior.> > >> > > Pls help> >
> >> > >> > > Thankx> > > Tharindu> > >> > >> > > --> > > Tharindu Rukshan
> Bamunuarachchi> > > all fabrications are subject to decay> > >> >> >> >> >
> --> > Tharindu Rukshan Bamunuarachchi> > all fabrications are subject to
> decay> >> > > > -- > Tharindu Rukshan Bamunuarachchi> all fabrications are
> subject to decay> -------------- next part --------------> An HTML attachment
> was scrubbed...> URL:
> http://mailman.eng.auburn.edu/pipermail/veritas-vx/attachments/20070228/49623da4/attachment-0001.htm>
> > ------------------------------> > Message: 5> Date: Wed, 28 Feb 2007
> 13:27:03 +0200> From: Asiye Yi?it <[EMAIL PROTECTED]>> Subject: [Veritas-vx]
> shared disk group> To: <veritas-vx@mailman.eng.auburn.edu>> Message-ID:>
> <[EMAIL PROTECTED]>> Content-Type: text/plain; charset="iso-8859-9"> > Hi,> >
> Is there any way if we create the disk group as not shared to convert that
> disk group to shared? I know we can import that disk group as shared with -s
> flag. However, to automatically import that disk group as shared, which flag
> I need to enable?> > > > Regards,> > Asiye Yigit> > > > -------------- next
> part --------------> An HTML attachment was scrubbed...> URL:
> http://mailman.eng.auburn.edu/pipermail/veritas-vx/attachments/20070228/70b41371/attachment.html>
> > ------------------------------> >
> _______________________________________________> Veritas-vx maillist -
> Veritas-vx@mailman.eng.auburn.edu>
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx> > > End of
> Veritas-vx Digest, Vol 10, Issue 20>
> ******************************************
_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx
_______________________________________________
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
