Kernel version is 5.4.0-28. Just upgraded to Ubuntu 20.04. btrfs-progs is version 5.6 That inode search returned an error: ERROR: ino paths ioctl: Input/output error I don't use any subvolumes. The next command also resulted in an error. Replaced the actual mountpoint in the error with /mountpoint. ERROR: not a block device or regular file: /mountpoint/ ERROR: device scan /mountpoint/: Input/output error Something definitely doesn't seem right. On Wed, May 6, 2020 at 7:55 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > On Wed, May 6, 2020 at 3:54 PM Tyler Richmond <t.d.richmond@xxxxxxxxx> wrote: > > > > Hello, > > > > I looked up this error and it basically says ask a developer to > > determine if it's a false error or not. I just started getting some > > slow response times, and looked at the dmesg log to find a ton of > > these errors. > > > > [192088.446299] BTRFS critical (device sdh): corrupt leaf: root=5 > > block=203510940835840 slot=4 ino=1311670, invalid inode generation: > > has 18446744073709551492 expect [0, 6875827] > > [192088.449823] BTRFS error (device sdh): block=203510940835840 read > > time tree block corruption detected > > [192088.459238] BTRFS critical (device sdh): corrupt leaf: root=5 > > block=203510940835840 slot=4 ino=1311670, invalid inode generation: > > has 18446744073709551492 expect [0, 6875827] > > [192088.462773] BTRFS error (device sdh): block=203510940835840 read > > time tree block corruption detected > > [192088.464711] BTRFS critical (device sdh): corrupt leaf: root=5 > > block=203510940835840 slot=4 ino=1311670, invalid inode generation: > > has 18446744073709551492 expect [0, 6875827] > > [192088.468457] BTRFS error (device sdh): block=203510940835840 read > > time tree block corruption detected > > > > btrfs device stats, however, doesn't show any errors. > > > > Is there anything I should do about this, or should I just continue > > using my array as normal? > > What kernel version? This looks like relatively recent kernel > reporting format. Can you search for inode 1311670? e.g. > > $ sudo btrfs insp ino -v 1311670 /mountpoint > > Note that each subvolume has its own set of inodes. You need to point > the command to the correct subvolume. In this case it's root=5 which > is the default/top-level. As long as you haven't changed the default > subvolume, and you've mounted the file system without subvol or > subvolid option, it should point to the correct file that's affected > by this. And also maybe useful: > > $ sudo btrfs insp dump-t -b 203510940835840 /mountpoint > > > > -- > Chris Murphy
