1.\" Copyright (c) 2007 The DragonFly Project. All rights reserved. 2.\" 3.\" This code is derived from software contributed to The DragonFly Project 4.\" by Matthew Dillon <dillon@backplane.com> 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 10.\" 1. Redistributions of source code must retain the above copyright 11.\" notice, this list of conditions and the following disclaimer. 12.\" 2. Redistributions in binary form must reproduce the above copyright 13.\" notice, this list of conditions and the following disclaimer in 14.\" the documentation and/or other materials provided with the 15.\" distribution. 16.\" 3. Neither the name of The DragonFly Project nor the names of its 17.\" contributors may be used to endorse or promote products derived 18.\" from this software without specific, prior written permission. 19.\" 20.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 21.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 22.\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS 23.\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE 24.\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 25.\" INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES (INCLUDING, 26.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 27.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED 28.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, 29.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT 30.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 31.\" SUCH DAMAGE. 32.\" 33.\" $DragonFly: src/sbin/newfs_hammer/newfs_hammer.8,v 1.1 2007/10/10 19:35:53 dillon Exp $ 34.Dd September 10, 2007 35.Dt NEWFS_HAMMER 8 36.Os 37.Sh NAME 38.Nm newfs_hammer 39.Nd construct a new HAMMER file system 40.Sh SYNOPSIS 41.Nm 42.Fl L Ar label 43.Op Fl S Ar segment 44.Op Fl U Ar uuid 45.Ar special 46.Op special... 47.Sh DESCRIPTION 48The 49.Nm 50utility creates a HAMMER filesystem on device 51.Ar special . 52If multiple devices are specified a single HAMMER filesystem is created 53which spans all of them. HAMMER filesystems are sector-size agnostic, 54however the 55.DX 56implementation requires the sector size to be no larger then 16K. 57HAMMER filesystems start at a relative offset of 0 and may only be created 58under out-of-band disk labels (disklabel64 or gpt labels), or in standard 59disklabel partitions which do not overlap the label area. 60.Pp 61The options are as follow: 62.Bl -tag -width indent 63.It Fl L Ar label 64All HAMMER filesystems must be named and names should be unique on a 65per-machine basis. 66.It Fl U Ar uuid 67All HAMMER filesystems are assigned a globally unique UUID. If no UUID 68is specified one will be synthesized. 69.It Fl S Ar segsize 70HAMMER organizes file objects in segments. Segments default to the maximum 712G size but a smaller size may be chosen if desired. This option is not 72recommended. HAMMER will still use all available disk space regardless. 73.El 74.Sh NOTES 75.Sh EXAMPLES 76.Bd -literal -offset indent 77newfs_hammer -L Home /dev/ad0s1d 78.Ed 79.Pp 80Create a file system named 'Home' on 81.Pa /dev/ad0s1d . 82.Sh DIAGNOSTICS 83Exit status is 0 on success and 1 on error. 84.Sh SEE ALSO 85.Xr disklabel 8 , 86.Xr fdisk 8 , 87.Xr newfs 8 88.Sh HISTORY 89The 90.Nm 91utility first appeared in 92.Dx 2.0 . 93.Sh AUTHORS 94.An Matthew Dillon Aq dillon@backplane.com . 95