From owner-freebsd-stable@FreeBSD.ORG Wed Feb 10 00:00:33 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C67BF1065693 for ; Wed, 10 Feb 2010 00:00:33 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3ADEA8FC15 for ; Wed, 10 Feb 2010 00:00:32 +0000 (UTC) Received: from inchoate.gsoft.com.au ([203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id o1A00UNq004773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 10 Feb 2010 10:30:31 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Wed, 10 Feb 2010 10:30:27 +1030 User-Agent: KMail/1.9.10 References: <201002091231.17551.doconnor@gsoft.com.au> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4655901.eT2to6VThY"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201002101030.29063.doconnor@gsoft.com.au> X-Spam-Score: -3.638 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Subject: Re: one more load-cycle-count problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Feb 2010 00:00:33 -0000 --nextPart4655901.eT2to6VThY Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 10 Feb 2010, Freddie Cash wrote: > > /d sets it (for me) to 6300 milliseconds (6.3 seconds). I took this > > as a special value that disabled it entirely (no idea why they > > didn't use 0 or 255..) > > > > I've seen reports of the same on various hardware forums. =C2=A0Not sure > > if it's > > due to different firmware, or different drive models. > > You should still be able to list the timeout value explicitly > (instead of using /d). =C2=A0According to the help output, you can use > either 25.5 seconds or 3000-something seconds as the max value > (depends on the drive). Yes I know, I used /d and haven't had any issues since. As the original timeout was 8 seconds I am pretty confident it treats 63=20 as special otherwise the problem would still be happening for me. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart4655901.eT2to6VThY Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBLcfcd5ZPcIHs/zowRAmiPAKCBiPxnCMemkHC3fYZ4SmZorFT/3ACaA7ge amdhvlXclq7Uhj307WJuiLQ= =mpl8 -----END PGP SIGNATURE----- --nextPart4655901.eT2to6VThY--