i often see a few lines (0-10) of orphaned inodes and stuff like that. nothing dramatic, and certainly nothing that demands user feedback.but i think the `recovering journal` part is an unambigous indication that the fs was not cleanly unmounted.
To throw my hat into the ring with this,, I can confirm I've been seeing the same for a while now (past 3-ish months?) I have a laptop that doesn't exhibit this behavior that is a bit out of date, and one that does. Something I can look into doing when I have some time is incrementally updating the "old" laptop to try and find the commit that introduced this behavior. Most of the time, this is not an issue and just causes a delay while booting while fsck cleans the filesystem. However, I have had an instance where my store did get corrupted, necessitating `guix gc --verify=contents,repair` to be ran and causing multiple store items to be deemed invalid. -- Best, Ryan
signature.asc
Description: PGP signature
