| This reads something between cluless/malicious and genius. Crosses several red lights with a car, smashes the car, rebuilds the car with AI, tells people to cross red lights Keeps repeating btrfs check --repair . This command is dangerous and warned anywhere as a last resort: if you try to execute it you get a warning; the documentation has a warning; any guide from google tell you not to run it unless all else fails; chatgpt/lechat do not metion it, or note it as last resort. So not sure why he keeps repeating it without any note > Use these tools ONLY if btrfs check --repair segfaults, enters an infinite loop, or leaves the filesystem in worse shape than before. > Timeline of events ... First repair attempts. btrfs check --repair The guy is recommending people brick their volumes permanently as first resort without any warning Between using a dup profile and this I would not be surprised a btrfs dev just disregarding all as slop > Pool only mounts with rescue=all,ro, fails to mount RW Also this is important, the data was not lost. Even though read-only I don't think I would run this code. Still it would be interesting a btrs dev to have look and comment if there is any value in the code generated. As it would be definitely interesting being able to repair more issues in the pool safely inplace |