From: Dominik Csapak <d.csapak@proxmox.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>,
pbs-devel@lists.proxmox.com
Subject: Re: applied: [PATCH proxmox-backup] tape: workaround non-standard drive behavior for rewind
Date: Tue, 14 Jul 2026 13:21:47 +0200 [thread overview]
Message-ID: <9085c3dc-eb28-4b5c-ab56-412219f654a4@proxmox.com> (raw)
In-Reply-To: <178402620783.364806.3639573565454111413.b4-ty@proxmox.com>
btw. this patch probably should not have been applied in this form.
dietmar wrote an answer but this didn't reach the mailing list
the root cause is probably another process/client interfering
with the tape drive, not a direct issue with the drive itself.
(and we can't safeguard against that)
while it'd do not much harm, i think it best to revert this again
(for now)
sorry for the inconvenience
prev parent reply other threads:[~2026-07-14 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 14:26 [PATCH proxmox-backup] tape: workaround non-standard drive behavior for rewind Dominik Csapak
2026-07-14 10:53 ` applied: " Fabian Grünbichler
2026-07-14 11:21 ` Dominik Csapak [this message]
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=9085c3dc-eb28-4b5c-ab56-412219f654a4@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/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