[Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT

geole0 1860917 at bugs.launchpad.net
Sun Feb 2 11:25:18 UTC 2020


ATTENTION
This error is new. and it is because  of use of logical device not un good order!!!!!!!
Feb 02 10:59:19 a systemd[1315]: mnt-USBsdb3.mount: Succeeded.
Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Feb 02 10:59:57 a kernel: usb 4-2: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd

** Attachment added: "Trace of  one execution"
   https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5324760/+files/Bug1857914-102-176-8192Mo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1860917

Title:
   uas_eh_abort_handler  uas-tag  inflight OUT

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  591/5000
  Hello
  To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game.

  Using this test game consisting only of cp and diff commands, I caused a similar problem.
  The first visible consequence which seems serious to me: The copied file is not identical to the sending file.
  It seems that the blocks are shifted.

  It would be desirable for the user to be warned that the written files
  have become incorrect.

  Thank you for your advice.

  Journalctl says only
  janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
  janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT 
  janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00
  janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
  a at a:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions



More information about the foundations-bugs mailing list