VERITAS FILE SYSTEM FEATURES

-Intent Log (fast file recovery)

-Extend-based allocation
-Online administration (resize, defragmentation,backup with snapshots)
-Storage checkpoints
-Multi-volume file system support
-Smart Tier (Dynamic Storage Tiering)
-Improve database performance (Quik I/O, EXTENSION FOR odm)
-Performance Tuning
-Cross-platform data sharing
-ACLs
-Quotas
-File change log
-Smart Move feature
-Thin provisioning support
-File system data compresion
File system deduplication
-File replication
-Cluster File system
VxFS EXTEND-BASED ALLOCATION
Inode: A unique identifier for file
Block: Smallest amount of disk space allocated to a file
Extend: A set of contiguos blocks
VXFS IS A EXTENDED FS.
Two pieces of information form the basic of an extended are:
LENGHT
OFFSET
USING VxFS COMMANDS
PATH : /opt/VRTS/bin
MANPATH: /opt/VTRS/man
man command_vxfs
command [fstype] [generic_options] \
[-o VxFS_options] [special | mount_point]
ejem:
mount -t vxfs -r -o noatime /dev/vx/dsk/appdg/appvol/app
AIX=
location /opt/VTRSvxfs/bin
FS type switch: -V vxfs
Dirs: /usr/lib/fs/vxfs
/etc/fs/vxfs
Default FS file: /etc/vfs
HP-UX=
location /sbin/fs
FS type switch: -F vxfs
Default FS file: /etc/default/fs
LINUX=
location /usr/lib/fs/vxfs
FS type switch: -t vxfs
Dirs: /sbin/command.vxfs

Default FS file: /etc/default/fs

