| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
operate on one type of filesystem, mention this.
While here, capitalise the use of "UFS" in growfs.8 to match other uses of
the term in other man pages.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
the fragment, and write the full block. Reading less might not work
due to device sector size bigger then size of direntries in the
last directory fragment.
Reported by: bz
In collaboration with: pho
Reviewed by: jeff
Tested by: bz, pho
|
|
|
|
|
|
| |
Reviewed by: mckusick, pjd, pho
Tested by: pho
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
| |
Reported by: Mikolaj Golub <to.my.trociny@gmail.com>
- Only require 256k of blocks per-cg when trying to allocate contiguous
journal blocks. The storage may not actually be contiguous but is at
least within one cg.
- When disabling SUJ leave SU enabled and report this to the user. It
is expected that users will upgrade SU filesystems to SUJ and want
a similar downgrade path.
|
|
|
|
|
|
|
| |
Document -j switch in usage() to reflect recent SUJ work.
Submitted by: Alastair Hogge
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
structure so that we correctly reload. Note that tunefs doesn't
properly detect the need to reload if the disk device is specified
for a read-only mounted filesystem.
- Lessen the contiguity requirement for the journal so that it is more
likely to succeed.
|
|
|
|
| |
Reported by: Florian Smeets
|
|
|
|
|
|
|
|
| |
brings in support for an optional intent log which eliminates the need
for background fsck on unclean shutdown.
Sponsored by: iXsystems, Yahoo!, and Juniper.
With help from: McKusick and Peter Holm
|
| |
|
|
|
|
| |
Submitted by: Marius Nünnerich <marius@nuenneri.ch>
|
|
|
|
| |
Reviewed by: rwatson
|
|
|
|
|
|
| |
PR: docs/139705
Submitted by: Warren Block <wblock at wonkity dot com>
Approved by: imp (mentor, implicit)
|
|
|
|
| |
Submitted by: Ulrich Spörlein
|
|
|
|
| |
Reviewed by: pjd
|
|
|
|
|
|
| |
Pointed out by: ru
Approved by: re (bmah)
MFC after: 3 days
|
|
|
|
|
|
|
| |
filesystem on to make SU work.
Approved by: re (hrs)
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
support.
I left -j flag for UFS journal implementation which we may gain at some
point.
Sponsored by: home.pl
|
| |
|
| |
|
|
|
|
|
|
| |
per letter dated July 22, 1999.
Approved by: core, imp
|
|
|
|
| |
declarations, uncuddled elses and excessive braces).
|
|
|
|
| |
the getopt() case statement).
|
| |
|
|
|
|
| |
the build almost a year ago.
|
| |
|
| |
|
|
|
|
| |
Reviewed by: mckusick
|
|
|
|
|
| |
in the new world order of libufs, where we also do statfs, and add a missing
close.
|
| |
|
|
|
|
| |
things.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the old 8-bit fs_old_flags to the new location the first time that the
filesystem is mounted by a new kernel. One of the unused flags in
fs_old_flags is used to indicate that the flags have been moved.
Leave the fs_old_flags word intact so that it will work properly if
used on an old kernel.
Change the fs_sblockloc superblock location field to be in units
of bytes instead of in units of filesystem fragments. The old units
did not work properly when the fragment size exceeeded the superblock
size (8192). Update old fs_sblockloc values at the same time that
the flags are moved.
Suggested by: BOUWSMA Barry <freebsd-misuser@netscum.dyndns.dk>
Sponsored by: DARPA & NAI Labs.
|
|
|
|
| |
Reported by: dd
|
| |
|
|
|
|
|
|
|
| |
inspecting a superblock.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
|
|
|
|
|
|
|
|
| |
I introduced a style problem when I sorted 'a' before 'A'; our
preferred order sorts 'A' first. Correct.
Use .Cm instead of .Ar.
Submitted by: bde
|
|
|
|
|
|
|
|
| |
command, permitting it to set FS_ACLS and FS_MULTILABEL administrative
flags on UFS file systems.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
|
|
|
| |
Fixed other bugs in the usage message so that it matches the man page.
|
|
|
|
|
|
| |
anymore.
Sponsored by: DARPA & NAI Labs.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
filesystem is no more or less required for -n than for any other option.
The previous commit clarified the actual requirement.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
| |
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
|
|
|
|
|
|
| |
add FILES section.
PR: 34239
Submitted by: Gary W. Swearingen <swear@blarg.net>
|