World Library  
Flag as Inappropriate
Email this Article

Hammer

Article Id: WHEBN0021115562
Reproduction Date:

Title: Hammer  
Author: World Heritage Encyclopedia
Language: English
Subject: Punch (tool), Axe, Vampire film, Hephaestus, War hammer
Collection: 2008 Software, Distributed File Systems
Publisher: World Heritage Encyclopedia
Publication
Date:
 

Hammer

HAMMER
Developer Matthew Dillon
Full name HAMMER
Introduced July 21, 2008 (DragonFly BSD 2.0[1])
Structures
Directory contents B+ tree[2]
Limits
Max. volume size 1 EiB[2]
Features
Forks no
File system permissions UNIX permissions
Data deduplication on demand
Other
Supported operating systems DragonFly BSD

HAMMER is a high-availability 64-bit file system developed by Matthew Dillon for DragonFly BSD using B-trees. Its major features include infinite NFS-exportable snapshots, master-multislave operation, configurable history retention, fsckless-mount, and checksums to deal with data corruption.[3] HAMMER also supports data block deduplication, meaning that identical data blocks will be stored only once on a file system.[4]

A port of HAMMER to Linux has been started that supports read-only access.[5]

Contents

  • Features 1
  • Limitations 2
  • Performance 3
  • Development 4
  • See also 5
  • References 6
  • External links 7

Features

HAMMER file system provides configurable fine-grained and coarse-grained filesystem histories with online snapshots availability. Up to 65536 master (read-write) and slave (read-only) pseudo-filesystems (PFSs), with independent individual retention parameters and inode numbering, may be created for each file system; PFS may be mirrored to multiple slaves both locally or over network connection with near real-time performance. No file system checking is required on remount.[3][6][7][8]

HAMMER supports volumes up to 1 EiB of storage capacity. File system supports CRC checksumming of data and metadata, online layout correction and data deduplication, and dynamic inodes allocation with effectively unlimited number of inodes.[6][9][10]

Limitations

Currently, regular maintenance is required for keeping file system clean and regaining space after file deletions. By default, a cron job is performing necessary actions on DragonFly BSD daily. HAMMER also does not support multi-master configurations yet.[6][8]

Performance

The following performance-related improvements were introduced on July 2011:[11]

  • Increased disk read speed in certain scenarios by implementing pulse-width modulated time-domain multiplexer on B-Tree cursor operation
  • Removed a deadlock stalling issue
  • Improved read performance during heavy, concurrent file write operations

Development

It was developed specifically for DragonFly BSD to provide a feature-rich yet better designed analogue of then increasingly popular ZFS.

As of June 2014, HAMMER2 file system is actively developed by Matthew Dillon, who initially planned to bring it up to minimal working state by July 2012 and ship the final version in 2013.[12] During Google Summer of Code 2013 Daniel Flores implemented compression in HAMMER2 using LZ4 and ZLIB algorithms.[13] On June 4, 2014 DragonFly 3.8.0 was released featuring support for HAMMER2, although the file system was said to be not ready for use.[14]

See also

References

  1. ^ Larabel, Michael (2011-01-07). "Can DragonFlyBSD's HAMMER Compete With Btrfs, ZFS?".  
  2. ^ a b  
  3. ^ a b  – DragonFly File Formats Manual
  4. ^ Sherrill, Justin (2010-11-07). "Deduplication arrives". Retrieved 2011-11-28. 
  5. ^ Lorch, Daniel. "Porting the HAMMER File System to Linux". Retrieved 2011-11-28. 
  6. ^ a b c "HAMMER".  
  7. ^ Vervloesem, Koen (2010-04-21). "DragonFly BSD 2.6: towards a free clustering operating system".  
  8. ^ a b George, Siju (May 2014). "Working with Hammer File System and PFSes".  
  9. ^  – DragonFly System Maintenance and Operation Commands Manual
  10. ^ Kemp, Juliet (2008-08-04). "Tip of the Trade: Dragonfly BSD and the Hammer Filesystem". ServerWatch. Retrieved 2014-05-26. 
  11. ^ Dillon, Matthew (2011-07-22). "git: HAMMER VFS - Add code to reduce frontend vs flusher locking conflicts". commits mailing list. http://leaf.dragonflybsd.org/mailarchive/commits/2011-07/msg00086.html.
  12. ^ Dillon, Matthew (2012-02-08). "DESIGN document for HAMMER2 (08-Feb-2012 update)". users mailing list. http://leaf.dragonflybsd.org/mailarchive/users/2012-02/msg00020.html.
  13. ^ "Block compression feature in HAMMER2".  
  14. ^ "DragonFly Release 3.8".  

External links

This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 


Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.