Path: csiph.com!4.us.feeder.erje.net!3.eu.feeder.erje.net!2.eu.feeder.erje.net!feeder.erje.net!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!bofh.it!news.nic.it!robomod From: Bastian Blank Newsgroups: linux.debian.bugs.dist,linux.debian.kernel Subject: Bug#989571: linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption Date: Mon, 07 Jun 2021 22:50:01 +0200 Message-ID: References: X-Original-To: Anton Ivanov , 989571@bugs.debian.org X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Mon Jun 7 20:45:08 2021 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -2.6 Reply-To: Bastian Blank , 989571@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: Debian Kernel Team X-Debian-Pr-Message: followup 989571 X-Debian-Pr-Package: src:linux X-Debian-Pr-Source: linux MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-Greylist: delayed 355 seconds by postgrey-1.36 at buxtehude; Mon, 07 Jun 2021 20:42:09 UTC X-Debian-Message: from BTS X-Mailing-List: archive/latest/1666960 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 46 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 7 Jun 2021 22:36:03 +0200 X-Original-Message-ID: <20210607203603.GA1884@shell.thinkmo.de> X-Original-References: <162309500123.8128.16275913823855412743.reportbug@madding.kot-begemot.co.uk> <162309500123.8128.16275913823855412743.reportbug@madding.kot-begemot.co.uk> Xref: csiph.com linux.debian.bugs.dist:1061355 linux.debian.kernel:72137 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.