Until Symantec can resolve the issue you might use the old SG driver. I had
to do this one time, many versions ago because it killed an E10k every time.
I have seen SG drivers not unload, it is usually because a MM process is
using it. If you stop NBU, it should unload. Good luck.
Regards,
Patrick Whelan
VERITAS Certified NetBackup Support Engineer for UNIX.
VERITAS Certified NetBackup Support Engineer for Windows.
netbackup AT whelan-consulting.co DOT uk
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of rhugga
Sent: Thursday, June 02, 2011 1:40 AM
To: VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Subject: [Veritas-bu] Anyone running 7.1 on Solaris 10 9/10 (u9) on sun4v
arch?
Just spent 12 hours trying to upgrade from 6.5.6 to 7.1. (working with
professional services). The upgrade appears to have gone smoothly. I can
browse images, emm looks clean, all the policies converted fine and are
browseable in the console, etc.... BUT we are having some strange issues
with the sg driver.
Config: Solaris 10 update 9 on a T5240 (sun4v). Quantum i500 18 LTO4 drives
(latest library and drive firmware). ProtecTIER VTL emulating 80 dlt drives.
Right from the jump I see the first problem.. After it appeared my devices
were fubar we started going thru the gamut of rebuilding the SG links. We go
to "rem_drv sg" (also tried modunload -i <instance>) and it claims sg is
busy and won't unload. I've been using netbackup since 3.x on solaris 2.x
thru 10 and have never seen the sg driver unable to unload. I even went as
far as completely rebuilding /dev/rmt as well.
So I have netbackup set to not auto-start on boot. After reboots --
sometimes the sg driver is loaded, sometimes its not. odd.
The core problem we had was a job would submit a mount request, the library
would mount the tape (verified), but the job never gets informed that the
mount is complete. (bptm is still waiting to here from ltid) Normally I
would suspect device mismatching/sg issues or library/communication issues
but not in this case.
robtest can mount and unmount tapes.
At this point we bumped up sg verbose logging to 9 and saw this gem during
boot:
Boot device: disk File and args:
SunOS Release 5.10 Version Generic_144488-08 64-bit Copyright (c) 1983,
2010, Oracle and/or its affiliates. All rights reserved.
Symantec SCSA Generic Revision: 3.7
WARNING: sg: _init failed on linkage 6
Wait, not weird enough yet? It doesn't do that on every reboot. Its
completely sporadic.
I looked at the sg driver file. File size matches what the backline engineer
shows on his system. The permissions were the same. Doesn't appear to be a
corrupt file or possibly the version from the 6.5.6 installation.
I just have a gut feeling this binary has issues with either update 9 or
sun4v. O was hoping to confirm if anyone is running 7.1 on update 9 on
sun4v.
At this point I've rolled back and abandoned this upgrade attempt. (oh how I
love ZFS)
+----------------------------------------------------------------------
|This was sent by chuck.carson AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
