Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1061355

Bug#989571: linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption

Cross-posted to 2 groups.

Show all headers | View raw

Control: severity -1 important
Control: tags -1 moreinfo

On Mon, Jun 07, 2021 at 08:43:21PM +0100, Anton Ivanov wrote:
> Version: 5.10.13-1~bpo10+1

This is not the latest version. 5.10.24 (at least) is in buster-backports.

> [801076.291139] scsi host10: uas
> [801076.291557] scsi 10:0:0:0: Direct-Access     ASMT     2115             0    PQ: 0 ANSI: 6
> [801076.292065] sd 10:0:0:0: Attached scsi generic sg0 type 0
> [801076.292232] sd 10:0:0:0: [sda] Spinning up disk...
> [801077.321342] ......ready
> [801082.447597] sd 10:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
> [801082.447600] sd 10:0:0:0: [sda] 4096-byte physical blocks
> [801082.447673] sd 10:0:0:0: [sda] Write Protect is off
> [801082.447674] sd 10:0:0:0: [sda] Mode Sense: 43 00 00 00
> [801082.447832] sd 10:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [801082.448032] sd 10:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
> [801082.494646] sd 10:0:0:0: [sda] Attached SCSI disk

So it detects a 4TB disk called sda.  Not a <20GB as you claimed.

> [801150.687429] loop: module loaded
> [801150.815997] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
> [803002.579925] blk_update_request: I/O error, dev loop0, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
> [803002.579960] blk_update_request: I/O error, dev loop0, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

But you mount an unrelated loop0.  Don't do that?  Okay, write requests
fail.

> [803318.984016] EXT4-fs (loop0): mounting ext3 file system using the ext4 subsystem
> [803318.984583] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)

Again you mount loop0, but now it sees an ext3, not an ext4 on it.

Something on your system creates loop devices.  You have to find it.

Maybe the output of "lsblk" can help to see what you actually have.

Bastian

-- 
There's a way out of any cage.
		-- Captain Christopher Pike, "The Menagerie" ("The Cage"),
		   stardate unknown.

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#989571: linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption Anton Ivanov <anton.ivanov@kot-begemot.co.uk> - 2021-06-07 22:10 +0200
  Bug#989571: linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption Bastian Blank <waldi@debian.org> - 2021-06-07 22:50 +0200
    Bug#989571: linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption Anton Ivanov <anton.ivanov@kot-begemot.co.uk> - 2021-06-07 23:40 +0200

csiph-web