I'm using Exabyte and DLT drives on Solaris 2.7 and 2.8.
On some hosts, everything looks good when I write to
tape, but when I read the tape back, I see that all
individual tape files have actually become one. It
looks like tape markers are not being written between
files.
I have used truss to verify that the process I am running
is indeed opening and closing the tape device.
There is an "mtio get" command issued immediately prior
to each close. My understanding is that this command
should not cause a problem, but if I remove it, the problem
goes away.
This process has worked for years, but recently our sysadmin
installed some new patches on some of our systems and the
problem began.
I do not know if it is a coding problem which just worked
by chance in the past, or if it is some kind of O/S, driver
problem.
I also cannot find a good reference on programming tape
devices. I'm basically using open/close/read/write system
calls and ioctl to issue the mtio commands.
Any ideas?
On some hosts, everything looks good when I write to
tape, but when I read the tape back, I see that all
individual tape files have actually become one. It
looks like tape markers are not being written between
files.
I have used truss to verify that the process I am running
is indeed opening and closing the tape device.
There is an "mtio get" command issued immediately prior
to each close. My understanding is that this command
should not cause a problem, but if I remove it, the problem
goes away.
This process has worked for years, but recently our sysadmin
installed some new patches on some of our systems and the
problem began.
I do not know if it is a coding problem which just worked
by chance in the past, or if it is some kind of O/S, driver
problem.
I also cannot find a good reference on programming tape
devices. I'm basically using open/close/read/write system
calls and ioctl to issue the mtio commands.
Any ideas?