| |||||||||||||
The 2006 Linux File Systems WorkshopThe 2006 Linux File Systems WorkshopPosted Jul 6, 2006 9:57 UTC (Thu) by nix (subscriber, #2304)In reply to: The 2006 Linux File Systems Workshop by cventers Parent article: The 2006 Linux File Systems Workshop
Does reiser4 even try to solve any of the nasty problems Val mentions (the fsck crunch, the need for internal integrity checks, et al)?
As far as I can tell it doesn't. It used to have nice support for small files, but that got turned off because it impacted benchmarks and I don't know if it was ever turned on again.
(Log in to post comments)
reiser4 Posted Jul 7, 2006 1:48 UTC (Fri) by xoddam (subscriber, #2322) [Link] One thing mentioned in the article which reiser4 does implement (thoughVal 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.
|
|||||||||||||