Just started a copies of /dev/urandom
to the new drive mirror pairs (in preparation
for crypt'ing them). This will take four
days so I can't touch the system for a
week now. No hurry on a 3.6 patch if
you were contemplating one. Maybe 3.7
will be out by then anyway.
>At 08:37 PM 11/10/2012 -05
At 08:37 PM 11/10/2012 -0500, Alan Stern wrote:
>Does the patch fix the problem?
Morning and coffee motivated an attempt
to build a kernel and try the patch.
However it fails to apply for 3.6.6
--even caffine is not enough to inspire
me to consider a -rc for production.
Any chance for a 3.6 patc
At 08:37 PM 11/10/2012 -0500, Alan Stern wrote:
>Does the patch fix the problem?
Will let you and the list know. Want
to wait for a full kernel release.
The drives go active if the power to
the docks is toggled after they spin
up--going with that for now.
Will finish configuring the array
and o
Hello,
I'm wondering how long it will be before this
patch appears in a 3.6.x release. Any idea?
Any opinion on whether a 3.4.x or 3.2.x kernel
would be better than 3.6.x for a production
network backup system (i.e. super critical)?
Or is 3.6 best? Running 3.1.8 at present.
Seeing the timeout
