Blank tape

[scsitape]

Blank tape

[jmwilson]

Can you try the cleanup branch on jmwilson/stenc? I'm unable to get a blank tape to trigger this sense code. The old code would ignore all errors in the next block encryption status query, so I added a media access check but my hardware will not report a blank tape.

[sunwire]

Can you try the cleanup branch on jmwilson/stenc?

Still the same error, blank tape. But it fixes #72
If I add O_NONBLOCK flag to line

stenc/src/scsiencrypt.cpp

Line 92 in f5856d7

unique_fd fd {open(device.c_str(), O_RDONLY)};

it also fixes #12 (under Linux)

[jmwilson]

This could be a drive firmware bug then. HP docs say this about the blank tape sense key:

If “blank media” is encountered during a space (in other words, the drive attempted to space on an unformatted tape), the drive behaves as if EOD was at BOM. It will then respond with GOOD status to a request to space to EOD, and with CHECK CONDITION to any other forward spacing request. Additional sense is set to 1403h (End of data not found).

Requesting status will not move the tape. The firmware might be incorrectly returning this code during the normal media access check when the next block encryption status page is processed. An erased tape returns Volume Encryption: Unable to determine on a HP LTO-6.

The old code simply ignored all errors from the next block encryption status query, but this probably not good in general. It sounds like the best idea to ignore BLANK CHECK sense key in this specific case.

[jmwilson]

@sunwire I forced pushed the cleanup branch again with a check for the BLANK CHECK sense - can you see if this handles your situation?

[sunwire]

can you see if this handles your situation?
Everything works!

[sunwire]

Fixed