login
Header Space

 
 

dragonflybsd-kernel mailing list

FromSubjectsort iconDate
Matthew Dillon
Re: HAMMER filesystem update - design document
Yes and no. The reason it isn't quite the same is that RAID storage has no ability to recovery corruption generated by the filesystem code itself or corruption caused by other parts of the kernel or by hardware snafus which occur prior to the data getting onto the platter. When you do logical replication, however, the possibility of this sort of corruption seeping into all the replicated copies is greatly reduced and the replicated copies can check against each other t...
Oct 10, 9:14 pm 2007
Matthew Dillon
Re: HAMMER filesystem update - design document
No, it isn't a volume manager, it's simply that the filesystem can be made up of multiple volumes. Each cluster (say, a 256M chunk) is integrated into the filesystem-wide B-Tree and can only be addressed by its parent or by the parent pointers of its children. This means that clusters can be migrated with minimal work and thus can be migrated while the filesystem is live. We don't have the situation such as we have in UFS where random inodes in the filesystem directly ...
Oct 10, 6:38 pm 2007
Thomas E. Spanjaard
Re: HAMMER filesystem update - design document
This is the functional equivalent of a RAID1, and that is all HAMMER provides; the point of RAIDZ (and RAID3,4,5,6,etc) is that you don't need 2n bytes worth of disk for n bytes worth of usable storage, yet keeping some level of resilience. There is something to be said for this kind of scheme, namely not wasting as much disk space, but in the case of RAID1,0,10,01, moving that to a different layer (e.g. Vinum) is good enough. In a clustering environment, it's not likely that you'll want an...
Oct 10, 7:45 pm 2007
Gergo Szakal
Re: HAMMER filesystem update - design document
I am asking some questions from the user's point of view. Sorry if it is covered in the document, I may have overlooked it. So, the filesystem is going to be the volume manager as well (like in ZFS), right? Will filesystems strictly be bounded to 'partitions' or 'slices'? Another question: will this mirroring capability allow for an FS-level RAID like RAIDZ? I wonder whether the filesystem can be extended so it can achieve this. Disclaimer: yes, those are ZFS features which I am asking about, ...
Oct 10, 6:00 pm 2007
Matthew Dillon
Re: HAMMER filesystem update - design document
I get a good 8 hours of sleep. As I get older I find myself unable to pull all-nighters any more without really screwing up the entire next day. -- ZFS serves a different purpose and I think it is cool, but as time has progressed I find myself liking ZFS's design methodology less and less, and I am very glad I decided against trying to port it. I do not think it is a good idea to put all one's marbles in a single copy of a filesystem, no matter how redun...
Oct 10, 5:25 pm 2007
Bill Hacker
Re: HAMMER filesystem update - design document
As *I* have gotten older 'day' has become virtualized anyway. Partly 'coz I spend half the year on Washington DC's timezone and half on Hong Kong's timezone and work nights anyway 'coz that's when the cable modems are at their Dunno about Slowlaris, but from what is passing by on 7-CURRENT, despite Pawel's excellent work, it 'seems to me' that ZFS is more fragile at the OS & RAM resource level than even yesteryear's storage media was/is at the hardware level. I can't put a lot of faith ...
Oct 10, 6:36 pm 2007
Matthew Dillon
HAMMER filesystem update - design document
Ok, here's the final design document that I am now implementing. Again, I expect most or all of these features to be ready and the filesystem to be beta-quality by the December release. Hammer Filesystem (I) General Storage Abstraction HAMMER uses a basic 16K filesystem buffer for all I/O. Buffers are collected into clusters, cluster are collected into volumes, and a single HAMMER filesystem may span multiple volumes. HAMMER maintains a small hinted r...
Oct 10, 3:33 pm 2007
Michael Neumann
Re: HAMMER filesystem update - design document
Interesting. What exactly are those database files used for? Is a database file attached to each file to store ACLs, for example? Or can it be used like btree(3)? Do they have their own namespace in the filesystem? Wow! I a am really looking forward to try out HAMMER!!! Regards, Michael
Oct 10, 7:12 pm 2007
Bill Hacker
Re: HAMMER filesystem update - design document
*snip* Matt, Awesome! Tells me: "ZFS, bend over, grab your ankles and kiss your an(atomy) 'Goodbye'" From the amount of work that has HAD to go into this, it also tells me you are: A) probably single, or soon will be and B) don't sleep much anyway! ;-) Looking forward to a 'test drive'... Bill Hacker
Oct 10, 4:30 pm 2007
Matthew Dillon
HAMMER filesystem update
I am going to start committing bits and pieces of the HAMMER filesystem over the next two months. Note that the filesystem will not be operational until we get closer to the 2.0 release in December so these bits and pieces will not be tied into buildworld/buildkernel until then. I am making good progress and I believe it will be beta quality by the release. It took nearly the whole year to come up with a workable design. I thought I had it at the beginning of the ...
Oct 10, 2:41 pm 2007
previous daytodaynext day
October 9, 2007October 10, 2007October 11, 2007
speck-geostationary