On Mon, 4 Nov 2024, Theodore Ts'o wrote: >> >> (I had tune2fs -r in the back of my head.) >> > >> >I've aways used mke2fs -m and tune2fs -m, myself. I personally very >> >rarely using -m 0. >> >> I use -r 2048 or something like that much more than -m, that’s why. > >Fortunately, if you had tried -r 2048 with mke2fs, it wouldn't have >worked:
Yeah ;) but this time I wanted 0 for a change. Oops indeed. >> Linux cafe.XXX 5.10.0-33-amd64 #1 SMP Debian 5.10.226-1 (2024-10-03) x86_64 >> GNU/Linux >Linux kvm-xfstests 5.10.208-xfstests #7 SMP Sat Oct 5 17:17:16 EDT 2024 x86_64 >GNU/Linux So, why does 5.10.208-xfstests warn but 5.10.226-1 doesn’t? (It *does* warn about r1 128-byte-inode ones.) >In any case, Debian stable Yeah, but I switched to bullseye and will stick with that, so. >That being said, this is the first time in decades I've become award >that anyone had mistakenly used mke2fs -r 0. While I'm sure you're >not the only person who has run into this, I don't think it's a common >mistake. As a result, I don't feel a lot of urgency to fixing this; Sure. >at least, I don't think it requires asking the Debian release team to >push out emergency fixes to Debian Stable.... They can also do nōn-emergency fixes with the next point update. Anyway *I* became aware of it due to seeing the kernel warning by chance, which means others can also be. (Although the kernel warning does NOT show up, for me, on r0 fs so it was a combination of circum‐ stances here ☻ mostly me wanting to write something that can check all my systems…) bye, //mirabilos -- 16:47⎜«mika:#grml» .oO(mira ist einfach gut....) 23:22⎜«mikap:#grml» mirabilos: und dein bootloader ist geil :) 23:29⎜«mikap:#grml» und ich finds saugeil dass ich ein bsd zum booten mit grml hab, das muss ich dann gleich mal auf usb-stick installieren -- Michael Prokop über MirOS bsd4grml
