Timeline for A standard way of dealing with a system crash / freeze
Current License: CC BY-SA 2.5
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 28, 2010 at 22:09 | comment | added | Gordon Davisson | Journalling doesn't work by rewinding, it actually does more the opposite: it completes whatever file operations were in process when the computer crashed. | |
| Oct 26, 2010 at 8:12 | vote | accept | Julian Wergieluk | ||
| Oct 25, 2010 at 21:24 | comment | added | Julian Wergieluk | I bought a new MacBookPro last thursday, and I already had a system freeze three times. Two of them while copying data from an external hard disk and one after a system update.. not a very lucky start :( But you are right Gordon: with journaling a file system should be able to rewind to the last working state. | |
| Oct 25, 2010 at 19:35 | comment | added | Gordon Davisson | Recent versions of OS X use file system journalling by default, which means the file system can almost always heal itself after a crash. Mind you, this does nothing to protect the contents of open files... | |
| Oct 25, 2010 at 18:29 | comment | added | Philip Regan | I've never had a problem with the file system upon killing the power to a Mac ever. I've had open files get corrupted, but I save early and often, so it's been a long, long time since that has last happened. | |
| Oct 25, 2010 at 18:20 | comment | added | Julian Wergieluk | I must admit, this is a bit surprising. Isn't the use of the power button dangerous? Again, on Linux it's usually the wost thing you can do, resulting eventually in a corrupted file system. Thanks! | |
| Oct 25, 2010 at 17:51 | history | answered | Philip Regan | CC BY-SA 2.5 |