Most of us, at this point are use to building fileystems with UFS. However Veritas offers the Veritas File System. A journaling filesystem with performance advantage over UFS. My favorite use of VxFS, however, is that very large filesystems can be created very quickly. This is because... well, I'll finish that later, but you don't have to wait minutes or hours sometimes to let the inode tables build. There are some special ways of working with VxFS, however. The two situations are in building filesystems, and fsck'ing filesystems. This is how you should do it:
a) Building a VxFS Filesystem:
/usr/lib/fs/vxfs/mkfs -F vxfs -o largefiles /dev/vx/rdsk/exampledg/vol01
-Sample Output:
version 4 layout
35363560 sectors, 4420445 blocks of size 4096, log size 256 blocks
unlimited inodes, largefiles supported
4420445 data blocks, 4419853 free data blocks
135 allocation units of 32768 blocks, 32768 data blocks
last allocation unit has 29533 data blocks
b) FSCK'ing a VxFS Filesystem:
fsck -F vxfs -o full,nolog /dev/vx/rdsk/exampledg/vol01
-Sample Output:
pass0 - checking structural files
pass1 - checking inode sanity and blocks
pass2 - checking directory linkage
pass3 - checking reference counts
pass4 - checking resource maps
OK to clear log? (ynq)y
set state to CLEAN? (ynq)y
-Note: You can _try_ using fsck with just the -F option, and ditching
the full,nolog options, but if you think the FS might really
be messed up you need 'em. Without them fsck will do something
like this:
# fsck -F vxfs /dev/vx/rdsk/prod6gr/saveusr
file system is clean - log replay is not required |