summaryrefslogtreecommitdiffstats
path: root/sbin/newfs/newfs.8
Commit message (Collapse)AuthorAgeFilesLines
* MFC r287396:trasz2016-01-111-1/+1
| | | | | | | | | | | It's 2015, and some people are still trying to use fdisk and then go asking what debug flags to set for GEOM to make it work. Advice them to use gpart(8) instead. Something similar should probably done with disklabel, but I need to rewrite the disklabel examples first. Sponsored by: The FreeBSD Foundation
* Sweep man pages replacing ad -> ada.pluknet2013-10-011-3/+3
| | | | | | Approved by: re (blackend) MFC after: 1 week X-MFC note: stable/9 only
* Remove contractions.joel2013-04-111-1/+1
|
* The purpose of this change to the FFS layout policy is to reduce themckusick2013-03-221-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | running time for a full fsck. It also reduces the random access time for large files and speeds the traversal time for directory tree walks. The key idea is to reserve a small area in each cylinder group immediately following the inode blocks for the use of metadata, specifically indirect blocks and directory contents. The new policy is to preferentially place metadata in the metadata area and everything else in the blocks that follow the metadata area. The size of this area can be set when creating a filesystem using newfs(8) or changed in an existing filesystem using tunefs(8). Both utilities use the `-k held-for-metadata-blocks' option to specify the amount of space to be held for metadata blocks in each cylinder group. By default, newfs(8) sets this area to half of minfree (typically 4% of the data area). This work was inspired by a paper presented at Usenix's FAST '13: www.usenix.org/conference/fast13/ffsck-fast-file-system-checker Details of this implementation appears in the April 2013 of ;login: www.usenix.org/publications/login/april-2013-volume-38-number-2. A copy of the April 2013 ;login: paper can also be downloaded from: www.mckusick.com/publications/faster_fsck.pdf. Reviewed by: kib Tested by: Peter Holm MFC after: 4 weeks
* Advertise growfs(8) a little better.trasz2011-06-221-1/+2
|
* Update the manual page to reflect the new 32K/4K defaults.mckusick2011-05-281-4/+4
| | | | Reminded by: Ivan Voras
* Xref makefs(8).jh2011-02-221-1/+2
| | | | | PR: 154708 Submitted by: jhs
* Add the -j option to enable soft updates journaling when creatingmckusick2011-02-161-1/+7
| | | | | | a new file system. Reviewed by: Kostik Belousov <kostikbel@gmail.com>
* Add support for FS_TRIM to user-mode UFS utilities.kib2010-12-291-2/+10
| | | | | | Reviewed by: mckusick, pjd, pho Tested by: pho MFC after: 1 month
* Synchronize newfs(8) manual with code.gjb2010-09-141-3/+4
| | | | | | | | PR: 61716 Submitted by: Radim Kolar <hsn at netmag cz> Patch by: arundel Approved by: keramida (mentor) MFC after: 1 week
* Rewording and typo fixes in newfs(8).gjb2010-09-121-3/+3
| | | | | | | | PR: 150490 Submitted by: Eitan Adler <foreignuser at eitanadler com> Additional fixes by: Warren Block <wblock at wonkity com>, keramida Approved by: keramida (mentor) MFC after: 1 week
* Fix "Empty input line" mdoc warning.sobomax2010-03-101-2/+2
| | | | Submitted by: Alexander Best
* Slightly improve gjournal documentation.trasz2009-04-291-0/+4
| | | | Reviewed by: pjd
* Enable operation of newfs on plain files, which is useful when youluigi2008-12-031-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | want to prepare disk images for emulators (though 'makefs' in port can do something similar). This relies on: + minor changes to pass the consistency checks even when working on a file; + an additional option, '-p partition' , to specify the disk partition to initialize; + some changes on the I/O routines to deal with partition offsets. The latter was a bit tricky to implement, see the details in newfs.h: in newfs, I/O is done through libufs which assumes that the file descriptor refers to the whole partition. Introducing support for the offset in libufs would require a non-backward compatible change in the library, to be dealt with a version bump or with symbol versioning. I felt both approaches to be overkill for this specific application, especially because there might be other changes to libufs that might become necessary in the near future. So I used the following trick: - read access is always done by calling bread() directly, so we just add the offset in the (few) places that call bread(); - write access is done through bwrite() and sbwrite(), which in turn calls bwrite(). To avoid rewriting sbwrite(), we supply our own version of bwrite() here, which takes precedence over the version in libufs. MFC after: 4 weeks
* Replace reference from vinum.8 to gvinum.8, it was advised in the PR toremko2008-03-211-2/+2
| | | | | | | | | | replace this with vinum.4, but that's the kernel interface manual, which is not appropriate in my understanding. I think that gvinum is a suitable replacement for this. PR: docs/121938 Submitted by: "Federico" <federicogalvezdurand at yahoo dot com> MFC after: 3 days
* Rename the undocumented -E option to -X.phk2007-12-161-5/+9
| | | | | | | | | | Implement -E option which will erase the filesystem sectors before making the new filesystem. Reserved space in front of the superblock (bootcode) is not erased. NB: Erasing can take as long time as writing every sector sequentially. This is relevant for all flash based disks which use wearlevelling.
* MFp4:yar2007-11-281-3/+21
| | | | | | | | | | | | | | | | | | | | | | Add a new option to newfs(8), -r, to specify reserved space at the end of the device. It can be useful, e.g., when the device is to become a member of a gmirror array later w/o losing the file system on it. Document the new option in the manpage. While I'm here, improve error handling for -s option, which is syntactically similar to -r; and document the fact that -s0 selects the default fs size explicitly, which can be useful, e.g., in a menu-based wrapper around newfs(8) requiring some value be entered for the fs size. Also fix a small typo in the help line for -s (missing space). Idea and initial implementation by: marck Discussed on: -fs Critical review by: bde Tested with: cmp(1)
* Add -J flag to both newfs(8) and tunefs(8) which allows to enable gjournalpjd2006-10-311-1/+3
| | | | | | | | support. I left -j flag for UFS journal implementation which we may gain at some point. Sponsored by: home.pl
* Polish previous revision:ru2005-01-221-6/+12
| | | | | | - Bump document date. - Spell "file system" properly. - Add missing markup bits.
* Add an option to suppress the creation of the .snap directory inwes2005-01-211-1/+16
| | | | | | | | the new filesystem. This is intended for memory and vnode filesystems that will never be fsck'ed or dumped. Obtained from: St. Bernard Software RAPID MFC after: 2 weeks
* Assorted markup, grammar, and spelling fixes.ru2004-05-171-3/+3
|
* Remove advertising clause from University of California Regent's license,markm2004-04-091-4/+0
| | | | | | per letter dated July 22, 1999. Approved by: core, imp
* Add a "-l" flag to newfs, which sets the FS_MULTILABEL flag. Thisrwatson2004-02-261-1/+3
| | | | | | | | permits users of newfs to set the multilabel flag on UFS1 and UFS2 file systems from inception without using tunefs. Obtained from: TrustedBSD Project Sponsored by: DARPA, McAfee Research
* s/disklabel/bsdlabel where needed.blackend2003-10-111-2/+2
|
* Remove an unneccessary comma.ceri2003-09-141-1/+1
|
* mdoc(7): Use the new feature of the .In macro.ru2003-09-081-1/+1
|
* Remove reference to diskpart(8)brueffer2003-04-201-1/+0
| | | | | PR: 51193 Submitted by: Yonatan@xpert.com
* Throw the switch--change to UFS2 as our default file system format forrwatson2003-04-201-1/+1
| | | | | | | | | | | | | | | | | | | | FreeBSD 5.1-RELEASE and later: - newfs(8) will now create UFS2 file systems unless UFS1 is specifically requested (-O1). To do this, I just twiddled the Oflag default. - sysinstall(8) will now select UFS2 as the default layout for new file systems unless specifically requested (use '1' and '2' to change the file system layout in the disk labeler). To do this, I inverted the ufs2 flag into a ufs1 flag, since ufs2 is now the default and ufs1 is the edge case. There's a slight semantic change in the key behavior: '2' no longer toggles, it changes the selection to UFS2. This is very similar to a patch David O'Brien sent me at one point, and that I couldn't find. Approved by: re (telecon) Reviewed by: mckusick, phk, bmah
* mdoc(7) police: markup laundry.ru2003-02-231-3/+3
|
* Our first keyword hit for apropos ufs2.jwd2003-02-191-1/+1
|
* Bring in support for volume labels to the filesystem utilities.gordon2003-02-011-0/+3
| | | | Reviewed by: mckusick
* Fix some 'SYNOPSIS' and 'usage' messages.trhodes2002-08-271-2/+2
|
* s/filesystem/file system/g as discussed on -developerstrhodes2002-08-211-25/+25
|
* mdoc(7) police: Consistently name options' arguments in the SYNOPSIS and ↵ru2002-08-131-16/+23
| | | | DESCRIPTION sections..
* The .Nm utilitycharnier2002-07-061-6/+9
|
* This commit adds basic support for the UFS2 filesystem. The UFS2mckusick2002-06-211-17/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | filesystem expands the inode to 256 bytes to make space for 64-bit block pointers. It also adds a file-creation time field, an ability to use jumbo blocks per inode to allow extent like pointer density, and space for extended attributes (up to twice the filesystem block size worth of attributes, e.g., on a 16K filesystem, there is space for 32K of attributes). UFS2 fully supports and runs existing UFS1 filesystems. New filesystems built using newfs can be built in either UFS1 or UFS2 format using the -O option. In this commit UFS1 is the default format, so if you want to build UFS2 format filesystems, you must specify -O 2. This default will be changed to UFS2 when UFS2 proves itself to be stable. In this commit the boot code for reading UFS2 filesystems is not compiled (see /sys/boot/common/ufsread.c) as there is insufficient space in the boot block. Once the size of the boot block is increased, this code can be defined. Things to note: the definition of SBSIZE has changed to SBLOCKSIZE. The header file <ufs/ufs/dinode.h> must be included before <ufs/ffs/fs.h> so as to get the definitions of ufs2_daddr_t and ufs_lbn_t. Still TODO: Verify that the first level bootstraps work for all the architectures. Convert the utility ffsinfo to understand UFS2 and test growfs. Add support for the extended attribute storage. Update soft updates to ensure integrity of extended attribute storage. Switch the current extended attribute interfaces to use the extended attribute storage. Add the extent like functionality (framework is there, but is currently never used). Sponsored by: DARPA & NAI Labs. Reviewed by: Poul-Henning Kamp <phk@freebsd.org>
* more file system > filesystemtrhodes2002-05-161-16/+16
|
* Remove the -v option, it is now default behaviour.phk2002-04-241-7/+0
| | | | Sponsored by: DARPA & NAI Labs
* Swing the axe and remove some archaic features from newfs which modernphk2002-03-201-82/+3
| | | | | | | | | | | | | | | | | | | diskdrives do neither need nor want: -O create a 4.3BSD format filesystem -d rotational delay between contiguous blocks -k sector 0 skew, per track -l hardware sector interleave -n number of distinguished rotational positions -p spare sectors per track -r revolutions/minute -t tracks/cylinder -x spare sectors per cylinder No change in the produced filesystem image unless one or more of these options were used. Approved by: mckusick
* Update the default newfs block and fragment sizes from 8192/1024 tosheldonh2001-12-111-5/+9
| | | | | | | | | | | | | | | | | | | 16384/2048. Following recent discussions on the -arch mailing list, involving dillon and mckusick, this change parallels the one made over a decade ago when the default was bumped up from 4096/512. This should provide significant performance improvements for most folks, less significant performance losses for a few folks and wasted space lost to large fragments for many folks. For discussion, please see the following thread in the -arch archive: Subject: Using a larger block size on large filesystems The discussion ceases to be relevant when the issue of partitioning schemes is raised.
* Fix typo: 'fragement' -> 'fragment'sheldonh2001-12-071-1/+1
|
* Fix the example of suggested default settings. It stated that settingssheldonh2001-11-271-1/+1
| | | | | | were only of benefit to large filesystems, which recent research suggests is not the case, and which the original author of the text no longer endorses.
* Correct the example introduced in rev 1.29, which suggested a block:fragsheldonh2001-11-271-4/+4
| | | | | | | | | | | size ratio other than 8:1. Currently, we only recommend an 8:1 ratio, because the impact of others ratios has not been adequately investigated. Also, do not recommend the use of the -c option in the example, since newfs now automatically calculates the best cyl:cylgrp ratio. This change was discussed with the author of rev 1.29.
* Document the optimal block:fragment ratio, per discussiondougb2001-10-151-0/+3
| | | | | | on -arch and cvs-all. Reviewed by: dillon
* Following the discussion in -arch and the submission of a patch by bde, hereroberto2001-10-041-6/+4
| | | | | | | it is. I added the manpage change. Submitted by: bde MFC after: 1 week
* Remove whitespace at EOL.dd2001-07-151-7/+7
|
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-101-1/+1
|
* mdoc(7) police: remove extraneous .Pp before and/or after .Sh.dd2001-07-091-2/+0
|
* Remove all references to MFS.dd2001-05-291-92/+2
|
* Add information about the new options to newfs and tunefs which set thenik2001-04-101-0/+6
| | | | | expected average file size and number of files per directory. Could do with some fleshing out.
OpenPOWER on IntegriCloud