Unsolved
This post is more than 5 years old
68 Posts
0
713
March 15th, 2007 11:00
Moved 1client index now have a error "save: SYSTEM error: Cannot lock file"
We were ruuning out of disk space on my networker 7.3.2 jumbo1 Red Hat 4 server on the pimary drive.
I moved "mv command" 1 of my clients index directory say called "primary2" to a different mounting point. The old path was /nsr/index whitch is linked to /home/nsr/index all of the clients are listed here. The new link "ln command" is to /backup/nsr/index/pimary2 so under /home/nsr/index/pimary2 with the pimary2 shows as a link.
I have shutdown networker and restarted netwoker. Problem was still their I have rebooted the server and the problem is still their.
Problem
pimary2:/ap00 3 retries attempted
pimary2:/ap00 save: SYSTEM error: Cannot lock file '/backup/nsr/index/devstar2bu/db6/45f80000/45f8fc89.sip'
pimary2:/ap00
pimary2:/ap00 save: shutdown failed
* : Failed with error(s)
The .sip files are in the new location and the system is making new directories.
I have tried to do a "nsrim -X" and "nsrck -L6 pimary2"
03/14/07 10:17:53 nsrck: checking index for 'pimary2' the error:
03/14/07 10:17:54 nsrck: File index for client 'pimary2' is already being checked
I did do just before the "mv" move i did a "nsrck -L6" command and it was fine.
So far I have not been able to get this fixed.
I moved "mv command" 1 of my clients index directory say called "primary2" to a different mounting point. The old path was /nsr/index whitch is linked to /home/nsr/index all of the clients are listed here. The new link "ln command" is to /backup/nsr/index/pimary2 so under /home/nsr/index/pimary2 with the pimary2 shows as a link.
I have shutdown networker and restarted netwoker. Problem was still their I have rebooted the server and the problem is still their.
Problem
pimary2:/ap00 3 retries attempted
pimary2:/ap00 save: SYSTEM error: Cannot lock file '/backup/nsr/index/devstar2bu/db6/45f80000/45f8fc89.sip'
pimary2:/ap00
pimary2:/ap00 save: shutdown failed
* : Failed with error(s)
The .sip files are in the new location and the system is making new directories.
I have tried to do a "nsrim -X" and "nsrck -L6 pimary2"
03/14/07 10:17:53 nsrck: checking index for 'pimary2' the error:
03/14/07 10:17:54 nsrck: File index for client 'pimary2' is already being checked
I did do just before the "mv" move i did a "nsrck -L6" command and it was fine.
So far I have not been able to get this fixed.
0 events found
No Events found!
lee6
68 Posts
0
March 15th, 2007 11:00
'/backup/nsr/index/pimary2/db6/45f80000/45f8fc89.sip'
This is the client name aka server name.
ble1
4 Operator
•
14.4K Posts
0
March 15th, 2007 11:00
Why simply not updating index path as that is official procedure?
ble1
4 Operator
•
14.4K Posts
0
March 15th, 2007 12:00
lee6
68 Posts
0
March 15th, 2007 12:00
I have been trying to get a official recommendation on what to do I am in my 3rd day with out a backup on this server.
Thanks for look at this.
ble1
4 Operator
•
14.4K Posts
0
March 15th, 2007 12:00
I guess lock() code uses does not handle symbolic links meaning you should follow official recommendation and see if that gets it work.
lee6
68 Posts
0
April 25th, 2007 09:00
a USA Government agency (over national security) told EMC NetWorker was unsecured so they rewrote it to not allow this to work.
I know this sounds a bit out there but I had to get support to get the programmer to track why this was not working and he said this.
Their maybe a work around. untested by me and was unknown my EMC NetWorker support person but it may work. I have it 1/2 way try and it look ok. I did not put it into production.