[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1032027: linux: i_reserved_data_blocks (2) not cleared



Source: linux
Severity: normal
X-Debbugs-Cc: sergey.aleynikov+deb@gmail.com

Dear Maintainer,

I have the following disk configuration:

sda                                  8:0    0 14.6T  0 disk
└─disk6                            254:0    0 14.6T  0 crypt
  └─disk6-part1                    254:1    0 14.6T  0 part
    └─md0                            9:0    0 58.2T  0 raid6
      ├─md0p1                      259:7    0  128G  0 part  /
      └─md0p2                      259:8    0 58.1T  0 part
sdb                                  8:16   0 14.6T  0 disk
└─disk2                            254:8    0 14.6T  0 crypt
  └─disk2-part1                    254:9    0 14.6T  0 part
    └─md0                            9:0    0 58.2T  0 raid6
      ├─md0p1                      259:7    0  128G  0 part  /
      └─md0p2                      259:8    0 58.1T  0 part
sdc                                  8:32   0 14.6T  0 disk
└─disk3                            254:6    0 14.6T  0 crypt
  └─disk3-part1                    254:7    0 14.6T  0 part
    └─md0                            9:0    0 58.2T  0 raid6
      ├─md0p1                      259:7    0  128G  0 part  /
      └─md0p2                      259:8    0 58.1T  0 part
sdd                                  8:48   0 14.6T  0 disk
└─disk1                            254:10   0 14.6T  0 crypt
  └─disk1-part1                    254:11   0 14.6T  0 part
    └─md0                            9:0    0 58.2T  0 raid6
      ├─md0p1                      259:7    0  128G  0 part  /
      └─md0p2                      259:8    0 58.1T  0 part
sde                                  8:64   0 14.6T  0 disk
└─disk4                            254:4    0 14.6T  0 crypt
  └─disk4-part1                    254:5    0 14.6T  0 part
    └─md0                            9:0    0 58.2T  0 raid6
      ├─md0p1                      259:7    0  128G  0 part  /
      └─md0p2                      259:8    0 58.1T  0 part
sdf                                  8:80   0 14.6T  0 disk
└─disk5                            254:2    0 14.6T  0 crypt
  └─disk5-part1                    254:3    0 14.6T  0 part
    └─md0                            9:0    0 58.2T  0 raid6
      ├─md0p1                      259:7    0  128G  0 part  /
      └─md0p2                      259:8    0 58.1T  0 part

Device md0 is constructed on top of 6x cryptsetup disks as following:

md0 : active raid6 dm-11[6] dm-9[4] dm-7[3] dm-5[2] dm-3[7] dm-1[0]
      62499463424 blocks super 1.2 level 6, 64k chunk, algorithm 2 [6/6] [UUUUUU]

Root filesystem is mounted from md0p1 with the following options:

UUID=bff1f017-bca2-4acc-9b97-170474c5e198 /                  ext4    noatime,nodelalloc,barrier=1,data=ordered 0       1

I've recently observed the following error in dmesg:

[163925.493694] EXT4-fs (md0p1): Inode 6562253 (00000000b30df460): i_reserved_data_blocks (2) not cleared!

It haven't repeated since. Messages preceeding it are from kvm, like this one:

[163814.292207] kvm [31458]: ignored rdmsr: 0x1a2 data 0x0

Does this mean a filesystem corruption? Do I need to take any additional steps (like force fsck), or would it recover silently?

-- System Information:
Debian Release: 11.6
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-21-amd64 (SMP w/56 CPU threads)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Reply to: