Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Input/Output error with any operation on tape #3

Open
WORMSTweaker opened this issue May 15, 2024 · 2 comments
Open

Input/Output error with any operation on tape #3

WORMSTweaker opened this issue May 15, 2024 · 2 comments
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@WORMSTweaker
Copy link

WORMSTweaker commented May 15, 2024

Hello!

I found STFS randomly, and I've been interested to try ever since discovering it! It's some really nice stuff, but that's not what I'm here to talk about

After installing STFS via the script, I wanted to try it out on my tape drive, only to be met with a very enigmatic "Input/Output error", while trying to server an FTP server. I thought that maybe my tape needed to be initialized, so I tried to do a stfs operation initialize, but it results in the same cryptic I/O error...

What could be the issue here? And thank you in advance for your help!

A few spec details:
OS: Arch, x86_64, Linux kernel 6.6.30-2-lts
SAS controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2
Tape Drive: HP Ultrium 3280 LTO5 External Drive
Command: stfs serve ftp -d /dev/st0 -m ~/Tape/metadata/metadata.sqlite --cache-write-type memory --compression brotli --compression-level 9 -v 4

Some verbose logs taken from STFS output:
stfs_debug.log

dmesg output when running STFS:

[ 8927.463637] st 5:0:0:0: device_block, handle(0x0009)
[ 8929.213272] st 5:0:0:0: device_unblock and setting to running, handle(0x0009)
[ 8929.215088] mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x500110a0140c68b8)
[ 8929.215091] mpt2sas_cm0: removing handle(0x0009), sas_addr(0x500110a0140c68b8)
[ 8929.215092] mpt2sas_cm0: enclosure logical id(0x500605b007b728d0), slot(3)
[ 9096.221722] mpt2sas_cm0: handle(0x9) sas_address(0x500110a0140c68b8) port_type(0x1)  --Plugged & started up drive
[ 9096.223943] scsi 5:0:1:0: Sequential-Access HP       Ultrium 5-SCSI   X5BD PQ: 0 ANSI: 6
[ 9096.223966] scsi 5:0:1:0: SSP: handle(0x0009), sas_addr(0x500110a0140c68b8), phy(3), device_name(0xa0100150b6680c14)
[ 9096.223976] scsi 5:0:1:0: enclosure logical id (0x500605b007b728d0), slot(3) 
[ 9096.223987] scsi 5:0:1:0: qdepth(254), tagged(1), scsi_level(7), cmd_que(1)
[ 9096.224419] scsi 5:0:1:0: Power-on or device reset occurred
[ 9096.227259] scsi 5:0:1:0: TLR Enabled
[ 9096.238043] st 5:0:1:0: Attached scsi tape st0
[ 9096.238047] st 5:0:1:0: st0: try direct i/o: yes (alignment 4 B)
[ 9096.238663]  end_device-5:1: add: handle(0x0009), sas_addr(0x500110a0140c68b8)
[ 9216.366703] st 5:0:1:0: [st0] Block limits 1 - 16777215 bytes.      --Ran `mt-st -f /dev/st0 status`
[ 9233.511391] st 5:0:1:0: [st0] Sense Key : Illegal Request [current] --Ran `stfs serve ftp` (once, notice the error repeating)
[ 9233.511397] st 5:0:1:0: [st0] Add. Sense: Invalid field in cdb
[ 9245.095731] st 5:0:1:0: [st0] Sense Key : Illegal Request [current] 
[ 9245.095748] st 5:0:1:0: [st0] Add. Sense: Invalid field in cdb
@pojntfx pojntfx added bug Something isn't working documentation Improvements or additions to documentation labels Jul 30, 2024
@pojntfx
Copy link
Owner

pojntfx commented Jul 30, 2024

Hi! Any chance you might be running into #1 ?

@WORMSTweaker
Copy link
Author

Oh whoops! That was indeed it! I didn't connect the dots and think that those 2 issues could be related, but indeed setting stsetoptions scsi2logical allows everything to work properly, initialization ftp and file writing

Very sorry about this (easily resolvable) open issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants