jbuszkie

I think it was a 5900 drive. "ST4000VN000". I'll have to check to see if I have any data from a full parity check. I'm pretty sure I don't have any since we the nr_requests thing was discovered.. I'll dig through my posts and logs to see. Maybe the last monthly parity check will be in logs somewhere..

I'd like to see an easy way to make the array read only.. Solely for the times when I'm upgrading parity. Right now, I believe the procedure is to not write to the array so your old parity is still valid. I did this by going into maintenance mode. I'd love an option to make the array RO so files can still be read... but no write will occur... One step further would be to allow new files to be written to the cache drive.. but not moved to the array until you made the array normal RW again. Is there a way to do this already? And sorry if this has already been suggested.. Jim

I mean this in the nicest possible way.. but you suck! I wish I had those speeds! lol I'm really tempted to go back to the 4T parity drive just to see how long that would take.. then it would be an apples to apples comparison. But I don't know that I want to put that extra stress on my system and have my array be unavailable for another day! But I am dying to know! I don't know what to do! *pout* I do have some older 2T and 3T disks in my system and I only have the older saslp controller (3Gb/s only I believe or was it 1.5Gb/s)

Just to throw my results in. I just did a pre-clear on a new 8T ~61 hours to preclear. I'm currently running a parity sync right now. It seems to be taking longer than my older 4T drive. Maybe I'll do a re-sync with the 4T drive for comparison??.. Call it 13.5 hours to get to my old 4T mark where it would have been done. Now it's just parity drive left as I have no other disks bigger then 4T. ========================================================================1.16 == invoked as: /boot/config/plugins/preclear.disk/preclear_disk.sh -M 4 -o 2 -c 1 -f -J /dev/sdg == ST8000AS0002-1NA17Z Z840AB6F == Disk /dev/sdg has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 1000448 Bytes == Last Cycle`s Pre Read Time : 19:16:58 (115 MB/s) == Last Cycle`s Zeroing time : 18:31:56 (119 MB/s) == Last Cycle`s Post Read Time : 23:09:17 (95 MB/s) == Last Cycle`s Total Time : 60:59:48 == == Total Elapsed Time 60:59:48

Ok.. Pre-clear took 60 hours! ouch! The parity synch seems to be taking longer too. Maybe once this is done, I'll resynch my old parity drive for a time comparison. It's almost at the 4T mark and it's about 14 hours into it.. I swore my old numbers were about 12 hours.. hmmm.... Jim

It works well!

This pre-clear is going to take a while.. 137MB/s, 132MB/s, and 125MB/s for the 25% 50% and 75% points of the pre-read. It seems like it's going to be like 16-18 hours just for the pre-read! I am going to use this archive drive as a parity drive justified by the link in the post above. Jim

I just got my first drive today.. Starting the pre-clear now.. I don't want to think about how long it's going to take to pre-clear this sucker! My second one is supposed to come on Monday. Hopefully the pre-clear will be done by then! Now I'm going to have to drudge through this forum to remember the best way to upgrade a parity disk!

Understood, so I added a "refresh" button which allows individual rows to be recomputed (works very nifty!) You're the man! Can't wait to try it out! Thanks! Jim

And how do I get this new "compute all" feature? I looks for an update to the plugins and I didn't see any update for the webgui? Or do I have to wait for the next release? Thanks again, Jim

Yeah.. but I don't necessarily want to recompute everything. Just the things I know changed? some of those things take a while to compute.

I don't know if this merits a new thread or not.. but along the same lines here... Can you add a "refresh" to each share? There are times when I'm shuffling things around and I want to refresh one drive/share without losing all the others I've displayed? Right now I have to go to main and come back. but I lose the others that I didn't touch but still want to see. Thanks, Jim

I just picked up 2 of them! :-)

Thanks for that! I assumed someone did a write up. Thanks for posting it for me! Maybe I'll get one?? hmm....

What kind of effects can we expect because this is an archive drive vs a regular one?

Cool! Thanks! Jim

My first guess is no.. It does some checks to see if the disk is in the array. That might break.. But that's just a guess... Someone else may have a better, more accurate, answer. I've done a spare usb drive with unraid eval before on another machine.. Boot to usb. Run unraid. Go back to normal os. Might be a little more complicated now that you have to get a temp key from limetech. Jim

There are times when I want to map out my whole system. Right now I have to click on each "compute" which takes a while for some shares. I'd much rather hit a "Compute all" button and walk away and come back later when it's finished. I'd like to see the same for the disk shares too.

+1...

I have 8... but 2 are not in the array .. in fact.. I may have been less than 6 as I'm not sure where my cache disks (2) are located! Jim If I trust the odering SDa- SDx... I had 5 disks in the parity check on the SASLP controller. (11 total in the array including parity)

I have 8... but 2 are not in the array .. in fact.. I may have been less than 6 as I'm not sure where my cache disks (2) are located! Jim

No idea. Looking at SuperMicro's specs, it IS based on a Marvell chip (Marvell 6480), but I don't know if that has the same issues as the 9480 chip used in the SAS2LP. Very easy to test => just do a parity check (Just run it for perhaps 10 minutes and update the status); then change the nr_requests values and repeat the process. Ok.. With the default.. I was at 90-95MB/s With the change I was at ~102-106MB/s So there is a speed up for the SASLP original card as well. I guess I put this in the go script? Jim

It's running it's monthly right now. But it's past the the 3T disks so only 4 or 5 are left in the check. Maybe I'll try it after the whole thing completes. Jim

Dumb question... Do we think this setting will improve parity check speeds with the original SASLP card? (and V6)

I wish I could afford a bunch of new 6T's!