1c85e6a35d
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> |
||
|---|---|---|
| .. | ||
| bridge | ||
| build | ||
| dial | ||
| doc/src | ||
| floppy.tree/etc | ||
| help | ||
| isp | ||
| mfs_tree | ||
| net | ||
| router | ||
| tinyware | ||
| README.html | ||
| Version | ||
<html> <body> <h1><b><center> PicoBSD Development Kit </center></b></h1> <p>All documentation, instructions, list of supported hardware and FAQ are in doc/ directory. If they are missing, go to the doc/src/ subdirectory and do a 'make'. The docs are marked with HTML tags, but we try to keep them readable even without a browser. <p>Please start from <A HREF="doc/intro.html">here</a> for general description of the project and its features, or just go directly <A HREF="doc/how2build.html">here</a> for detailed instructions on how to build your version of PicoBSD. <p>Enjoy!</p> <! $FreeBSD$ > </body> </html>