Procedure
- Log in to the client host, instead of the storage system, using an SSH tool, enter the mount command, and locate the corresponding file system by the mount point of the client.
NOTE: /fs200 on indicates that /mnt/test2 is mounted to file system fs200 on the storage array. - Use an SSH tool, such as Xshell 5 or later, PuTTY 0.63 or later, or SecureCRT 6.7 or later, to connect to the management network port of the storage device. Log in to the CLI of the storage device.
NOTE: By default, user name admin and password Admin@storage are used to log in to the SSH tool.
- Run the show upgrade package command to view the names of all controllers.
NOTE: Name indicates the controller name. The following figure shows controller 0A and controller 0B. - Log in to the storage system using an SSH tool. In the admin view, run the show file_system general command to locate ID corresponding to file system.
NOTE: ID corresponding to the file system fs200 is 200. - In the admin view of the storage system, run the change user_modecurrent_mode user_mode=developer command to go to the developer view.
- Determine whether to clear lock resources of the file system on the controller.
- If yes, go to 6.a.
- If no, no further action is required.
NOTICE: Perform steps by following R&D engineers' instructions.- Run the clear nfs nfsv3_lock file_system_id=<ID> controller=<Name> command to delete the lock resources of the file system on the controller.
NOTE: ID indicates the file system ID. Name indicates the controller name.
Clear the lock resources of corresponding controllers based on the controller names.
- Collect related information and contact technical support engineers.