To determine if the filesytem was created using the "-T" option
1. Create a new UFS filessytem.
# newfs/dev/vx/rdsk/test/vol1
newfs:construct a new file system /dev/vx/rdsk/test/vol1: (y/n)? y
/dev/vx/rdsk/test/vol1:204800 sectors in 100 cylinders of 32 tracks, 64 sectors
100.0MB in 7cyl groups (16 c/g, 16.00MB/g, 7680 i/g)
super-blockbackups (for fsck -F ufs -o b=#) at:
32, 32864,65696, 98528, 131360, 164192, 197024,
2. Check the parameters that the UFS filesytem was created with:
#/usr/sbin/mkfs -F ufs -m /dev/vx/rdsk/test/vol1
mkfs -F ufs-onsect=64,ntrack=32,bsize=8192,fragsize=1024,cgsize=16,free=10,rps=120,nbpi=2060,opt=t,apc=0,gap=0,nrpos=8,maxcontig=128/dev/vx/rdsk/test/vol1 204800
Where the fragsize=1024 and it does not equal bsize=8192 , therefore the filesytem was NOT created with the "-T" filesystem
3. Repeating the process with "-T" we get:
# newfs -T/dev/vx/rdsk/test/vol1
newfs:construct a new file system /dev/vx/rdsk/test/vol1: (y/n)? y
/dev/vx/rdsk/test/vol1:204800 sectors in 100 cylinders of 32 tracks, 64 sectors
100.0MB in 1cyl groups (215 c/g, 215.00MB/g, 256 i/g)
super-blockbackups (for fsck -F ufs -o b=#) at: 32,
4. Check using"-m" option we get:
# mkfs -Fufs -m /dev/vx/rdsk/test/vol1
mkfs -F ufs-onsect=64,ntrack=32,bsize=8192,fragsize=8192,cgsize=215,free=10,rps=120,nbpi=1162499,opt=t,apc=0,gap=0,nrpos=8,maxcontig=128/dev/vx/rdsk/test/vol1 204800
where fragsize=bsize=8192 and the nbpi=1162499 and hence the -T option has been used.
To conclude, when creating a new UFS filesystem originally smaller than 1TB you must use the -T option with newfs to ensure the filesystem can extended greater than 1TB when required.
# newfs -T/dev/vx/rdsk/test/vol1