June 18, 200917 yr fyi I posted about this issue at AVS forums and have a good sense the problem isn't unraid itself which is good. It would be helpful to confirm exactly how to ensure Windows XP/Vista/7 clients can be made to not attempt to index files on the unraid server. I believe I've ruled this out but will have to simply turn them off to prove that's not the cause of the problem I'm seeing. I think I more suspect some other process on the client decoding the stream at this point. http://www.avsforum.com/avs-vb/showthread.php?p=16670214#post16670214
June 18, 200917 yr Author fyi I posted about this issue at AVS forums and have a good sense the problem isn't unraid itself which is good. http://www.avsforum.com/avs-vb/showthread.php?p=16670214#post16670214 Dabl, the difference with your issue is I don't have any problems streaming at all once the drive is spun up. The problem rears its head when I'm streaming off say disk 1 and then disk 2 is accessed returning it from standby and stalls the data of disk 1. My stall problem disappears entirely if I set the drives to not spin down at all. Do you have the same results? It seems most of the replies on AVS point to the whole movie being on a single drive as well, which could mean another drive is not being accessed and the problem is not being triggered. You could also keep a laptop next to you and look at which drives are spun up when you start the streaming and then look again and see if any additional are now spun up once you experience a hiccup. Try turning spindown standby off.
June 18, 200917 yr Author I suspect it might be a lock placed by the "md" driver, so you might not see the same behavior under native Ubuntu unless you also set up a "raid-5" array on it using the stock "md" driver. (Don't do this with your current disks, as it will probably be incompatible with the existing reiser file-system.) Joe L. Ah That's a good call. I certainly was not testing using that driver. Perhaps we're onto something for better or worse?
June 19, 200917 yr Dabl, the difference with your issue is I don't have any problems streaming at all once the drive is spun up. The problem rears its head when I'm streaming off say disk 1 and then disk 2 is accessed returning it from standby and stalls the data of disk 1. My stall problem disappears entirely if I set the drives to not spin down at all. Do you have the same results? It seems most of the replies on AVS point to the whole movie being on a single drive as well, which could mean another drive is not being accessed and the problem is not being triggered. You could also keep a laptop next to you and look at which drives are spun up when you start the streaming and then look again and see if any additional are now spun up once you experience a hiccup. Try turning spindown standby off. Thanks for the comments and suggestions, duly noted. If I'm able to observe anything interesting I'll be sure to follow up.
August 21, 200916 yr Author For the moment... Setting the drives to never spin down is the only way to get around it. From other discussions, it sounds like it may be a Linux locking bug vs. an explicitly unraid issue that may be addressed in the next Linux kernal. Once stable, Tom has a good track record of incorporating those kernels into unraid. There's a good post one of the gang wrote around here, but I don't have time to search for it at the moment. Do a search for locking maybe.
September 10, 200916 yr Has anyone tried this with the latest release of slackware in a dev environment and unraid? Just curious. I think Slackware release a 64 bit version as well.
Archived
This topic is now archived and is closed to further replies.