This post is more than 5 years old
46 Posts
0
3514
scanner command error
Hi Guys,
We have 2 environments 1 production and 1 DR. Both NetWorker servers run on 7.4.2. We use Datadomain for our disk backups, the data is then cloned off to tapes.
The block size on the Datadomain is set to (1024 KB). :
Also the server we are using is a proliant DL580 G2 with 4 CPUS 2794mhz
OS is Windows 2003 SP1
3.8 GB RAM
1.2GB Virtual memory
9.67GB page file.
When we try and run the scanner command to import index and media database information in case of the DR, we get the following error:
failed to create shmem object Global\lgtsm1006405: Input/output error
failed to create shared memory: failed to create shmem object Global\lgtsm1006405: Input/output error
scanner: SYSTEM error: not enough space
I have contacted EMC but we have got nowhere so far, has anyone seen this before?
Any help is appreciated
Thanks
We have 2 environments 1 production and 1 DR. Both NetWorker servers run on 7.4.2. We use Datadomain for our disk backups, the data is then cloned off to tapes.
The block size on the Datadomain is set to (1024 KB). :
Also the server we are using is a proliant DL580 G2 with 4 CPUS 2794mhz
OS is Windows 2003 SP1
3.8 GB RAM
1.2GB Virtual memory
9.67GB page file.
When we try and run the scanner command to import index and media database information in case of the DR, we get the following error:
failed to create shmem object Global\lgtsm1006405: Input/output error
failed to create shared memory: failed to create shmem object Global\lgtsm1006405: Input/output error
scanner: SYSTEM error: not enough space
I have contacted EMC but we have got nowhere so far, has anyone seen this before?
Any help is appreciated
Thanks
ble1
2 Intern
2 Intern
•
14.3K Posts
0
June 16th, 2008 05:00
dd1980
46 Posts
0
June 12th, 2008 07:00
My customer was reccomended by the vendor to use block size 1024 in order to get the best writing performance to the datadomain.
I havent tried to change the heap memory as of yet, I need to contact an expert to do so as I am not quite sure how to do so.
Do you have any relevant articles you can point me to?
If not thanks for your help so far much appreciated.
ble1
2 Intern
2 Intern
•
14.3K Posts
0
June 12th, 2008 07:00
The error itself seems to suggest either an issue with heap memory or block size indeed. Did you try to increase heap memory?
Usually disk device has 128KB block size - I assume you change it manually?
dd1980
46 Posts
0
June 12th, 2008 07:00
ble1
2 Intern
2 Intern
•
14.3K Posts
0
June 12th, 2008 08:00
dd1980
46 Posts
0
June 16th, 2008 02:00
1. Click Start | Run and run regedt32
2. Browse to the following key in the registry editor:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems
3. Click to modify the "Windows" value
4. Locate the SharedSection parameter within the data of this value. This parameter will have 3 or 4 values.
5. Increase the third value by 256 or 512
For example, when the SharedSection equaled "1024,3072,512,512" in one case, changing it to "1024,3072,1024,512"
ble1
2 Intern
2 Intern
•
14.3K Posts
0
June 16th, 2008 02:00
ble1
2 Intern
2 Intern
•
14.3K Posts
0
June 16th, 2008 02:00
dd1980
46 Posts
0
June 16th, 2008 02:00
we changed the memory heap in widows registry to 1024, restarted the NetWorker Server but we are getting the same error on the scanner command.
Any other ideas?
dd1980
46 Posts
0
June 16th, 2008 02:00
ble1
2 Intern
2 Intern
•
14.3K Posts
0
June 16th, 2008 02:00
In my test the only strange thing is that scanner in both cases states record size to be 128KB (however volume properties report size to be 1024KB):
C:\>scanner -i -v C:\tmp\filedev
8909:scanner: using 'C:\tmp\filedev' as the device name
8374:scanner: Reading the adv_file label
8936:scanner: scanning adv_file disk hrle.001 on C:\tmp\filedev
8937:scanner: volume id 4265883292 record size 131072
created 6/02/08 20:06:20 expires 6/02/10 20:06:20
8939:scanner: adv_file disk hrle.001 already exists in the media index
8850:scanner: ssid 5648526: found beginning of hcrvelin:C:\tmp
29485:scanner: ssid 5648526: scan complete
8786:scanner: ssid 5648526: 328 MB, 50 file(s)
32339:scanner: (ssid 5648526) confirmed 50 existing file index entries
8761:scanner: done with adv_file disk hrle.001
C:\>scanner -i -v C:\tmp\filedev
8909:scanner: using 'C:\tmp\filedev' as the device name
8374:scanner: Reading the adv_file label
8936:scanner: scanning adv_file disk hrle.001 on C:\tmp\filedev
8937:scanner: volume id 4283839107 record size 131072
created 6/16/08 11:29:39 expires 6/16/10 11:29:39
8939:scanner: adv_file disk hrle.001 already exists in the media index
8850:scanner: ssid 4250284757: found beginning of hcrvelin:C:\tmp
29485:scanner: ssid 4250284757: scan complete
8786:scanner: ssid 4250284757: 328 MB, 50 file(s)
32339:scanner: (ssid 4250284757) confirmed 50 existing file index entries
8761:scanner: done with adv_file disk hrle.001
To be honest, I'm not sure if bs is really related to this problem. The only remotely close thing to your problems is described in esg68857.
dd1980
46 Posts
0
June 16th, 2008 02:00
Thanks a lot for all your help so far, already you have been more useful that Legato support.
I have 7.4.2 set up in our lab, and I tried the scanner command which seemed to work fine on the disk device, both at 128kb and 1024kb. I am going to do some more research on the matter and post back once I know a little more.
Thanks
dd1980
Biku1
42 Posts
0
June 16th, 2008 17:00
I think you should tried to increse the share quota of the folder and also please check that the folder should have the administrative rights given ..This should work.
dd1980
46 Posts
0
August 5th, 2008 01:00
the issue was resolved by running scanner directly form the console.
The customer was running it via RDP (and failed to let me know).
Thanks for all your help.
DD1980
avmaint
115 Posts
0
February 3rd, 2016 04:00
running the "cmd" as administrator fixed my issue, exactly same error