Thanks to Dr. Blinn, Satheesh.B., Prithwish Chatterjee, Jose A Fabregas,
and Michael James Bradford
Suggestions were (organized in a best practices order):
1) Verify that there is sufficient room after the volume is removed before
attempting to remove it. While the rmvol command should exit gracefully if
there is insufficient room, don't run the risk of problems by cutting it
too close.
2) Run the verify command against the file domain as there may be a problem
with the file domain. The file sets will all need to be unmounted for
verify to be able to examine the domain.
3) Defragment completely before trying to remove the volume.
4) A race condition may exist. Enter single-user mode and try removing the
volume.
5) Install the latest patch kits. At least one responder required specific
patches from support to correct the problems with the BMT.
6) Backup the filesets in the file domain, remove the file domain, recreate
the file domain, and restore the filesets.
In my case I followed steps 1,2, 3, and 4 which resulted in the volume
being successfully removed.
Original problem description
======================================================
I have an AdvFS volume. When attempting to remove an old disk after adding
two new disks I receive the following error:
rmvol: Removing volume '/dev/re0c' from domain 'domain_exe'
rmvol: Can't remove the volume
rmvol: Error = E_BMT_NOT_EMPTY (-1175)
rmvol: Can't remove volume '/dev/re0c' from domain 'domain_exe'
After looking at the archives I found a reference that said defragmenting
would resolve the problem. I tried this but it didn't resolve the problem.
Has anybody else encountered this error?
Best regards,
Jeffrey Hummel
Received on Thu Mar 14 2002 - 19:41:42 NZDT