login
Header Space

 
 

dragonflybsd-kernel mailing list

FromSubjectsort iconDate
Matthew Dillon
Re: HAMMER Update
Bleh, I meant to say 'background process' not 'backup ground process'. -Matt Matthew Dillon <dillon@backplane.com>
Nov 5, 6:05 pm 2007
Matthew Dillon
Re: HAMMER Update
HAMMER has an independant B-Tree for each cluster. The clusters are then glued together (leaf -> new cluster root) to form a unified B-Tree. Except for lookups and no-free-space cases, B-Tree operations are local to a cluster. A cluster in HAMMER is around 64MB and can have up to 4096 records. If a cluster needs to be recovered, HAMMER will simply throw away the B-Tree and regenerate it from scratch using the cluster's record list. This way all B-Tre...
Nov 5, 4:27 pm 2007
Dmitri Nikulin
Re: HAMMER Update
Speaking of on-disk B-Trees, ReiserFS' biggest problems are all based on its use of flexible B-Trees. For instance, the difficulty of correctly rebuilding the tree if a node is damaged, and correctly detecting if a ReiserFS system is hosted on a file in another (supposedly damaged) ReiserFS system, are noted as big problems that are supposedly solved for Reiser4. Are there likely to be similar issues in Hammer for the time being, or have you already planned far ahead for these cases with extra info...
Nov 5, 1:26 am 2007
previous daytodaynext day
November 4, 2007November 5, 2007November 6, 2007
speck-geostationary