Hello everyone,
so I noticed a new bug has been reported in both #guix IRC channel and on debbugs (#77086). This bug reports that filesystems are not unmounted cleanly on reboot. So I wanted to raise my concern that there isn't really a bug which would make guix write zeros to files, but that it's a corruption of files steming from the filesystems not being unmounted cleanly. I cannot really find anything that would make this explanation implausible in this thread. Am I missing something? Were you guys somehow able to actually *verify* it's guix writing zeros and not the files getting corrupted afterwards? If you reconfigure and then reboot right after, I think it's feasible some of the data might not be written to the disk yet, and this is the way most folks do it. If there isn't currently a way to rule out this concern, I think best course of action would be to get a reproducer for this guix writing zeros if it's possible. I am not sure if you kept the incorrect guix on your disks or removed everything in which case it's probably impossible to get a reproducer. Moreover if you remember that you got fsck, then I would treat the cause being corrupted files by not properly unmounting as more likely than the current explanation that guix is somehow writing empty files. Regards, Rutherther
