Re: 20TB Storage System

From: Geoff Buckingham (geoffb_at_chuggalug.clues.com)
Date: 09/03/03

  • Next message: Petre Bandac: "simicq 0.8.3 cannot be built from ports && openoffice" 
    Date: Wed, 3 Sep 2003 11:06:15 +0000
To: Max Clark <max.clark@media.net>

    On Tue, Sep 02, 2003 at 03:53:53PM -0700, Max Clark wrote:
    > Depends on whether you plan on crashing or not :) According to
    > http://lists.freebsd.org/pipermail/freebsd-fs/2003-July/000181.html,
    > you may not want to create filesystems over 3TB if you want fsck to
    > succeed. I don't know if that's using the default newfs settings
    > (which would create an insane number of inodes), though.
    >
    > - This is a big problem (no pun intended), my smallest requirement is still
    > 5TB... what would you recommend? The smallest file on the storage will be
    > 500MB.
    >
    If you files are all going this large I imagine you should look carefully at
    what you do with inodes, block and cluster sizes

    However I just read the newfs man page and am intrigued to know what effect
    the -g and -h options have....

         -g avgfilesize
                 The expected average file size for the file system.

         -h avgfpdir
                 The expected average number of files per directory on the file
                 system.

    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"

  • Next message: Petre Bandac: "simicq 0.8.3 cannot be built from ports && openoffice"

    Relevant Pages

    • Re: 20TB Storage System
      ... > you may not want to create filesystems over 3TB if you want fsck to ... I don't know if that's using the default newfs settings ... > (which would create an insane number of inodes), ...
      (freebsd-hackers)
    • Re: 20TB Storage System
      ... > you may not want to create filesystems over 3TB if you want fsck to ... I don't know if that's using the default newfs settings ... > (which would create an insane number of inodes), ...
      (freebsd-performance)
    • Re: New 1.4T SVM UFS fs does not have enough inodes
      ... Dougii wrote: ... filesystems with lots of inodes take a long time to fsck. ... to get a little extra usable space by making fewer inodes. ... One problem with this many inodes is that fsck will use a *LOT* of RAM ...
      (comp.unix.solaris)
    • [PATCH 0/3] i_ino uniqueness: alternate approach -- hash the inodes
      ... Since there's been no further comment on these patches, ... clean up the other filesystems and ensure that they properly hash their ... Since Joern mentioned that he thought that hashing the inodes might be simpler ... trivially fix this by making the static counters in new_inode and iunique ...
      (Linux-Kernel)
    • [PATCH 0/3] i_ino uniqueness: alternate approach -- hash the inodes
      ... Resending this set of patches to the list per Al Viro's request. ... Since Joern mentioned that he thought that hashing the inodes might be simpler ... We can't do anything for filesystems that have ... trivially fix this by making the static counters in new_inode and iunique ...
      (Linux-Kernel)