Re: Is there the equivalent of a Windows "fast format" for UFS?

On Fri, Dec 4, 2009 at 2:23 PM, Peter Steele <psteele@xxxxxxxxxxxxx> wrote:
I suspect I know the answer to this question but I'll ask it anyway. We're dealing with some very large disks (11TB raid array) and a newfs operation takes a significant time. Is there any way to get a volume formatted faster than the typical newfs does?


It's actually the other way around - there is only "fast" format for
UFS. As far as I know, full format for FAT or NTFS also checks for bad
sectors on the drive, so that's why Windows has that distinction.

What you need to do is properly configure block/frag sizes and inode
density. Figure out the average file size that will be stored on the
volume and divide the total volume size by that number. That is the
minimum number of inodes you should create, since one inode is
required per file. Of course, you should aim higher since you will not
be able to add more inodes without reformatting the system.

Increasing block and fragment sizes may also help, depending on what
type of files you are storing. Read tuning(7) and then newfs(8) for
options -b, -f, and -i.

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

Relevant Pages

  • [2.6 patch] ALSA core: misc cleanups
    ... or a negative error code on failure or if the ... * @format: the format to check ... -int snd_pcm_open(struct inode *inode, struct file *file) ... +static int snd_pcm_release ...
    (Linux-Kernel)
  • Re: 2.6.24-rc2-mm1 -- mkfs failing on variety of fs types
    ... Fragment size=4096 ... First data block=0 ... Writing inode tables: ... Guessing about desired format.. ...
    (Linux-Kernel)
  • Re: LVextend
    ... When you run ext2resize it sets up the inode table and superblocks. ... Sent from my iPhone ... when we format first LV1 it make inode table for 200M. ... The extend process covers ...
    (RedHat)
  • Re: Corrupt XFS -Filesystems on new Hardware and Kernel
    ... tell you the inode numbers that are bad. ... bad format 0 for inode 8458341 type 0100000 ... agno = 0 ... would clear inode number in entry at offset 152... ...
    (Linux-Kernel)
  • Re: [2.6.7-BK] NTFS 2.1.13 patch 8/8
    ... NTFS: 2.1.13 - Enable overwriting of resident files and housekeeping of system files. ... until the inode is unlocked before returning it and it never gets ... Skip the mft record if it is not in use. ...
    (Linux-Kernel)