Each month, we will introduce a disaster scenario and accept
submissions of recovery procedures from them. For examples of good
disasters, see my O'Reilly article
here.
If you're new to UML, you'll probably want to read the following pages
before starting to solve this month's problem:
This month's disaster involves a trashed filesystem. To create the
disaster, boot up UML with a COW-ed or copied root filesystem, and
zero out the root filesystem's superblock:
You can try running halt, but it probably won't work, so shut it down
with the mconsole instead:
(debian) sysrq u
OK
(debian) halt
OK
Your mission, should you choose to accept it, is to restore this
filesystem to health.
Submit your solution
If you have a solution to this month's problem and you want it to be
immortalized on this very site, submit it here.
I will pick one or more winning solutions based on criteria such as
originality - all else being equal, I like non-obvious solutions
subtlety - if applicable, small fixes are better than big ones
brevity - short and sweet is better than long and involved
parsimony - the fewer external resources you need, the better
Propose a disaster
If you have a scenario which you think would make a good Disaster of
the Month, please submit it here. If you have a good solution,
include it as well. Disasters which have actually happened in real
life are especially good, but anything which can happen on a physical
box is fine.
Each month, I will look over the submissions and choose an interesting
one to feature as that month's disaster of the month.