Dec 23, 2008
Never seen this before. This volume is about 50% full, total size 300GB. I tried defragging the file system with fsadm, but didn’t seem to help. I even unmounted it, mounted it somewhere else and immediately tried the resize again – still the same error. I know there are no open files on the file system.
server# vxresize -g rootdg perforce 285g
UX:vxfs fsadm: ERROR: V-3-20343: cannot shrink /dev/vx/rdsk/rootdg/perforce - blocks are currently in use.
VxVM vxresize ERROR V-5-1-7514 Problem running fsadm command for volume perforce, in diskgroup rootdg
I may have to backup/newfs/restore on this one. Too lazy to open a Symantec case because it’s not a big priority.
May 13, 2008
rm: cannot determine if this is an ancestor of the current working directory
This is caused by an underlying mount point permission that is too strict (700). You can change the permissions on the mount point without unmounting the volume by using lofs creatively:
#create temp directory
server1> mkdir -m 755 /fix-mnt
# mount the directory which contains the mount point, not the mount point itself, but its parent directory.
server1> mount -F lofs -o nosub /users/zones/server1-z3/root/users/ /fix-mnt
server1> ls -ld /fix-mnt/mountpoint #confirms the permssions are not 775
server1> chmod 775 /fix-mnt/mountpoint
server1> umount /fix-mnt
server1> rmdir /fix-mnt