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

[geole0]

Hello.
When I decide to reduce the size of a partition stored in an external drive and formatted in EXT4 after booting with ubuntu 19.10, this partition is destroyed. it seems abnormal to me.

This is systematic for the twelve partitions   and twelve boots in the
prepared context.

If several partitions are reduced in the same passage, only the first in
the list is destroyed. The others are well treated!

Failure does not occur if another external drive is used.

The incident does not occur if the partition is formatted in EXT3 or if
the size reduction is done with ubuntu 18.04.3

Some results will be provided as an attachment

Here is the script used.


export LC_ALL=POSIX
Size=35957760k
Debug="-d 60"
Trace=Bug1857914-ThreePartitions.txt
date>$Trace
for Part  in  sdb1 sdb6 sdb7  ;    do
    sudo umount /dev/$Part
    echo "================================check file system on /dev/$Part for errors with command sudo e2fsck -f -y -v  /dev/$Part >>$TRACE" >>$Trace
    sudo e2fsck -f -y -v  /dev/$Part 2>>$Trace >>$Trace
    echo "================================ shrink for /dev/$Part with command sudo resize2fs $Debug -p /dev/$Part $Size >>$Trace" >>$Trace
    sudo resize2fs $Debug -p /dev/$Part  $Size 2>>$Trace >>$Trace
    echo "================================check file system on /dev/$Part for errors with command sudo e2fsck   -f -n -v  /dev/$Part >>$TRACE" >>$Trace
    sudo e2fsck -f -n -v  /dev/$Part 2>>$Trace  >>$Trace
    echo "================================check for erreur on UAS  module with command journalctl -b | egrep  "resize2fs|uas_eh_abort_handler" >>$TRACE" >>$Trace
done
journalctl -b  | grep -E  "resize2fs|CDB|uas_eh_abort_handler|I/O error|sdb" >>$Trace
date>>$Trace
cat $Trace



** Attachment added: "An execution with three partitions"
   https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5323753/+files/Bug1857914-ThreePartitions.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