Re: [Networker] Novell abends

Hi Simon,

I know of a problem with SNAPSHOT.NLM on multiprocessor machines which may be 
causing abends. Are all machines on which you have problems multi-CPU? Does the 
backup run correctly on single-CPU systems?

What you can try in any case is unloading SNAPSHOT.NLM and retrying the backup 
like that.

Hope this helps,
Tom.

_______________________________________

Tom Willems - Consultant - Professional Services

Fujitsu Siemens Computers 
20, rue des Peupliers - L-2328 LUXEMBOURG-HAMM 
Phone: +352-26099-891 - Fax: +352-26099-895 
<mailto:tom.willems AT fujitsu-siemens DOT com> 

This message may contain confidential and/or privileged information. If you are 
not the addressee or authorized to receive this for the addressee, you must not 
use, copy, disclose or take any action based on this message or any information 
herein.  If you have received this message in error, please advise the sender 
immediately by reply e-mail and delete this message.

Thank you for your cooperation. 


-----Original Message-----
From: Simon Phillips [mailto:sdph AT DML.AC DOT UK]
Sent: jeudi 1 août 2002 16:04
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Novell abends


Hi,

I'm running Networker 4.2.1 client on Novell, backing up to a Sun with 
Networker 6.1.1. 

Several servers abend, all with the following messages 


Console Log:


SNAPSHOT.NLM:*Trying to mount volume !MAIL at 4:50:26 7/28/2002.
SRV1 <1>:
SRV1 <1>:mount !MAIL
Mounting Volume !MAIL
**  Reading In FAT
**  Verifying Directory FAT Chain
**  Scanning the Directory
**  Checking Subdirectories
**  Scanning Files with Trustee Nodes
**  Scanning Deleted Files
**  Linking the Name Spaces
**  Shrinking the Extended Directory
Problem with file 0728POA.001, length extended.
Problem with file 0728POA.001,  old length = 0, new length = 65536
Problem with file 0728POA.001, length extended.
Problem with file 0728POA.001,  old length = 0, new length = 65536
Problem with file POOL0003.DAT, length extended.
Problem with file POOL0003.DAT,  old length = 0, new length = 13107200
Problem with file POOL0002.DAT, length extended.
Problem with file POOL0002.DAT,  old length = 0, new length = 131072
Problem with file POOL0001.DAT, length extended.
Problem with file POOL0001.DAT,  old length = 0, new length = 2097152
Problem with file POOL0000.DAT, length extended.
Problem with file POOL0000.DAT,  old length = 0, new length = 131072

SNAPSHOT.NLM: Volume !MAIL mounted at 4:51:29 7/28/2002.


SRV1 <1>:
SRV1 <1>:dismount !MAIL
SNAPSHOT.NLM: Volume !MAIL dismounted at 5:49:49 7/28/2002.
Dismounting volume !MAIL
Volume !MAIL has been dismounted.

SNAPSHOT.NLM: Deleting snapshot virtual device for !MAIL...

28-07-2002   5:50:19 am:    NWPA-3.6-0
     NWPA-004:  The CDM driver deactivated device [V5E0-A2-D0:0] Snapshot of #
     0 IBM RAID rev:1 due to a device failure.


28-07-2002   5:50:19 am:    SERVER-5.0-1534  [nmID=B0013]
     Device "[V5E0-A2-D0:0] Snapshot of # 0 IBM RAID rev:1" deactivated by
     driver due to device failure.

SNAPSHOT.NLM: FINISHED deleting snapshot virtual device.


_ _ _ _ _ _ _


SNAPSHOT.NLM:*Trying to mount volume !SHARED at 9:13:23 8/01/2002.
SRV1:
SRV1:mount !SHARED
Mounting Volume !SHARED
**  Reading In FAT
**  Verifying Directory FAT Chain
**  Validating the Extended Directory
**  Scanning the Directory
**  Checking Subdirectories
**  Scanning Files with Trustee Nodes
**  Scanning Deleted Files
**  Linking the Name Spaces
**  Shrinking the Extended Directory
Number of unclaimed FAT blocks that were freed 148
Problem with file ALLSTU.LDB, length extended.
Problem with file ALLSTU.LDB,  old length = 0, new length = 65536
Problem with file ~$02_F~1.DOC, length extended.
Problem with file ~$02_F~1.DOC,  old length = 0, new length = 65536
Problem with file INDUCT~1.LDB, length extended.
Problem with file INDUCT~1.LDB,  old length = 0, new length = 65536

SNAPSHOT.NLM: Volume !SHARED mounted at 9:14:28 8/01/2002.
The running process will be suspended.

 1-08-2002   9:14:29 am:    SERVER-5.0-4631  [nmID=1001C]
     WARNING! Server SRV1 experienced a critical error.  The offending
     process was suspended or recovered.  However, services hosted by this
     server may have been affected.



Abend Log

Additional Information:
    The CPU encountered a problem executing code in SERVER.NLM.  The problem 
may be in that module or in data passed to that module by a process owned by 
SNAPSHOT.NLM.

____________________________

Has anybody seen this kind of fault before? If so, is there a solution??

Will summarise.





Simon Philllips

System Administrator/DBA
UHI Millennium Institute
Dunstaffnage Marine Laboratory
Dunbeg, Oban, Argyll
PA37 1QA

Tel: +44 (0) 1631 559286
Mobile: 07885-663308
Fax: 01631 559001
Email: s.phillips AT dml.ac DOT uk
http://www.uhi.ac.uk

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=