Icelander here, I'm more concerned how well does this house work in icelandic conditions? Does it handle earthquakes well? What about regular storms? Being wet for months end? Constant freezing and thawing? Can you put it in an active volcano? Does if float on magma? There are lot of questions here!

While I'm not really concerned about it, I doubt that it would live up to Danish building regulations. I'm mean we pressure test our homes... then install ventilation systems because living in a house that can parse the pressure test would be unhealthy. We then continue to get headaches and stuffed noses because the ventilation systems aren't any good either.

Anyway, it doesn't look like this house would fit the required amount of isolation.

Only briefly.

If you built a boat from SiC attached to enormous heat sinks radiating into empty space, it would float for longer.

But air-conditioning expense makes it cost-prohibitive.

Magma is pretty dense (it's molten rocks, after all), so many things float on magma.

Very interesting discussion on the subject :

http://www.wired.com/2012/01/can-you-walk-on-lava-falling-in...

Just leaving this here, side project comic strip http://www.commitstrip.com/wp-content/uploads/2014/11/Strip-...

Well, we used it for storage backend for VMs few years back.

For some reasons it usually failed on high load, resulting in bad split-brains, extremely slow IO and loss of data. Very bad. We contacted Red Hat regarding that and got comments that gluster was not VM ready yet. We ditched gluster and went for plane proven old iSCSI.

This. We had the same failure mode, on a cluster with dozens of nodes and thousands of VMs.

http://thr3ads.net/gluster-users/2011/06/480298-Enomaly-user...

This bug (and others) would happen when moving files and/or folders over top of existing ones, ie:

  mkdir -p foo/bar/baz && \

  mkdir -p foo/bar/tmp && \

  touch foo/bar/baz/file foo/bar/tmp/file && \

  mv foo/bar/tmp/file foo/bar/baz/ && \

  rm -rf foo/bar/tmp

This was a method to replace an existing lockfile. Mercurial uses some similar code. The expected behavior would be that foo/bar/tmp/file replaced /foo/bar/baz/file. Instead, the outcome was that there was a race in Gluster where it got confused about which version of 'file' was correct, and it would end up with a split brain between the two nodes. This would be exacerbated by a node failure, but didn't always require one. Heavy load seemed to make the failure more likely. We couldn't replicate the same bug moving files in the same folder, it was the subfolders in the same gluster fs that seemed to cause the issue. The frustrating part was how gluster pointed fingers at the file operation being incompatible, despite advertising a posix compatible filesystem. Apparently the bug is fixed, but we moved off gluster, never to return.

Also, filesystems are hard, I get it, so no hard feelings :)

I look at the k as a algebric constant, i.e. SI prefix http://en.wikipedia.org/wiki/SI_prefix#List_of_prefixes

so 2k8 is 2000 +8,

2k1da3 would be 2013