I had a similar experience with `btrfs check --repair` a few years ago, and with an MS-DOS antivirus program called VSAFE, and there was the infamous Linux 2.1.44.
File systems are fragile by their very nature. The last thing we need is for some yolobot to go full bull-in-china-shop on the file system's source code while the human-allegedly-in-the-loop takes a snooze.
LisPi (npub1326…gzqx) amenome (npub1smq…kqn5)