I was referring to physically write-protecting the tape so as to
eliminate any possibility of someone inadvertantly re-labeling the tape.
I have seen at least one case where someone was messing around with the
tar archive utility, thinking they were accessing a different drive, and
they ended up writing over the NetWorker label on the wrong tape because
the device names were mismatched. Hence, we always physically write
protect tapes as soon as we can. I should have been clearer on that
point.
I would have to recover an older version of the logs to see what
actually transpired on or about that time as the current logs don't go
back that far. I will check the cores, but the last time this tape was
written to was the end of January 2003.
George
Carston Locher wrote:
>
> George,
>
> You should check /nsr/cores for any new core dumps. My guess is
> you'll see a core dump for nsrmmd. I've seen this problem with
> tapes that were being written to and either nsrmmd or NetWorker
> in general went down unexpectedly.
>
> You should also check /nsr/logs/daemon.* and see if you can find
> any problems that happened during the history of that tape. My
> guess is if you still have the logs you'll see some kind of crash
> during the writing to that tape.
>
> Another comment from your original email bothers me. You mention the
> tape was full so you write protected it. Once a tape is full there
> is no need for you to write protect it. NetWorker marks the tape
> as full and will not try to write to it. Could you explain the logic
> of write protecting it to me?
>
> Thanks,
>
> Carston
>
> -----Original Message-----
> From: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]On Behalf Of George Sinclair
> Sent: Monday, March 17, 2003 11:32 AM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] Has anyone seen this one?
>
> I'm not familar with any way to remove savesets from a tape. I guess you
> were suggesting removing the saveset from the media database using the
> command line?
>
> I opened a call with Legato about this matter. They suspect that the
> media database could contain some corruption, and the corruption is
> preventing the tape from mounting. They suggested one possible solution
> would be to remove the volume, scan the tape and then try mounting.
> Perhaps removing the volume would remove the corruption, and since we
> still have the tape, we could then scan it back in. Of course, if
> corruption is the culprit, I guess we really have nothing to lose since
> we can't mount the tape.
>
> I had some more questions for them, and I'm still waiting to hear back.
> Will post a follow -up as soon as I know something.
>
> The mminfo command shows the tape as full.
>
> Thanks.
>
> George
>
> Bob Schuknecht wrote:
> >
> > George,
> >
> > We've seen this before. Networker wants to write an end-of-file marker on
> > this tape.
> > Try marking the tape as appendable and see if there is enough space left
> on
> > it to
> > write the EOF. Furthermore, you can always mount the tape manually using
> > nsrjb and
> > the '-n' switch though I don't know what you'd do with the tape once it
> were
> > manually
> > mounted. Another option is to view the save sets on that volume and delete
> > the
> > problem save set.
> >
> > -----Original Message-----
> > From: George Sinclair [mailto:George.Sinclair AT noaa DOT gov]
> > Sent: Thursday, March 13, 2003 9:38 AM
> > To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> > Subject: [Networker] Has anyone seen this one?
> >
> > Okay,
> >
> > I went to mount a full LTO tape yesterday, and as NetWorker was trying
> > to mount it, a message popped into the nwadmin messages box indicating
> > that NetWorker was writing x number of bytes before the crash -- I don't
> > recall any crash -- so then it forwards a bunch of records through the
> > tape and when it reaches the point where it wants to start writing data
> > -- I guess that's what it wanted to do -- it then complains that the
> > tape is read-only. Well, of course it's write-protected because the
> > volume window shows it as full, so we write-protected it sometime ago.
> > NetWorker then ejects the tape. Hmm.... Obviously, un-write protecting
> > the tape will not help since there's no space. What should I do?! I
> > can't mount the tape without NetWorker insisting on wanting to write to
> > it. There was no activity going on on the server or storage node at the
> > time. nwadmin shows everything is quiet. All groups are dormant. Nothing
> > is running. I can mount other tapes in this same pool, and they mount
> > just dandy. Clearly, NetWorker must have had some problem at some point
> > in the past and it still thinks it has some stuff to write to this
> > volume? How can that be?! How do I fix that?
> >
> > Thanks.
> >
> > George
> >
> > --
> > Note: To sign off this list, send a "signoff networker" 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 networker" 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 networker" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
