Søren Schmidt wrote:
On 7Nov, 2008, at 20:12 , Peter Wemm wrote:
On Thu, Nov 6, 2008 at 11:17 PM, Jeremy Chadwick [EMAIL PROTECTED]
wrote:
[..]
As stated, FreeBSD's ATA command timeout is hard-set to 5 seconds, and
is not adjustable without editing the ATA code yourself and increasing
the
Note that Western Digital's RAID edition drives claim to take up to 7
seconds to reallocate sectors, using something they call TLER, which
force-limits the amount of time the drive can spend reallocating. TLER
cannot be disabled:
TLER can be enabled/disabled on recent WD drives
On Fri, Nov 07, 2008 at 12:08:01AM -0800, Artem Belevich wrote:
Note that Western Digital's RAID edition drives claim to take up to 7
seconds to reallocate sectors, using something they call TLER, which
force-limits the amount of time the drive can spend reallocating. TLER
cannot be
But regardless of TLER being toggleable, FreeBSD's ATA command timeout
of 5 seconds is too aggressive, and should be increased. Likewise, the
value should be a sysctl, so those who do want such aggressive values
Once it migrates from a constant to sysctl variable, could kernel maybe
also
On Thu, Nov 6, 2008 at 11:17 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
[..]
As stated, FreeBSD's ATA command timeout is hard-set to 5 seconds, and
is not adjustable without editing the ATA code yourself and increasing
the value. The FreeNAS folks have made patches available to turn the
I can confirm that. Many FreeNAS users had problems with their HDDs
(e.g. with APM, awake disks to access them after they felt to sleep).
Increasing timeouts solves the problem in most cases. I think increasing
the value BUT allowing the user to set it to a preferred value via
sysctrl would
On 7Nov, 2008, at 20:12 , Peter Wemm wrote:
On Thu, Nov 6, 2008 at 11:17 PM, Jeremy Chadwick
[EMAIL PROTECTED] wrote:
[..]
As stated, FreeBSD's ATA command timeout is hard-set to 5 seconds,
and
is not adjustable without editing the ATA code yourself and
increasing
the value. The FreeNAS
As i'm writing this i'm trying to rescue the contents of another computers disk.
Something about the seek heads or something related to that is
physically half-broken so the disk might need up to 10 retries just to
read a sector, once read however it's usually no problem. I'm using
myrescue
A user and myself on a broadband forum were discussing the possibility
of diminishing quality of hard disks (particularly 1TB models) in recent
days (specifically October).
The user continually referenced something called deep recovery cycle,
backed with claims from Newegg reviewers (who often
