Networker

Re: [Networker] wrong tape capacitiy displayed

2005-02-22 10:43:44
Subject: Re: [Networker] wrong tape capacitiy displayed
From: Yura Pismerov <ypismerov AT TUCOWS DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 22 Feb 2005 10:39:20 -0500
        I don't think the "advertised" capacity matters.
        Networker does not really rely on it, but rather tries to write until 
it hits EOT.
        Hope this helps...

ingo AT visionet DOT de wrote:
Thanks so far.

I removed the tape from the database, wrote some bytes on the tape, so that
the tape label was deleted, and labeled the tape by hand as you suggest.
By the way: my problem ist the default capacity rather than the block size.

Questions:

Do I have to set the variables affecting the behaviour of the devices on
the server or on the storage node (or on both)?

Why doesn't this server by itsself know that Mammoth2-tapes have a native
capacity of 60GB? We have a 6.1.4-server with Mammoth2-drives at a
different site where this is not a problem at all.

Is the default capacity really being written on tape when labeling or is it
just an entry in the media database?


Thank you,
Ingo


On Tue, 22 Feb 2005 09:32:07 -0500, Stan Horwitz <stan AT TEMPLE DOT EDU> wrote:


On Tue, 22 Feb 2005, ingo AT visionet DOT de wrote:

Notice that there are four different capacities displayed!

I tried setting NSR_DEV_DEFAULT_CAPACITY_8MM_MAMMOTH_2=60GB on both server
and storage node and restarting networker. I am getting a message on
startup that this setting is ok, but when labeling a tape, the displayed
capacity is again randomly wrong.

I tried erasing a tape via Exabyte's MammothTool so that any existing tape
label would be deleted and then again labeling the tape. No effect.

Did you also remove the tape  you erased from NetWorker's media database?
If so, try erasing one of those tapes after removing it from the media db,
then use "nsrjb -L" to manually label the tape. This should compel
NetWorker to use the desired block size.

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


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

--
Yuri Pismerov, Sr. System Administrator,
TUCOWS.COM INC. (416) 535-0123  ext. 1352

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

<Prev in Thread] Current Thread [Next in Thread>