Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
Slashdot Deals: Deal of the Day - 6 month subscription of Pandora One at 46% off. ×

Comment Re:New study shows... (Score 1) 428

Wow, you are so wrong. The human body (and our microbial friends in our stomachs) are extremely good at digesting food. For any reasonable amount of food, KJ in = KJ stored + KJ expended.

It doesn't matter if it's fruit or Coke, you keep those calories. Plus, there is more energy in a banana than in the same weight of Coke.

Comment Re:ZFS is nice... (Score 2) 279

One GREAT advantage it has over your bog-standards filesystems like NTFS and ext4 is its copy-on-write architecture, and the essentially free and near-instant snapshot system it provides.

When you take a snapshot of a filesystem, it simply makes a copy of the superblock. All of the space on the devices remain marked as in-use, and both snapshots share exactly the same physical storage.

When you make a change to one of the snapshots, it simply writes the changed blocks to a different location on the underlying devices and leaves the still-in-use original block alone.

Comment Re:ZFS is nice... (Score 1) 279

This is completely correct. By having knowledge of all layers, ZFS is able to easily offer features that other systems don't.

One of my favourites what happens when you set a filesystem to keep two copies of a file. Instead of placing the second copy on a random device determined by the RAID layer, it will attempt to ensure that all blocks from one device are placed on the adjacent device.

The advantage of that is non-obvious at first glance, but what it means is this: When two devices in the JBOD fail, instead of corrupting all the files when *any* two devices fail, it means you will only have corruption when two *adjacent* drives fail.

In a 5-device JBOD, that means the chance of corruption when the second device fails drops from ~100% to 25%.

Comment Where have I heard this before? (Score 5, Insightful) 255

So with this API stuff, what you are proposing is that all systems should be divided up into functional blocks, where every block has a single logical purpose, and that savvy users are able to chain these functions together however they see fit to suit their purposes?

Where have I heard this idea before? Oh yeah... it's called The Unix Philosophy.

"Old age and treachery will beat youth and skill every time." -- a coffee cup