Why does e2fsck keep the '?' files? They seem completely
illegal, at least as far as /bin/ls can tell.
If e2fsck finds several severely corrupt inodes, I think it
should go into a suspicious mode that throws out anything
with extremely weird permissions. For example, I've never
seen ------x-w- on a real file. AFAIK, Linux only uses the
sticky bit on directories: any non-directory with that flag
is corrupt. Suid and sgid have no meaning for device special
files, so those are invalid too.
[trimmed example]
26853 c--x-wxr-T 1 30840 14640 58, 48 Feb 23 2014 #26853
27793 br-x-w---- 1 26740 27758 101, 110 Sep 24 2022 #27793
27794 ?r-xrw-rwt 1 26925 8564 1634020718 Sep 12 2028 #27794
27795 br-Srw--w- 1 27425 15392 46, 101 Sep 9 2028 #27795
27796 c--xr--rwx 1 14641 26990 116, 105 Jun 29 1975 #27796
27798 ?--sr-sr-t 1 15392 27765 1986491189 Oct 10 2021 #27798
27799 ?--x-w-r-- 1 20525 20013 1769239407 Oct 23 2030 #27799
27800 ?r-xrwS-wx 1 28784 18954 779383407 Mar 20 14:23 #27800
27801 c---rwxrw- 1 26989 28535 114, 100 Jan 29 2029 #27801
27802 br-xr-sr-- 1 29728 25970 32, 115 Oct 6 2023 #27802
27803 c--xr-xrwx 1 28535 26223 104, 116 Mar 17 2031 #27803
27804 br-sr-srwT 1 24944 26144 101, 112 Nov 28 2023 #27804
27809 br-x-w---- 1 26740 27758 101, 110 Sep 24 2022 #27809
27810 c--SrwS-wT 1 25966 26977 111, 97 Apr 27 2024 #27810