From: Michael Ablassmeier <abi@grinser.de>
To: stgt@vger.kernel.org
Subject: Re: VTL emulation, no barcodes shown in mtx
Date: Wed, 6 Jan 2021 23:08:05 +0100 [thread overview]
Message-ID: <20210106220805.gztfmh7he76pwnci@lrrr.dead-link.org> (raw)
In-Reply-To: <20210106185825.h7v4dpn2cg3gdejc@lrrr.dead-link.org>
hi again,
On Wed, Jan 06, 2021 at 07:58:25PM +0100, Michael Ablassmeier wrote:
> > mtx -f /dev/sg8 status
> > Storage Changer /dev/sg8:1 Drives, 8 Slots ( 0 Import/Export )
> > Data Transfer Element 0:Empty
> > Storage Element 1:Full
> > Storage Element 2:Full
> > Storage Element 3:Empty:VolumeTag=
it seems this i a regression introduced by one of the following commits
to smc.c:
> commit 2de8bebe132e3b998bf4848d0bd22b50367ad4b8
> Author: Lee Duncan <lduncan@suse.com>
> Date: Sat Feb 16 10:29:19 2019 -0800
>
> Fix gcc7 string truncation warnings.
> commit 73cb8f355479d8f7cb402ca967b137d4a32c8f76
> Author: FUJITA Tomonori <tomof@acm.org>
> Date: Fri Jul 28 11:34:15 2017 +0900
> smc: fix snprintf warnings with gcc7
i reverted both commits and removed -WAll from the makefile to be
able to compile, and now mtx show the barcodes:
> Storage Changer /dev/sg8:1 Drives, 8 Slots ( 0 Import/Export )
> Data Transfer Element 0:Empty
> Storage Element 1:Full :VolumeTag=TAPE001
> Storage Element 2:Full :VolumeTag=TAPE002
bye,
- michael
next prev parent reply other threads:[~2021-01-06 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 18:58 VTL emulation, no barcodes shown in mtx Michael Ablassmeier
2021-01-06 19:01 ` Michael Ablassmeier
2021-01-06 22:08 ` Michael Ablassmeier [this message]
2021-01-06 22:28 ` [PATCH] " Michael Ablassmeier
2021-01-06 22:41 ` Michael Ablassmeier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210106220805.gztfmh7he76pwnci@lrrr.dead-link.org \
--to=abi@grinser.de \
--cc=stgt@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).