Veritas Filesystem

http://www.datadisk.co.uk/html_docs/veritas/veritas_file_system.htm

Veritas File System

Veritas Filesystem ( VxFS) is an extent based, intent logging file system. VxFS is geared toward Unix environments that require high performance and availability and deal with large amounts of data. VxFS features: Extent based allocation Extent attributes Fast filesystem recovery Access control lists (ACL) Online administration Online backup Enchanced I/O and mount options Improved synchronous writes Support for large filesystems (up to 2 terabytes) Support for large files (up to 1 terabytes) Veritas quicklog Version 4 disk Layout The VxFS version 4 disk layout divides the entire file system space into fixed sized allocation units. The first allocation unit starts at block zero and all allocation units 32K blocks. All structural information are contained in files. So expanding the filesystem structures simply requires extending the appropriate structural files. All version 4 structural files reside in the structural fileset. The structural files in version 4 disk layout are:
Contains the object location table (OLT). The OLT, which referenced from the superblock is used to locate the other structural files.

Object location Table file

Label File

Encapsulates the super-block and super-block replicas. Although the primary location of the super-block is known, the label file can be used to locate upper-block copies ifthere is structural damage to the filesystem.

Device File

Records device information such as volume length and volume label and contains pointers to other structural files.

Fileset Header File

Hold information on a per- fileset basis. This may include the inode of the filesets inode list file, the maximum number of inodes allowed, an indication of whether the filesystem supports large files and the inode number of quotas file if the filesetsupports quotas. When a filesystem is created, there are two filesets, the structural fileset, whichdefines the file system structure and the primary fileset which contains user data.

Inode List File

Both the structural fileset and the primary fileset have their own inode lists which are stored in inode list files. Increasing the number of inodes involves increasing the size of the file after expanding the inode allocation unit file.

Inode Allocation Unit File Log File

Hold the free inode map, extended operations map and a summary of the inode resources. Maps the block used by the filesystem intent log. Indicates the allocation state of each AU by defining whether each AU is free allocated as a whole (no bitmaps allocated) or expanded, in which case the bitmaps associated with each AU determine which extents are allocated.

Extent Allocation Unit State File

1 of 3

27/09/2011 11:04

Veritas Filesystem

http://www.datadisk.co.uk/html_docs/veritas/veritas_file_system.htm

Extent Allocation Unit Summary File Free Extent Map File Quotas File

Contains the AU summary for each allocation unit, which contains the number of free extents of each size. The summary for an extent is created only when an allocation unit is expanded for use. Contains the free extent maps for each of the allocation units. If the filesystem supports quotas, there is a quotas file, which is used to track the resources allocated to each user.

Creating a Filesystem The mkfs command creates veritas filesystems by writing to a special character device.
mkfs F vxfs o largefiles /dev/vx/rdsk/appdg/samba_vol mkfs [-F vxfs] [ generic_option] [-o special_option] device [size] Options common to other filesystem types Options specific to VxFS filesystem disk device or Veritas volume the size in sectors

Create

generic_option special_option device size

Mounting/ Unmounting a Filesystem

Mount a VXFS filesystem Umount a VXFS filesystem
mount F vxfs o largefiles /dev/vx/rdsk/appdg/samba_vol /samba umount /samba

Displaying a Filesystem
mount -v mount -p mkfs -F vxfs -n N <filesystem> mkfs -F vxfs -m <character device>

Information

How created

Identifying Filesystem types

fstyp -v /dev/vx/dsk/appdg/samba_vol fstyp -v /dev/vx/rdsk/appdg/samba_vol (block device) (raw device)

Identify filesystem type

Shrink/grow a Filesystem
Shrink a filesystem Grow a filesystem
/usr/lib/vxfs/fsadm -b 102400 /samba /usr/lib/vxfs/fsadm -b 204800 /samba

Reorganise a Filesystem Use the fsadm ro reorganise (defrag) a filesystem:

Report on extent fragmentation: Report on directory fragmentation: Reorganise extents: Reorganise directories:
/usr/lib/fs/vxfs/fsadm -E /samba /usr/lib/fs/vxfs/fsadm -D /samba /usr/lib/fs/vxfs/fsadm -e /samba /usr/lib/fs/vxfs/fsadm -d /samba

Create and Mount a snapshot filesystem Use the mount command to create the snap shot filesystem then use vxdump (or tar, dd, cpio) to backup the filesystem to tape:

2 of 3

27/09/2011 11:04

Veritas Filesystem

http://www.datadisk.co.uk/html_docs/veritas/veritas_file_system.htm

Create the snapshot filesystem: Backup the filesystem: Restore the filesystem (to /restore filesystem):

mount -F vxfs -o snapof=/dev/vx/dsk/appdg/samba_vol snap,size=208400 \ /dev/vx/dsk/rootdg/snapshot/snapshot vxdump -cf /dev/rmt/1cbn /snapshot vxrestore -vx /restore

Using quotas
Turn on a quota for a filesystem (make sure filesystem vxquotaon <mount_point> has been mounted with quota option): Note: a file will be created called quotas (it's a text file) To setup a users quota To view a users quota:
vxedquota <username> vxquota -v <username> vxquotaoff <mount_point>

To turn off quota on a filesystem:

Note: The quota file is not removed.

VxFS consistancy
Full check Two f/s in parallel
fsck -F vxfs -o full,nolog <volume> fsck -F vxfs -o p <raw-device>,raw-device>

Intent Log The intent log is uded to speed up recovery

Create Mount
fsadm -F vxfs -o log=size,logdevice=<device> mount -F vxfs -o log mount -F vxfs -o delaylog (integrity) (performance)

3 of 3

27/09/2011 11:04