I have two pata drives that I'm pretty sure are on the same controller.  Disk1 is hde and disk2 is hdf.  Disk1 has music on it and gets used fairly often.  Disk2 has movies and is less used.

 

I recently upgraded to 4.5.3 from 4.4.2 and now when disk1 spins up, disk2 also spins up.  This did not happen with 4.4.2.

 

The drives are attached to the motherboard, an Asus P5LD2-VM.

 

Anyway to fix this?

 

Thanks

syslog-2010-05-02.txt

I have two pata drives that I'm pretty sure are on the same controller.  Disk1 is hde and disk2 is hdf.  Disk1 has music on it and gets used fairly often.  Disk2 has movies and is less used.

 

I recently upgraded to 4.5.3 from 4.4.2 and now when disk1 spins up, disk2 also spins up.  This did not happen with 4.4.2.

 

The drives are attached to the motherboard, an Asus P5LD2-VM.

 

Anyway to fix this?

 

Thanks

Disable spin-up groups (on the settings page).

 

 

Thanks Joe, that did it.

Thanks Joe, that did it.

Just be aware, the spinup-group feature was added for a reason. To fix the "freeze" of a movie and/or music when the other drive on a controller spins up when accessed.

 

You might not need it based on how you store your data and how you use your server, but others find it being enabled by default provides a better experience for family members using the server. 

 

See here: http://lime-technology.com/forum/index.php?topic=4782.0

 

Joe L.

Thanks Joe, that did it.

Just be aware, the spinup-group feature was added for a reason. To fix the "freeze" of a movie and/or music when the other drive on a controller spins up when accessed.

 

You might not need it based on how you store your data and how you use your server, but others find it being enabled by default provides a better experience for family members using the server. 

 

See here: http://lime-technology.com/forum/index.php?topic=4782.0

 

Joe L.

 

Joe, is that the same as the BKL issue, or are they unrelated?

Thanks Joe, that did it.

Just be aware, the spinup-group feature was added for a reason. To fix the "freeze" of a movie and/or music when the other drive on a controller spins up when accessed.

 

You might not need it based on how you store your data and how you use your server, but others find it being enabled by default provides a better experience for family members using the server. 

 

See here: http://lime-technology.com/forum/index.php?topic=4782.0

 

Joe L.

 

Joe, is that the same as the BKL issue, or are they unrelated?

Not related.  Of a similar class in that inter-process locks and semaphores are involved, but not the big-kernel-lock.

 

 

Thanks Joe, that did it.

Just be aware, the spinup-group feature was added for a reason. To fix the "freeze" of a movie and/or music when the other drive on a controller spins up when accessed.

 

You might not need it based on how you store your data and how you use your server, but others find it being enabled by default provides a better experience for family members using the server. 

 

See here: http://lime-technology.com/forum/index.php?topic=4782.0

 

Joe L.

 

Joe, is that the same as the BKL issue, or are they unrelated?

Not related.   Of a similar class in that inter-process locks and semaphores are involved, but not the big-kernel-lock.

 

 

 

Ah, weak.  The BKL is still probably my #1 annoyance with my unRAID server.  I know it isn't something that LimeTech can fix directly, but I sure hope it gets taken care sometime soon.  Thanks Joe.

BKL in ReiserFS was mostly fixed in Linux Kernel 2.6.33 series, I believe.

 

It might have been back-ported to 2.6.32 series.

Thanks Joe, that did it.

Just be aware, the spinup-group feature was added for a reason. To fix the "freeze" of a movie and/or music when the other drive on a controller spins up when accessed.

 

You might not need it based on how you store your data and how you use your server, but others find it being enabled by default provides a better experience for family members using the server. 

 

See here: http://lime-technology.com/forum/index.php?topic=4782.0

 

Joe L.

 

Joe, is that the same as the BKL issue, or are they unrelated?

Not related.   Of a similar class in that inter-process locks and semaphores are involved, but not the big-kernel-lock.

 

 

 

Ah, weak.  The BKL is still probably my #1 annoyance with my unRAID server.  I know it isn't something that LimeTech can fix directly, but I sure hope it gets taken care sometime soon.  Thanks Joe.

How do you think the BKL lock affects you?   I've not seen it.  Yes, prior to 4.5.3 there was lock contention but that was not the BKL.   I thought it was the cause of pauses of video when disks were spun up, but I was wrong.

 

I know that the BKL was/is being removed from the reiserfs.  I'm guessing it will be in a future release of the kernel.  I doubt it will have much effect.

 

How do you think the BKL lock affects your server?

The most common issue is this:

 

I'm playing music (streaming from the server to either the HTPC or desktop).  I start browsing my server (from either the HTPC or desktop) and the music pauses for a good couple of seconds.  It doesn't seem to matter if I'm browsing the same disk that contains the music, or another one.  Spinning up all drives in advance also does not fix the issue.  Therefore, I thought this was caused by BKL.  Maybe not?  Maybe enabling and configuring spinup groups would solve this?  I would be quite happy if it did.

The most common issue is this:

 

I'm playing music (streaming from the server to either the HTPC or desktop).  I start browsing my server (from either the HTPC or desktop) and the music pauses for a good couple of seconds.  It doesn't seem to matter if I'm browsing the same disk that contains the music, or another one.  Spinning up all drives in advance also does not fix the issue.  Therefore, I thought this was caused by BKL.  Maybe not?  Maybe enabling and configuring spinup groups would solve this?  I would be quite happy if it did.

I think you are describing this issue:

3. An I/O stream via Windows PC freezes when same Windows PC is used to access data on a spundown disk.  This is a Windows problem and can not be fixed by unRAID OS.  From examining SMB connection traces, what I have determined is this: When a Windows PC (client) connects to a Server, it opens a single "SMB Connection".  Over this connection it sends it's requests: lookups, read, writes, etc, no matter which Share is being accessed (that is, all shares on the same server are accessed over a single SMB connection).  Hence, say for example, video is being read from the server and rendered on a Windows PC; if from the same Windows PC you now try to access another share with a spundown drive, Windows will use the same connection, resulting in "freeze" of the video while the I/O reqeust to the spundown drive is being serviced.

 

I have spent a couple of hours looking into this issue on the Windows side and have not found any way to tell Windows to open multiple SMB connections to multiple shares on the same server.

I'm not sure if there is a fix, other than to get rid of the windows OS and install a multitasking OS.

 

Joe L.

I'm not sure if there is a fix, other than to get rid of the windows OS and install a multitasking OS.

 

Hmm, I'll have to do some testing, I guess.  I know this happens with my HTPC as well (which runs XBMC Live, which is Linux-based), but perhaps my Windows computer and my HTPC have been accessing unRAID simultaneously.

I'm not sure if there is a fix, other than to get rid of the windows OS and install a multitasking OS.

 

Hmm, I'll have to do some testing, I guess.  I know this happens with my HTPC as well (which runs XBMC Live, which is Linux-based), but perhaps my Windows computer and my HTPC have been accessing unRAID simultaneously.

It could be that your SATA controllers are actually emulating IDE controller behavior at a lower level.