https://bugzilla.kernel.org/show_bug.cgi?id=203943 --- Comment #5 from Yann Ormanns (yann@xxxxxxxxxxx) --- Thank you for your support, Ted. About one week before the RAID got degraded, I created a full file-based backup, so at least I can expect minimal data loss - I just would like to save the time it would take to copy ~22TB back :-) Before filing a possible bug in the correct section for RAID, I'd like to comprehend the steps you described. In fact e2fsck does not report inode numbers, only variables ("%$i", and so does it for blocks, "%$b"). Using the the total inode count number in debugfs leads to an error: share ~ # tune2fs -l /dev/mapper/share | grep "Inode count" Inode count: 366268416 share ~ # debugfs /dev/mapper/share debugfs 1.44.5 (15-Dec-2018) debugfs: stat 366268416 366268416: File not found by ext2_lookup Or did I get you wrong? -- You are receiving this mail because: You are watching the assignee of the bug.
