From: Georgette, Danielle (Danielle.Georgette@det.nsw.edu.au)
Date: Mon Feb 04 2008 - 18:54:29 EST
Jim Ownes hit the nail on the head, changing the link name to be the
same as the underlying volume name was the first suggestion I tried and
it worked. I was a little dubious about trying it while the domain was
active and the fileset mounted but it has worked like a charm. The
volume is now removed from the domain. We have different names for a few
volumes in their advfs directories and I guess we had never struck this
problem before as we very rarely addvol and rmvol from these domains.
Thank you everyone for your suggestions, I'm attaching them to the
summary for others to try in future:
Jim Owens:
I suspect the utilities (balance and rmvol) have a dependency on the
name convention in /etc/fdmns that the kernel does not require:
lrwxrwxrwx 1 root system 30 May 17 2007 ltc01dg.ltc_vdump.01 ->
/dev/vol/ltc01dg/ltcvdumpvol01
Try:
# cd /etc/fdmns/vdump_dom
# rm ltc01dg.ltc_vdump.01
# ln -s /dev/vol/ltc01dg/ltcvdumpvol01 ltc01dg.ltcvdumpvol01
so the short name matches the real name.
from Johan Brusche:
You could try by giving volume on dsk18c the same transfer size:
/sbin/chvol -r 512 -w 512 /dev/disk/dsk18c vdump_dom
Then move the AdvFS logging to dsk18:
/sbin/advfs/switchlog vdump_dom 2
And maybe also
/sbin/chvol -A \
/dev/vol/ltc01dg/ltcvdumpvol01 vdump_dom
in case the volume was disabled due to a previous unsuccessfull rmvol
command.
**********************************************************************
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:37 EDT