SOLARIS=
location command /opt/VTRSvxfs/bin
FS type switch: -F vxfs
Dirs: /usr/lib/fs/vxfs
/etc/fs/vxfs
Default FS file: /etc/default/fs
VxFS MKFS OPTIONS
Se puede usar para desplegar el bsize and logsize on a existing filesystem
-o N: Display how fs would be created
-m: Display how fs was created
-o version=n : Spaecifies layout version (7,8 and default is 9
-o bsize=n : Sets block size for files (only on create)
Valores validos:
1024 bytes (1k) (Filesystem menor o igual a 1TB)
8192 bytes (8k) (Filesystem mayor a un TB)
mount [-v]: Display mounted FS
mount -a : Mount all FS in file system table
mount -r or -ro: Mount read only
umount /mydata : Umount FS
umount -a : Umount all mounted FS
fstyp /dev/vx/dsk/datadg/datavol: Display FS type
df -h : Disply free space
MOUNTLOCK FEATURE
Protect against accidental file system unmount
Lock: mount fstype -o mntlock=ID block_device mount_point
Observe: mount | grep mntlock
Unlock:
AIX, SOlaris: umount -o mntunlock=ID mount_point
HP-UX, Linux: vxumount -o mntunlock=ID mount_point
UPGRADING THE FILE SYSTEM LAYOUT
Bettter performace use layout version 9
Upgrade:
vxupgrade [-n new_version] [-o noquota] \
[-r rawdev] mount_point
Display: vxupgrade /mnt
Exmp: vxupgrade -n 8 /mnt
LOGGING IN VxFS
INTENT LOG
1-The intent log records pending file system changes before metadata is changed
2-The intent log is written before file system updates are made
3-If the system crashes, the intent log is replaced by VxFS fsck
MAINTAINING VxFS CONSISTENCY
-Check FS consistency using intent log for the VxFS on the datavol volume:
fsck [fstype] /dev/vx/rdsk/appdg/appvol
-To perform a full check without using the intent log:

fsck [fstype] -o full,nolog /dev/vx/rdsk/appdg/appvol

-To perform a full check and report status at regular intervals:
fsck [fstype] -o full,status,interval=N \
/dev/vx/rdsk/appdg/appvol
-To check two file system un parallel using the intent log:
fsck [fstype] -o p /dev/vx/rdsk/oradg/oravol01 \
/dev/vx/rdsk/oradg/oravol02

FILE CHANGE LOG

Tracks changes to files and directories
Useful for utilities that traverse the directory structure
Location: mount_point/lost+fount/changelog
Off by default fcladm on | off
fcladm state mount_point
FILE SYSTEM FRAGMENTATION
-2 types (directory , extent(files))
To monitor directory fragmentation :
fsadm -D /mnt1
To monitor extent fragmentation:
fsadm -E /home
DEFRAGMENTING A FILE SYSTEM
Small files are made contiguos,
large files are built from large extends
fsadm [-de] [-DEH] [-t time] [-p passes] mount_point | -f dir
Extend:
fsadm -eEH /mnt1
fsadm -eEH -f /mnt1/largedir
Directory:
Directory are packet into the inode area,
before other files, entries are sorted by access time
fsadm -dDH /mnt1
FREE SPACE DEFRAGMENTATION FOR A FILE SYSTEM
Free space reorganization aims to create
biggger chunks of free space in the FS
- fsadm [fstype] -C [-v] mount_point
- df -os /mnt3
SCHEDULING DEFRAGMENTATION
-Depende on usage and activity patterns,
on demand, as a cron job, intervals based on reports
TESTING PERFORMANCE USING VXBENCH
Tools to create secuencial or random I/O trafic to test
vxbench_platform -w workload [option] filename
Sequencial write:
vxbench_platform -w write -i iosize=8, iocount=131072 /mnt/testfile01
Random write:
vxbench_platform -w rand_write -i \
iosize=8, iocount=131072, maxfilesize=1048576 /mnt/testfile01

THIN PROVISIONING
Solo ocupa en el arreglo el espacio
que contiene data, el arreglo debe ser compatible
vxdisk list
vxdisk -e list
vxdisk -o thin, fssize list
SMARTMOVE
2 BENEFITS OF SMARTMOVE ARE:
-FASTER PLEX CREATION
-REDUCE STORAGE REQUIREMENTS
On by default
Copiar data entre arreglos, no copia todo el lun solamente la data
se puede espejear un lun de 100gb con uno de 10gb si el de 100 solo tiene 8gb de
datos por ejemplo
Esto sucede porque el lune tiene comunicacion que el FS que le indica cuales blo
ques tiene data valida
vxdefault list (list parameteres can be set also use usefssmartmove)
To modify: vxdefault set tunable value
Non-default parameters stored in /etc/defaults/vxfs
MIGRATING TO THIN PROVISIONING USING SMART MOVE
1-Verify SmartMove turned on.
2-Add thin LUNs to disk group
3-Mirror volumens to thin LUNSs.
4-Test performance of new plexes
5-Remove original mirrors and LUNSs fron disk group
6-If necessary expand (if larger thin LUNs
RECLAIM STORAGE WITH THIN PROVISIONING
Reclaim disk space
By VxFS:
fsadm -R [-P] mount_point
By VxVM:
vxdisk reclaim disk|enclosure|diskgroup
AGRESSIVE RECLAMATION
fsadm -R [-o analyze | -A] mount_point
Compacts free space first for effective reclamation
AUTOMATIC RECLAMATION FOR VOLUMES
-Volume on thin reclaimable LUNs
-Volume deleted or shrunk -> Array disk space automatically reclaimed
Related parameters
-reclaim_on_deleted_wait_period
Default -> 1 day
-reclaim_on_deleted_start_time
Default -> 22:10
DEFAULT VxVM BEHAVIOR WITH THIN LUNs
-When disk group includes thin LUNs, mirrored
volumes are automatically created with
data change objects.
-Update to the original volume are recorded in
DCO logs stored on disk

-Resynchronization involves applying only

changed data, rather than performing an
entire atomic resynchronizarion