-
Notifications
You must be signed in to change notification settings - Fork 13
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
bad rip value; linux 5.4/ubuntu w/ tape drive #21
Comments
Same here: uname -aLinux node234.domain.com 5.4.106-1-pve #1 SMP PVE 5.4.106-1 (Fri, 19 Mar 2021 11:08:47 +0100) x86_64 x86_64 x86_64 GNU/Linux (Proxmox Kernel, Debian 10) Container (LXC): CentOS Linux release 8.3.2011 mt --versionmt-st v. 1.1 Tape drive: Quantum LTO-7 HH Task: mt -f /dev/st0 erase [ 1451.195489] INFO: task mt:5821 blocked for more than 1208 seconds. |
Have a machine running ubuntu 20.04
#uname -a
Linux loki 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
mt-st --version
mt-st v. 1.3
commands being sent:
mt-st -f /dev/st0 rewind
mt-st -f /dev/st0 setblk 0
mt-st -f /dev/st0 defblksize 0
mt-st -f /dev/st0 defcompression 1
mt-st -f /dev/st0 compression 1
# dmesg happens with the weof command
mt-st -f /dev/st0 weof
mt-st -f /dev/st0 rewind
sending tape commands to external LTO6 tape drive; when writing eof to tape am getting bad rip values reported:
[145607.017412] INFO: task mt-st:1854856 blocked for more than 120 seconds.
[145607.017440] Tainted: P O 5.4.0-54-generic #60-Ubuntu
[145607.017460] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[145607.017483] mt-st D 0 1854856 1761783 0x00000000
[145607.017486] Call Trace:
[145607.017496] __schedule+0x2e3/0x740
[145607.017498] schedule+0x42/0xb0
[145607.017499] schedule_timeout+0x10e/0x160
[145607.017505] ? blk_mq_run_hw_queue+0x92/0x120
[145607.017506] wait_for_completion+0xb1/0x120
[145607.017510] ? wake_up_q+0x70/0x70
[145607.017515] st_do_scsi.constprop.0+0x37a/0x3f0 [st]
[145607.017517] st_int_ioctl+0x6ff/0xf70 [st]
[145607.017519] st_ioctl+0x37a/0xba0 [st]
[145607.017522] do_vfs_ioctl+0x407/0x670
[145607.017525] ? putname+0x4a/0x50
[145607.017526] ksys_ioctl+0x67/0x90
[145607.017527] __x64_sys_ioctl+0x1a/0x20
[145607.017530] do_syscall_64+0x57/0x190
[145607.017532] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[145607.017534] RIP: 0033:0x7f4714e7750b
[145607.017539] Code: Bad RIP value.
[145607.017540] RSP: 002b:00007ffcb0ee9758 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[145607.017541] RAX: ffffffffffffffda RBX: 0000556ccc5fb020 RCX: 00007f4714e7750b
[145607.017542] RDX: 00007ffcb0ee9770 RSI: 0000000040086d01 RDI: 0000000000000003
[145607.017543] RBP: 0000000000000003 R08: 0000000000000000 R09: 00007f4714f76d50
[145607.017543] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000003
[145607.017544] R13: 0000000000000004 R14: 00007ffcb0ee99b8 R15: 0000000000000004
the EOF appears to be written and commands appear to complete however the above is being dumped to dmesg.
The text was updated successfully, but these errors were encountered: