Re: [Networker] More NW 7.3 oddness.

We saw similar messages in earlier versions of NetWorker (either v6.1.3
or v7.1.1, can't remember which) when the tape was empty or contained
VERY little data.  The explanation I got from Legato was that the block
size reported was the size of the initial header block rather than a
data block.  

-Teresa

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Oscar Olsson
Sent: Tuesday, January 10, 2006 7:49 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] More NW 7.3 oddness.

I just opened the following case. Might be good to know for others who 
experience similar issues:

---

It seems like the block size in networker 7.3 doesn't work as expected
for 
devices. With 7.2.1, we
used the following in the networker startup script to set the block
size:

         set NSR_DEV_BLOCK_SIZE_SAIT_1=64
         export NSR_DEV_BLOCK_SIZE_SAIT_1

We have modified the networker 7.3 startup script to reflect this. We
have 
also configured all
devices to use 64kb blocksize in the networker admin GUI. However, this 
doesn't seem to work
anymore, because we get the following error:

(from daemon.log):

01/10/06 13:28:23 nsrd: media notice: Volume "007494S1" on device
"rd=sn01:/dev/nst0": Block size is 32768 bytes not 65536 bytes. Verify
the 
device
configuration. Tape positioning by record is disabled.

The tape was just labeled, and an old volume was overwritten, which had
a 
block size of 64kb. The
tape was moments before labeled in the same drive as the error occured
in.

Worth noting (altoigh not directly related to this issue) is that it now

waits for more tapes to be
mounted than there are available devices, which makes it relabel tapes 
instead of mounting existing
non-full tapes in that pool. In NW 7.2.1, no more tape mount requests
were 
listed as pending when
there were no more available devices to mount them in.

---

In general, NW 7.3 feels like an immature product, full of old code that

has been temporarily fixed and patched, with a "new" Java GUI which
makes 
monitoring of server operations more difficult. It seems common that 
things that were fixed by a hack in one release are then gone in the
next 
one. To summarize: with NW, I feel like I'm constantly beta-testing it. 
And considering how much stuff I tend to come up with... well..

//Oscar

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER