Alternate method to remove SRT in LOCKED_WRITE state
# bmrsrtadm
Select one of the following options:
1. Create a new Shared Resource Tree.
2. Create a new CD image based Shared Resource Tree.
3. Copy an existing Shared Resource Tree to a new location.
4. Import a Shared Resource Tree.
5. Modify an existing Shared Resource Tree.
6. Delete an existing Shared Resource Tree.
7. List Shared Resource Trees available on this server.
8. Quit.
Enter your selection (1-8) [1] : 7
Name State Type Path Description
------------- ------------ ---- ------------------------------ --------------------
linuxRH67 LOCKED_WRITE NFS /nbu_bmr/SRT/linuxRH67 Redhat Linux 6.7
Select one of the following options:
1. Create a new Shared Resource Tree.
2. Create a new CD image based Shared Resource Tree.
3. Copy an existing Shared Resource Tree to a new location.
4. Import a Shared Resource Tree.
5. Modify an existing Shared Resource Tree.
6. Delete an existing Shared Resource Tree.
7. List Shared Resource Trees available on this server.
8. Quit.
Enter your selection (1-8) [1] : 6
Enter the name of an existing SRT : linuxRH67
That SRT is in use and cannot be deleted until its lock is released.
Select one of the following options:
1. Create a new Shared Resource Tree.
2. Create a new CD image based Shared Resource Tree.
3. Copy an existing Shared Resource Tree to a new location.
4. Import a Shared Resource Tree.
5. Modify an existing Shared Resource Tree.
6. Delete an existing Shared Resource Tree.
7. List Shared Resource Trees available on this server.
8. Quit.
Enter your selection (1-8) [1] : 5
Enter the name of an existing SRT : linuxRH67
The SRT you selected is in a LOCKED state. This typically means
that the SRT is busy, and you should wait for it to come unlocked
before you continue.
Would you like to wait for the SRT to come free? (y/n) [y] : n
If you are ABSOLUTELY SURE nobody is using this SRT and this is a stale
lock, you may choose to break the lock and continue.
If you break the lock while somebody is using the SRT, you may corrupt
the SRT.
Are you ABSOLUTELY SURE you want to break the lock and continue? (y/n) [n] : y
The SRT lock has been broken and the SRT has been placed into a DAMAGED
state. Next, SRT recovery will be attempted. If recovery is
successful you will be able to use this SRT. If recovery fails you
probably will have to delete this SRT and create a new one
Working ...Segmentation fault (core dumped)
# ls -l
drwxr-xr-x 14 root root 4096 Jul 13 10:45 linuxRH67
# mv linuxRH67 linuxRH67.old
# bmrsrtadm
Select one of the following options:
1. Create a new Shared Resource Tree.
2. Create a new CD image based Shared Resource Tree.
3. Copy an existing Shared Resource Tree to a new location.
4. Import a Shared Resource Tree.
5. Modify an existing Shared Resource Tree.
6. Delete an existing Shared Resource Tree.
7. List Shared Resource Trees available on this server.
8. Quit.
Enter your selection (1-8) [1] : 7
Name State Type Path Description
------------- ------------ ---- ------------------------------ --------------------
linuxRH67 LOCKED_WRITE NFS /nbu_bmr/SRT/linuxRH67 Redhat Linux 6.7
Select one of the following options:
1. Create a new Shared Resource Tree.
2. Create a new CD image based Shared Resource Tree.
3. Copy an existing Shared Resource Tree to a new location.
4. Import a Shared Resource Tree.
5. Modify an existing Shared Resource Tree.
6. Delete an existing Shared Resource Tree.
7. List Shared Resource Trees available on this server.
8. Quit.
Enter your selection (1-8) [1] : 5
Enter the name of an existing SRT : linuxRH67
The SRT you selected is in a LOCKED state. This typically means
that the SRT is busy, and you should wait for it to come unlocked
before you continue.
Would you like to wait for the SRT to come free? (y/n) [y] : n
If you are ABSOLUTELY SURE nobody is using this SRT and this is a stale
lock, you may choose to break the lock and continue.
If you break the lock while somebody is using the SRT, you may corrupt
the SRT.
Are you ABSOLUTELY SURE you want to break the lock and continue? (y/n) [n] : y
The SRT lock has been broken and the SRT has been placed into a DAMAGED
state. Next, SRT recovery will be attempted. If recovery is
successful you will be able to use this SRT. If recovery fails you
probably will have to delete this SRT and create a new one
V-125-3 mkdir(/nbu_bmr/SRT/linuxRH67/isolinux,0755) failed: No such file or directory
V-125-39 caught exception: runtime error in srtPlat.cpp:DoMkdir()
[Error] V-125-267 Cannot prepare boot files for this SRT.
You may choose either to leave this SRT on the server in its current state,
or to delete it.
Do you want to delete this SRT from the server? (y/n) : y
Removing SRT "linuxRH67" from server -- please stand by ...
# bmrsrtadm
Select one of the following options:
1. Create a new Shared Resource Tree.
2. Create a new CD image based Shared Resource Tree.
3. Copy an existing Shared Resource Tree to a new location.
4. Import a Shared Resource Tree.
5. Modify an existing Shared Resource Tree.
6. Delete an existing Shared Resource Tree.
7. List Shared Resource Trees available on this server.
8. Quit.
Enter your selection (1-8) [1] : 7
Name State Type Path Description
------------- ----- ---- ------------------------------ --------------------
Select one of the following options:
1. Create a new Shared Resource Tree.
2. Create a new CD image based Shared Resource Tree.
3. Copy an existing Shared Resource Tree to a new location.
4. Import a Shared Resource Tree.
5. Modify an existing Shared Resource Tree.
6. Delete an existing Shared Resource Tree.
7. List Shared Resource Trees available on this server.
8. Quit.
Enter your selection (1-8) [1] : 8
[Info] V-125-491 No SRT changes made.
