Write file to mhvtl fails

Env: mhvtl 1.7, media configured LTO8, 200GB capacity per tape.

cta-taped, 5.8.7

labelling was fine, when flushing files to tape, I got the following error.

Just wondering if there is an utility to test the drive/media in CTA format. tar seems fine with mhvtl.


Oct 16 15:44:32.242349 pps06 cta-taped: LVL="ERROR" PID="179092" TID="180402" MSG="Tape thread complete for writing" thread="TapeWrite" tapeDrive="DRIVE2" tapeVid="C03001" mountId="23" ErrorMessage="Failed verify for the VOL1:      /lib64/libctacommon.so.0(cta::exception::Backtrace::Backtrace(bool)+0x69) [0x7f1e71248ed9] /lib64/libctacommon.so.0(cta::exception::Exception::Exception(std::string const&, bool)+0x89) [0x7f1e7124a73d] /usr/bin/cta-taped() [0x57ad55] /usr/bin/cta-taped() [0x5822ce] /usr/bin/cta-taped() [0x50caef] /usr/bin/cta-taped() [0x5061bf] /usr/bin/cta-taped() [0x508562] /lib64/libctacommon.so.0(cta::threading::Thread::pthread_runner(void*)+0xef) [0x7f1e71270e97] /lib64/libpthread.so.0(+0x7ea5) [0x7f1e70f1aea5] /lib64/libc.so.6(clone+0x6d) [0x7f1e6acc698d]" type="write" mountTime="0.141417" positionTime="0.000000" waitInstructionsTime="0.106559" checksumingTime="0.000000" readWriteTime="0.000000" waitDataTime="0.000000" waitReportingTime="0.003609" flushTime="0.000000" unloadTime="0.003610" unmountTime="1.116502" encryptionControlTime="0.002412" transferTime="0.110168" totalTime="1.267894" dataVolume="0" headerVolume="0" files="0" payloadTransferSpeedMBps="0.000000" driveTransferSpeedMBps="0.000000" status="error"
Oct 16 15:44:32.242453 pps06 cta-taped: LVL="DEBUG" PID="179092" TID="180402" MSG="In MigrationReportPacker::reportEndOfSessionWithErrors(), pushing a report." thread="TapeWrite" tapeDrive="DRIVE2" tapeVid="C03001" mountId="23" ErrorMessage="Failed verify for the VOL1:      /lib64/libctacommon.so.0(cta::exception::Backtrace::Backtrace(bool)+0x69) [0x7f1e71248ed9] /lib64/libctacommon.so.0(cta::exception::Exception::Exception(std::string const&, bool)+0x89) [0x7f1e7124a73d] /usr/bin/cta-taped() [0x57ad55] /usr/bin/cta-taped() [0x5822ce] /usr/bin/cta-taped() [0x50caef] /usr/bin/cta-taped() [0x5061bf] /usr/bin/cta-taped() [0x508562] /lib64/libctacommon.so.0(cta::threading::Thread::pthread_runner(void*)+0xef) [0x7f1e71270e97] /lib64/libpthread.so.0(+0x7ea5) [0x7f1e70f1aea5] /lib64/libc.so.6(clone+0x6d) [0x7f1e6acc698d]" type="ReportEndofSessionWithErrors" mountTime="0.141417" positionTime="0.000000" waitInstructionsTime="0.106559" checksumingTime="0.000000" readWriteTime="0.000000" waitDataTime="0.000000" waitReportingTime="0.003609" flushTime="0.000000" unloadTime="0.003610" unmountTime="1.116502" encryptionControlTime="0.002412" transferTime="0.110168" totalTime="1.267894" dataVolume="0" headerVolume="0" files="0" payloadTransferSpeedMBps="0.000000" driveTransferSpeedMBps="0.000000" status="error"

Hi Simon,
I’m unsure re. the above error message.

For the purpose of testing drive/media in general we use the cta-ops-admin drive test and cta-ops-admin tape mediacheck, which are available as part of the CTA operations utilities. The tools however use a lower level dd in this case to write/read data, so CTA is only involved for the purpose of labelling (and the tape state management of course).

We’ll tag a new release in the near future (v1.5), which will include a number of fixes related to labelling and mount/unmount behavior in these tools, so I recommend waiting for this to be completed.

Hello Simon,
we have this ticket about LTO support in CTA generic drive: CTA cannot archive files on MHVTL ULTRIUM config (#257) · Issues · cta / CTA · GitLab

Our conclusion was that for now we stay with T10K mhvtl configuration.

Indeed migrating our CI runners means we would need to support both T10K and LTO in the DriveGeneric code: this means increasing the complexity.

And in practice changing the drive type in mhvtl will just change a few strings with no impact on the current tests we are running in CTA CI.

As we felt the gain/pain ratio was quite low there: we lowered this ticket priority, but we gladly accept MRs.