Messages posted by: dvdmonster

Brahim wrote:
Yeah, it will be like a virtual directory.
In fact, it will be like DFS with automatic data management.

Sounds sweet.. can't wait to try it out.

Brahim wrote:Basically, all your data including network data will be presented as a single view to which your will write and read from.

I'm not sure i fully understand this. Will it be like a virtual directory with access to all the drives shown with dir-names or am I completely off here?

Brahim wrote:
It is booting that's usually an issue with having too many drives.
Note that the WD 2TB will use almost twice as much power as the 1TB version.

I had not seen that the 2TB where using more power than the nice 1TB's, it's not twice, but it's up there.

I an using 3 PSU's for my 24 1tb's. It's more or less a mix of what I had at hand when I was adding drives. I do check power-on with a watt-meter just to make sure the draw on starup is at accaptable levels.
I read somewhere that the WD's support poweron without spinup with a jumper, but i didnt look into that more at the time.. Would be nice if it's true, as my Areca supports staggered spinup.

.

Brahim wrote:
A completed timestamp and more log info would be useful.

Ok, but i can see the new and improved Flexraid 1.1 with proper logging has not been leaked yet

Great news. I guess you can never EVER get enough storage space.

I'm looking to downsize my 24 WD 1TB's to 12 WD 2TB's.. Happy days.

Any idear how long it will take to run a create on 12 TB2's in flexraid?

And while I'm out of control here, total filesizes as well.

IE. "raid-4 created successfully in 1hour 2min 20sec containing a total of 12.200.032 Mb of data (12 Mb/s)" or something like that ..

.

It would be nice if FlexRAID reported the duration of different time-consuming actions in a more understandable way in the log.

IE. "raid-4 created successfully in 1hour 2min 20sec." or something like that.

All i get now in the server log is
[2009-01-26 20:00:44,515] INFO : *** New files can now be written to the data directories! ***
and no more, even on completion.

and status returns:
* Task: create
* Status: completed
* Started: 26. januar 2009 20:00:41 CET
* T-stamp: 26. januar 2009 20:02:51 CET

T-stamp just returns the time i run the status command so all in all no information on the duration of the configration, and if i go back and check the log later, no information about what happend beside "New files can now be written to the data directories". Not very usefull.

Maybe I'm off here, but I think a better log would be nice.
Thanks in advance.

I understand what you are saying, and agree.

I was just wondering why restore to a new location would also require deleted/move/rename the damaged data in the original location, as it would also be untouched.

Brahim wrote:Was the data you were trying to restore still present?
FlexRAID will only recover data if absent.

Ahh ok!

I did try the "advanced->restore to these paths:" to another dir with the same result.
After deleting the file with errors both options work.
I don't think I like the fact that I need to delete the file from the original location in order to restore it to a new location. Is there any specific reason for this?

Thanks.

I have been testing different situations with FLEXraid, and i have run into this problem.

When i do a verity get bit mismatch error:

But when i do a restore on the DRU i get the following:

I can keep pressing verify and restore, and still get the same result.
What can i the problem here, as i would HATE to have this situation on my large server.

Ok, I found another tread about the same issue here http://www.openegg.org/forums/posts/list/50.page.
One thing that was not really adressed it how the algorithm works with relation to disk access on the datadrives.

After lurking for a long time i finally jumped in

Well, i have a question about the difference between quick-validate, validate and verify.

I understand they all check the data integrity, but i don't understand how efficient the q-validate/validate is.

Validate performs an algorithm check while verify performs a bit for bit check.

Does this algorithm check mean that just some of the data on the datadrives are read or that all the data is read but checked with a less demanding algorithm? and even less demanding with q-validate? I can't figure it out.

Thanks for the great program, i look forward to using it in the future.