It is not actual summary, but workaround instead. Casper Dik points me out that Solaris have no limits for mount points and i must dig somewhere else. But as i wrote all possible reasons are not actual - mount points was not busy, disks was not mounted. Meanwhile i've noticed that two new volumes mounted without problems at all. Quick-and-dirt solution - i've removed all "not mountable" mount points and recreated them. Problem vanished. Hell it knows what it was, but now all works fine. Original question follows. ==== Original question ==== Hi all. Operating environment: SunOS XXXXX 5.7 Generic_106541-19 sun4u sparc SUNW,Ultra-Enterprise Veritas Volume Manager: VERSION: 3.2,REV=08.15.2001.23.27 Total mount points: 26 9 vxfs filesystems mounted on volumes under vxvm control. All vxvm volumes are in one diskgroup physically placed on T3+ diskgroups connected via JNI adapters. All was fine until adding two new volumes ( on one disk/lun ) and two other luns. Now we have 28 mounts, 11 from them are vxfs mounts. Volumes created without problems, vxfs filesystems mounted, snapstart performs ideally. But during snapshot, snapshot itself and fsck snapvolumes passed ok, but parallel mount ( mount -a ) this new 11 filesystems ( mount -a ) fails with error: UX:vxfs mount: ERROR: /dev/vx/dsk/XXXXXXdg/SNAPvolumeXX is already mounted, /snapmount/mountpoint is busy, allowable number of mount points exceeded Mountpoints NOT busy. Snapvolumes DOES NOT already mounted. Manual mount of single snapshot volume fails with same error. Thanks in advance for any help in this matter. -- Sergey Tsyganenko <tsyganenko@vectis.ru> _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Fri Mar 14 02:07:37 2003
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:05 EST