Reasons why @_behindthesofa went down #15:
@FiloSottile mounted a corrupted SD card and the OpenBSD kernel panickedpic.twitter.com/HJRY9Ev1LG
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
computerrrrss arrre badddd 
If a filesystem is in such inconsistent state that the kernel can't proceed, better panic then carry on like normal..
I would rather a mount + ls action not implode a system though. Give me a error return. Anything but a panic
You want userland applications to have to deal with a filesystem that is corrupted in unpredictable ways?
If it got to the point where it knew it was time to panic. It likely could have also just returned a error code and aborted. Saving the sys
Ideally, but if the filesystem is marked clean, but actually dirty for some reason (hw failure? forced?), then panic fails closed.
Unmounting also fails closed but doesn’t kill the rest of the system. Also not marked clean, mounted ro.
So you'd rather the kernel force unmount /, /usr, or /home? No way. This code was written long before removable media..
I'd rather logical fs implementation be factored such that corrupt or malicious underlying fs doesn't violate invariants or force panic...
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.