System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

tape drive problem with alpha GS60 in writing

MahdiRa
Frequent Advisor

tape drive problem with alpha GS60 in writing

Hi all
I have tru64 version 4 cluster system 1.6 contains three members: GS60, 2*A4000 all the members connected through router to backup library of two tapes LT8000.
The problem is between the tape and the GS60 it can read from the tape but it canâ t write in spite it can do from the other two nods
Mahd
9 REPLIES
Ralf Puchner
Honored Contributor

Re: tape drive problem with alpha GS60 in writing

any message within binary.errlog or /var/adm/messages?

Have you checked the scsi busses by using
clu_ivp -v. What does the "mt status" device tell you?

Are you sure rmt0 is identical on all machines? (use the "file" command to check)

Help() { FirstReadManual(urgently); Go_to_it;; }
Johan Brusche
Honored Contributor

Re: tape drive problem with alpha GS60 in writing


If the GS60 can read from the tapedrives, then the SCSI-bus mapping must be OK to do that.
What backup software do you use ? vdump, tar, Legato Networker, Veritas Netbackup ?
If one of the 2 last ones, is the GS60's client license OK ?

Is the cartdrige write-enabled (check with "file /dev/nrmt0h")
Is the protection of /dev/rmt0h on the GS60 OK crw-rw-rw ?

Johan.

_JB_
MahdiRa
Frequent Advisor

Re: tape drive problem with alpha GS60 in writing

hi all
am sorry for delay but i was in vacation....
all the files are WR with no problems in permissions. also i tried to write and read small file and it was succeeded, for large file there was the following error: tar : write: I/O error
the small file was 152K
the large one that fails: 4G

Mahdi
Johan Brusche
Honored Contributor

Re: tape drive problem with alpha GS60 in writing


Ahhh, tar !

Do you use the -E switch for tar, when archiving 'large files'.

I did not check for V4.x but on V5.x for large files >2G , tar switches from mmap() to malloc(), which means that the memory space allowed to the user by the system ie. per_proc_data_size must be large enough to accomodate large malloc's.

Johan.

_JB_
Ralf Puchner
Honored Contributor

Re: tape drive problem with alpha GS60 in writing

It seems a "blocking" or "limitation" problem with your backup software. Btw. tar is not a good choice for large backups. If it is a library use real backup tools like networker or veritas. This software stores the files within 2GB chunks readable by other architectures and uses streams to satisfy the write/read highwater-marks, preventing "streaming" of tapes.


Help() { FirstReadManual(urgently); Go_to_it;; }
MahdiRa
Frequent Advisor

Re: tape drive problem with alpha GS60 in writing


am using -E in my command and the same prob is happining
Johan Brusche
Honored Contributor

Re: tape drive problem with alpha GS60 in writing


Mahdi,

From your previous entry the problem was seen with tar and a file of 4G. At the time I asked to check if the per_proc_data_size was large enough to fit 4GB. You never came back with data on that subject,
so what is the result of "sysconfig -q proc | grep data_s" ?
Do tar files of >2GB on the 4100 too? If yes, what is the per_proc_data_size on that system.

Johan.

_JB_
Ralf Puchner
Honored Contributor

Re: tape drive problem with alpha GS60 in writing

Answer from madi:

per_proc_data_size 1073741824
Help() { FirstReadManual(urgently); Go_to_it;; }
Johan Brusche
Honored Contributor

Re: tape drive problem with alpha GS60 in writing

Mahdi,

We now know that you have a 1GB per_proc_data_space, but we do not know on what system....
So, once more, can you tar files > 2GB on the 4100 and what is the per_proc_data_space over there ???

patiently yours,
Johan.

_JB_