New error with build 009

[2008-11-28 16:30:17,953] ERROR: [create] Unable to acquire disk free space for H:\! - Please retry the task...
java.lang.Exception: Unable to acquire disk free space for H:\! - Please retry the task...
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
[2008-11-28 16:32:04,890] ERROR: [rsynch] null
java.io.EOFException
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
[2008-11-28 16:32:31,656] ERROR: [create] Unable to acquire disk free space for H:\! - Please retry the task...
java.lang.Exception: Unable to acquire disk free space for H:\! - Please retry the task...
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
[2008-11-28 16:35:46,953] ERROR: [create] Unable to acquire disk free space for N:\! - Please retry the task...
java.lang.Exception: Unable to acquire disk free space for N:\! - Please retry the task...
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)
	at java.lang.Void.<unknown>(Unknown Source)

Both H and N are perfectly functional drives, with plenty of space for the test RAID I was trying to generate.

Are both drive totally empty?

If so, try creating a dummy file in each drive and leave them there.
Let me know if that makes a difference.

Nope. H was empty, that's why I tried switching parity to N, which had plenty of space for the test but it sure wasn't empty.

gorman wrote:Nope. H was empty, that's why I tried switching parity to N, which had plenty of space for the test but it sure wasn't empty.

Ah, I just found a stupid bug, which I have just fixed.
As of now, the workaround is not being executed (so much for having that in place).

Nevertheless, I am curious as to why getting the free space using the normal logic is failing 100% for you.

A will publish a new build in a few minutes.
I will post back when done.

Oh, what anti-virus are you using?

Ok, new builds uploaded in the pre-release section.

I'm using Antivir for antivirus.
I'll check the new build and report back.

Ok, with the new build it appears to be working. The previous error has disappeared.
Thanks!

gorman wrote:Ok, with the new build it appears to be working. The previous error has disappeared.
Thanks!

Phew!
Great news.

Hi,
I've got the same error, but with the 1.0 final build...
(I'm running WHS)
If I restore on a local disk (eg E:\, C:\..) it works but if I go through a share (eg \\server\Vidéos) then it gave me this error. But if I add write something via another computer in this share, it works w/o pb.
Do you have any idea why ?

Thanks for all your work, I'm looking forward the release of a realtime version.. ^^

The problem here is that the root share \\server\Vidéos is not reporting the free space correctly.
It is not reporting the free space of all of the combined drives to which it spreads.
It is only reporting the free space of the drive where the parent folder "Vidéos" is on.
This is the same issue as when using DFS.

If you know that you indeed have enough space for the process, set the strictOnFreeSpace property to false.

Ok I will try this next time.. thanks !