Date: Fri, 15 Jan 2016 20:58:29 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 206296] mt - write protect is not reported in status Message-ID: <bug-206296-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206296 Bug ID: 206296 Summary: mt - write protect is not reported in status Product: Base System Version: 10.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: andrew@grillet.co.uk The mt command does not show the "write protect" status of a tape. This wou= ld presumably apply to other devices that support write protection, but I cann= ot test for that.=20 You cannot write to write protected tapes (see BID9933), and get an error if you try - but it is very hard to find the error message if you tar to a wri= te protected tape using a remote login, and if you use a changer remotely, thi= s is seriously hard to debug!=20 So two bugs (possibly feature requests): 1) mt -f /dev/sa0 status # Should report "Write protected" or "Write enabled" as appropriate # I tried to implement this myself, but I think it might be easier for some= one else to do it! 2) tar c -f /dev/sa0 file # should write "Error: target is Write protected" to stderr # which presumably requires significant design effort, as both cam and tar # would need changes. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206296-8>