| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
| |
It does not help modern compilers, and some may take some hit from it.
(I also found several functions that listed *every* of its 10 local vars with
"register" -- just how many free registers do people think machines have?)
|
|
|
|
|
|
|
|
|
| |
open "/dev/stdout". This doesn't actually affect growfs, but does affect
ffsinfo, permitting ffsinfo to output to the shell's stdout rather than
requiring it be dumped to a file or explicitly pointed at a special
device.
Reviewed by: peter
|
|
|
|
|
| |
PR: docs/34918
Submitted by: Harry Newton <harry_newton@telinco.co.uk>
|
| |
|
|
|
|
|
|
| |
Binary builds that cannot handle this must explicitly set WARNS=0.
Reviewed by: mike
|
| |
|
| |
|
|
|
|
|
|
| |
Submitted by: Chris Boltwood <chris@hiendmedia.com>
Reviewed by: tomsoft
MFC after: 5 days
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
and yes now it also works on alpha
Reviewed by: chm
MFC after: 3 weeks
|
|
|
|
|
|
|
| |
in an unclean filesystem after growing by a large amount of cylinder
groups
Reviewed by: chm
|
|
|
|
| |
- MAN[1-9] -> MAN.
|
| |
|
|
|
|
|
| |
Submitted by: ru
Reviewed by: chm
|
| |
|
|
|
|
|
|
|
|
|
|
| |
check a couple of mallocs
usage of errx
linebreaks of DBG_ macros,
correcting the usage of nroff macros
Submitted by: grog, charnier
Reviewed by: chm
|
|
Reviewed by: grog
|