Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Detect additional corrupt journal cases #69
I ran into a case of a busted journal transaction (due to the filesystem filling up...), which prevented kestrel from starting up. It manifested as a
So there are 2 fixes here:
In my case there wasn't really an old-style-CMD_ADD in the journal I'd imagine, and probably just some null bytes being misinterpreted. I guess this isn't alarming, since probably all bets are off if the filesystem fills up, though it's not obvious to me how that would lead to null bytes at that spot in the journal.