QRecallDownloadIdentity KeysForumsSupport
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Groups] Back to home page 
Preallocation failed  XML
Forum Index » Problems and Bugs
Author Message
Christian Roth



Joined: 12-Jul-08 13:09
Messages: 26
Offline

Hi,

after updating to 1.1.4, I get the error that pre-allocation failed when trying to do a capture. Is this incidentally the case (I have 44 GB free on the target) or has this something to do with the "known issues" item about "Preallocation on Airport Extreme Volumes"? My target volume is a Netgear ReadyNAS NV+, and I think I was able to do captures even with less free space on that NAS with earlier volumes.

So my question is if the Preallocation issue might also apply to other manufacturers' NASes or if this is an issue specific to the Airport Extreme device?

The log says the following:



The pre-allocation size of "Length: 33554432" would only be 32 MB (if I did my math correctly), so with 44 GB available, that should not be a problem, should it?

Am I safe to apply the QRFilePreallocateDisable preference for a test if that remedies the issue or are there chances of ending up with a corrupt archive?

And a final note: The QRFilePreallocateDisable key does not yet seem to be listed here. Could you please add the description and the allowed key values there? Thanks!

-Christian
James Bucanek



Joined: 14-Feb-07 10:05
Messages: 1476
Offline

Christian,

Thanks for the reminder to document those settings. I've updated the advanced QRecall settings page. Look for the QRFilePreallocateDisable and QRFilePreallocateBugWorkaroundRule towards the bottom of the page.

I'd suggest starting by setting QRFilePreallocateBugWorkaroundRule to 1. This causes QRecall to assume that all volumes are affected by the pre-allocation bug and to use a workaround. This allows QRecall to continue to preallocate space (important to maintaining the integrity of the archive should the volume fill up), but avoids the pre-allocation bug in some versions of the OS and NAS drives.

If that fails to solve the problem, you can just turn off pre-allocation by setting QRFilePreallocateDisable to true.

- QRecall Development -
[Email]
Christian Roth



Joined: 12-Jul-08 13:09
Messages: 26
Offline

James Bucanek wrote:I'd suggest starting by setting QRFilePreallocateBugWorkaroundRule to 1.


I did that and as far as I can tell, this solved my problem. Thank you!

Also, thanks for updating the Advanced QRecall settings page, and the explanations are - as always - thorough and easy to understand.

A suggestion would be to include the contents of that page in the manual (i.e. application help file), as that was where I first looked. Or include a link to said page if you do not want this info to be available too easily

-Christian
 
Forum Index » Problems and Bugs
Go to:   
Powered by JForum 2.1.8 © JForum Team