Quantum Forum V

Quantum Forum for DXi V5000

Hi,

I am using the DXiV1000 and have an issue where space reclamation has started to fail almost straight away every time it runs . No configuration changes have been made since it last was working. The logs show the following:

INFO - 01/05/16-17:41:07 - bpgc GCDaemon.cpp(848) [bpgc] interruptWait() - Start Reclamation Request detected, stopping wait
INFO - 01/05/16-17:41:12 - bpgc CleanupStrategyFactory.cpp(152) [bpgc] create() - Selecting the Target Cleanup Strategy
INFO - 01/05/16-17:41:12 - bpgc GCDaemon.cpp(1562) [bpgc] bloom_init() - BPGC Bloom Projected Element count: 400000.
INFO - 01/05/16-17:41:12 - bpgc GCDaemon.cpp(1592) [bpgc] bloom_init() - Bloom Filter size: 240417 bytes
INFO - 01/05/16-17:41:12 - bpgc ReconcileThread.cpp(1163) [bpgc] doProcess() - [TID=18386]{46991293344064} Reconciling Blockpool Tags
INFO - 01/05/16-17:41:12 - bpgc ReconcileThread.cpp(125) [bpgc] dumpBlockpoolTags() - [TID=18386]{46991293344064} Dumping the blockpool tags
ERROR - 01/05/16-17:41:12 - bpgc BfstV2.cpp(156) [bpgc] handleErr() - Bfst error occurred [/mnt/work/QuantumVTL/lib/tsunami/Blockpool/BP/GetBfstBlobV2.cpp(312)::next()]): ErrorCode: 8107160 ErrorString: Network error(bfst2_query_blobs_next() failed: Network connection lost.
Error writing parcel to client server.
Error writing data to network socket: 127.0.0.1:1062. Broken pipe
)(0x7BB498)
ERROR - 01/05/16-17:41:12 - bpgc ReconcileThread.cpp(162) [bpgc] dumpBlockpoolTags() - NASException calling GetBfstBlobV2::next() - details: ErrorCode: 8107160 ErrorString: Network error(bfst2_query_blobs_next() failed: Network connection lost.
Error writing parcel to client server.
Error writing data to network socket: 127.0.0.1:1062. Broken pipe
)
ERROR - 01/05/16-17:41:12 - bpgc ReconcileThread.cpp(1296) [bpgc] process() - [TID=18386]{46991293344064} ErrorCode: 8107160 ErrorString: Network error(bfst2_query_blobs_next() failed: Network connection lost.
Error writing parcel to client server.
Error writing data to network socket: 127.0.0.1:1062. Broken pipe
)
INFO - 01/05/16-17:41:13 - bpgc GCStatusFile.cpp(1353) [bpgc] logState() - Reclamation Results --- StartTime:1452015667; EndTime:1452015673; Running:false; Progress:100; TotalProgress:100; Status:; SubStatus:; ActualBytesReclaimed:0; ActualBytesToReclaim:0; UserBytesReclaimed:0; UserBytesToReclaim:0; NumberOfStages:2

Does anyone have any ideas of what could be causing this?

Views: 50

Reply to This

Replies to This Discussion

The DXI looks to be having issue accessing its blockpool. Try rebooting the DXI v1000 two times in a row to see if that will resolve the issue.

I tried rebooting for a second time earlier today and it appears to be running successfully now, it is taking a while to complete as it has not run in two weeks but I will update tomorrow whether or not it has finished alright.

This seems to have done the trick, it is all back to normal now but it is a little odd that it needs two reboots.

Hi, I'm just updating in regards to this discussion in that my colleague is still experiencing the same issues with the DXi space reclamation process. This seems to now occur on a regular basis.

So the error appears. JR reboots the unit twice, it then "seems OK". A few days later it goes again. 

If the firmware for the DXI is not at 2.3.2.2, then the first thing to do is update. This issue was seen at the earlier firmware versions. If the DXi version is current, I would suggest a redeploy of the DXI ovf. 

Hi Jerry, thanks for the reply. Can you confirm if this is the latest version? Thanks.

2.3.2 (12170-55464 Build12)

2.3.2.2 is the most current version.

Ok. Downloading now.

I would assume as long as the DXI can ping an outside network, the firmware can be downloaded and installed via the home page of the DXi. Click on the link that says software upgrade.

If the DXI is not able to ping the network you can get the DXI 2.3.2.2 firmware upgrade file from here. https://forms.quantum.com/Software/V1000upgrade/2.3/ There are also instructions on the page which explain how to apply the upgrade file.

Hmmm - the DXI on that build is saying it's current when it checks (which is why we queried the version no).

Thanks.

RSS

Tips + Tricks

© 2022   Created by Quantum Forum V.   Powered by

Badges  |  Report an Issue  |  Terms of Service