reiser4
Posted Jul 7, 2006 1:48 UTC (Fri) by
xoddam (subscriber, #2322)
In reply to:
The 2006 Linux File Systems Workshop by nix
Parent article:
The 2006 Linux File Systems Workshop
One thing mentioned in the article which reiser4 does implement (though
Val doesn't include it in her list of examples) is copy-on-write atomic
storage hierarchy updates -- depending on settings, changing an inode can
result in allocation of new copies of the block containing the inode and,
recursively, every parent block which references the change, right up to
the master block. The old versions are only freed once the root has been
'committed' to its canonical location.
(
Log in to post comments)
