I m not sure if you already investigated this but s.m.a.r.t. has quite many
diagnostic info. Even if the drive has not actually been marked as broken.
This is somewhat vendor dependent. I did not check these info with openbsd
but it should be possible.
Facts from my hard drives include:
Bad
On Mon, Dec 02, 2013 at 03:39:17PM +0100, Jan Lambertz wrote:
I m not sure if you already investigated this but s.m.a.r.t. has quite many
diagnostic info. Even if the drive has not actually been marked as broken.
This is somewhat vendor dependent. I did not check these info with openbsd
but it
On Mon, 2 Dec 2013, Erling Westenvik wrote:
On Mon, Dec 02, 2013 at 03:39:17PM +0100, Jan Lambertz wrote:
I m not sure if you already investigated this but s.m.a.r.t. has quite many
diagnostic info. Even if the drive has not actually been marked as broken.
This is somewhat vendor dependent. I
OK, just to clarify:
The kernel is 5.3 with the official patches applied, no other modifications.
I read through the changes for 5.4 and certainly, there has been a ton of
work done, and I will upgrade soon. Nothing listed in the changes seems
like it would directly address a problem like this,
On 12/01/13 06:20, John Hynes wrote:
OK, just to clarify:
The kernel is 5.3 with the official patches applied, no other modifications.
I read through the changes for 5.4 and certainly, there has been a ton of
work done, and I will upgrade soon. Nothing listed in the changes seems
like it
I'm having some trouble figuring out what is causing a systemic performance
issue. By systemic I mean that running even seemingly trivial things
(i.e. 'ls' on a directory with only a few files in it) is accompanied by a
substantial delay before any response, say, of 15-30 seconds. Not *every*
On Sat, 30 Nov 2013, John Hynes wrote:
I'm having some trouble figuring out what is causing a systemic performance
issue. By systemic I mean that running even seemingly trivial things
(i.e. 'ls' on a directory with only a few files in it) is accompanied by a
substantial delay before any
On Sat, Nov 30, 2013 at 04:02:58PM -0500, John Hynes wrote:
I'm having some trouble figuring out what is causing a systemic performance
issue. By systemic I mean that running even seemingly trivial things
(i.e. 'ls' on a directory with only a few files in it) is accompanied by a
substantial
On Sat, Nov 30, 2013, at 03:55 PM, Kenneth R Westerback wrote:
On Sat, Nov 30, 2013 at 04:02:58PM -0500, John Hynes wrote:
OpenBSD 5.3 (GENERIC.MP) #0: Fri Sep 13 04:11:52 EDT 2013
j...@hytronix-gw1.hytronix.com:/usr/src/sys/arch/amd64/compile/
GENERIC.MP
Try 5.4 or -current.
On 11/30/13 20:04, Shawn K. Quinn wrote:
On Sat, Nov 30, 2013, at 03:55 PM, Kenneth R Westerback wrote:
On Sat, Nov 30, 2013 at 04:02:58PM -0500, John Hynes wrote:
OpenBSD 5.3 (GENERIC.MP) #0: Fri Sep 13 04:11:52 EDT 2013
j...@hytronix-gw1.hytronix.com:/usr/src/sys/arch/amd64/compile/
On Sat, Nov 30, 2013 at 07:04:44PM -0600, Shawn K. Quinn wrote:
On Sat, Nov 30, 2013, at 03:55 PM, Kenneth R Westerback wrote:
On Sat, Nov 30, 2013 at 04:02:58PM -0500, John Hynes wrote:
OpenBSD 5.3 (GENERIC.MP) #0: Fri Sep 13 04:11:52 EDT 2013
11 matches
Mail list logo
