Hitting Inode Limits

Matthew Dillon dillon at apollo.backplane.com
Fri Aug 14 08:47:02 PDT 2009

    Its a good test for HAMMER anyhow.  The more people who use HAMMER in
    different ways the better.

    The hardlink mechanic will not be optimal, take care as the disk fills
    up to limit the number of automatic snapshots so you can actually
    recover space when removing directory trees.

    I'm not sure if you are using a nohistory mount or not.  With a nohistory
    mount snapshots basically don't work but space will be recovered
    directly by 'rm'.  Even so, due to the hardlink mechanic you are using,
    the space will be severely fragmented and might not recover as much
    as hoped so running a regular hammer cleanup (it should happen
    automatically from cron) will still be necessary.

    One additional benefit:  The hardlink counter in the HAMMER inode
    is a 64 bit field, so unlike UFS it is not possible to hit a
    hardlink limit on a file.  In previous years I often hit the hardlink
    limit on UFS for CVS/* files when using the hardlink mechanic for
    backups because CVS itself hardlinks those files too.


More information about the Users mailing list