2 ms·
You missed the other two common ones: permissions change and a disk filled up somewhere. Before finding out the dead simple failure mode and fix, engineers nee
by mattbrewsbytes 4y ago
You missed the other two common ones: permissions change and a disk filled up somewhere.
Before finding out the dead simple failure mode and fix, engineers need to spend countless hours diving into the most technically complex scenarios that might be happening but are irrelevant. Then they can reset permissions or add disk space or add back a DNS entry.
- bombcar 4y agoReminds me of the old sysadmin who always made a file 10% the size of the disk named .root-emergency or similar. Disk filled up? Delete the file, get some breathing time, fix the problem, recreate the file.
- buggeryorkshire 4y agoIsn't that what ext filesystems on Linux do? IIRC the reserved portion is 5% which can be dropped if you need some headroom.
- yamtaddle 4y agoYeah, the root-reserved blocks are tunable. Won't save you if someone's running-as-root reporting job goes rogue and fills up the disk, though, while the file might... I mean, obviously one ought not have done that in the first place, but the real world is a whole thing.
- bombcar 4y agoYep. Often a system crash is caused by logging, which often logs ... as root.
- throwaway81523 4y agoTry SCE to AUX.