Your message dated Sat, 2 Nov 2024 15:33:58 +0100
with message-id <zyy4voumtmohu...@eldamar.lan>
and subject line Re: Bug#1086230: linux: LTFS mount failure on ATTO H680 due to 
possible pm80xx driver SCSI length mismatch
has caused the Debian Bug report #1086230,
regarding linux: LTFS mount failure on ATTO H680 due to possible pm80xx driver 
SCSI length mismatch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1086230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: src:linux
Severity: normal
X-Debbugs-Cc: joseppe.maye...@gmail.com

Dear Maintainer,

I’m reporting an issue encountered with LTFS on Debian 12 using the ATTO 
ExpressSAS H680 HBA, potentially due to a compatibility problem with the pm80xx 
driver.

Problem Details:

What led up to the situation?

Attempting to mount a tape with LTFS using the ATTO ExpressSAS H680 HBA.

What exactly did you do (or not do) that was effective (or ineffective)?

Executed a standard LTFS mount operation, which consistently fails when 
attempting to read the tape index during the mount process.

What was the outcome of this action?

LTFS outputs the following error message, suggesting an issue with SCSI data 
transfer length handling:

LTFS30216W Length mismatch is detected. (Act = 524288, resid = 0, resid_sense = 
523235).

As a result, the tape fails to mount.

What outcome did you expect instead?

I expected LTFS to mount the tape without issues, as it does on macOS with the 
ATTO vendor-specific driver.

Additional Information:
The same hardware works without issues on macOS, which suggests a potential bug 
or missing feature in the pm80xx driver regarding SCSI data transfer length 
handling for this device.

Please let me know if further information or testing is needed.



-- System Information:
Debian Release: 12.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.8.12-2-pve (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message ---
Hi,

On Tue, Oct 29, 2024 at 12:10:13PM +0200, joseppe mayer wrote:
> Hi Salvatore,
> 
> Thank you for the guidance.
> 
> At the moment, I am unable to test on a clean Debian kernel. However, I
> thought Proxmox was built on the Debian kernel, but I’m happy to report
> this issue upstream as you suggested. I will keep this report updated with
> any findings from my tests or responses from the upstream maintainers.

FWIW, thanks for reporting it upstream.

I will close this bug specifically, as the issue was detected in a
non-Debian kernel and the issue is now reported upstream. If it
affects stable series as used in Debian, the fix would flow into it
via the regular rebases we do.

If you will be able to reproduce it specifically with Debian, then
feel free to reopen as well the bug.

Thanks already!

Regards,
Salvatore

--- End Message ---

Reply via email to