linux-kernel - Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200906031216.44737.M4rkusXXL@web.de>
Date:	Wed, 3 Jun 2009 12:16:44 +0200
From:	Markus <M4rkusXXL@....de>
To:	linux-kernel@...r.kernel.org
Cc:	Robert Hancock <hancockrwd@...il.com>
Subject: Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17

Robert Hancock wrote:
> Markus wrote:
> > Now I want to know after what period of the time the kernel timeouts 
at 
> > these commands!? And if this timeout can be increased (manually, 
small 
> > patch for the kernel) and the min/max/avg time could somehow be 
> > messured. Every timeout kicks the drives off the raid, so I disabled 
> > the write cache (hdparm -W0 /dev/sdx) but thats no solution, just a 
bad 
> > workaround.
> 
> I believe the timeout for commands like these is usually 30 seconds. 
> Normally if it doesn't respond after that length of time, it never 
will. 
> Even if it eventually did, I don't think you'd be happy with disk 
access 
> delays of over 30 seconds..

Ok thats definitly bad. Will reask at the support...

Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/