hibernation

If your defragmenter knows about the hibernation system, it will update the 'pointer' to the hibernation file.

Such an OS would be foolish if it wouldn't write the current location of the hibernation file whenever it went into hibernation.

Then there is the swap space and hibernation image which if you have a lot of ram is enormous.

Also, if you are using Windows 8.0 onwards disabling hibernation will also disable the fast startup feature.

Managed apps (package managed installs, one click install/update/uninstall) plus seamless app hibernation and resumption are overall a big win for usability.

Interstellar seemed to suggest use of a similar method when the astronauts were in hibernation.

So, this only is a problem if you hibernate your system, defragment its disk on another system using a defragmenter that doesn't know about hibernation files, and then try to wake up from hibernation.

Ability to run multiple Virtual machines, a working hibernation feature in commonly used operating systems and popularization of Distributed version control systems...

The flaw here would be a scenario where there are deliberate repeated modifications to blocks of the harddrive (somewhere like within hibernation/wake code).

OSX also reserves space for the hibernation image, so it shouldn't get fragmented.

If it can load a config file, it can also load FS drivers or hibernation files, and prepare the actual kernel boot more subtlety.

Maybe at low temperatures though, 250 years is a short hibernation.

I reckon this to be conceptually similar to the concept of "hibernation" in modern computers; during hibernation, the operating system saves the contents of its virtual memory (physical plus any swapped/paged memory) to non-volatile storage, then reloads that saved state on the next boot.

Hibernation can stay enabled, it just dumps RAM contents into a file, once.