The remove command removes a resource from the vfiler, but does not delete the resource. The volume or qtree goes back to vfiler0, the physical filer. However, in this case, I suspect the vfiler owns the volume... vfiler status -a will show that... if so, then you can't remove a qtree if the volume is already assigned. To remove the qtree, do it from a cifs or nfs client and delete the directory (qtree). There is also an advanced mode on the filer to do this but that would be best with support on the phone since we can't talk about unsupported features...but ok to say there is a way to do it (most netapp se's know the method if an empty qtee to delete from the filer).
vfiler0 owns vol/vol0/qtree0 vfiler1 owns vol/vol1/qtree1 * vfiler0 owns qtree0 and can delete it * vfiler0 does not own qtree1 and cannot delete it * vfiler1 owns qtree1 and can delete it * vfiler1 does not own qtree0 and cannot delete it
When you add /vol/vol0/qtree0' to filer1, vfiler0 no longer owns qtree0 and should not be able to delete it. vfiler1 is also not able to delete qtree0 because the qtree resides in vol0, which is not accessible by vfiler1 and vfiler0 owns it.