All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ric Wheeler <ric@emc.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: David.Ronis@McGill.CA, linux-ide@vger.kernel.org
Subject: Re: Problem with disk
Date: Fri, 05 May 2006 20:51:14 -0400	[thread overview]
Message-ID: <445BF302.4050709@emc.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0605051939120.13704-100000@coffee.psychology.mcmaster.ca>



Mark Hahn wrote:

>>I would suggest that you should run with the write cache disabled unless 
>>you can verify working barrier support.
>>    
>>
>
>this is true, but extremely conservative/paranoid.  it makes a lot 
>of sense if you're handling banking transactions or if you really
>see a lot of abrupt power-offs (yank the battery).  what are the chances
>of a drive failing to write dirty blocks when idle, halting?
>  
>
The write cache in modern drives is multiple megabytes - 8 or 16MB is 
not uncommon. The chances that you have data that is lost on a power 
failure in the write cache is actually quite high...

I agree that most people should not lose too much sleep over this.

>don't get me wrong: write barriers are A Good Thing.  just that Linux 
>survived very nicely for many years before such things were bothered with.
>
>  
>
>>The fact that your drive reports IO errors is also worrying - you might 
>>just have a bad drive...  You can look at drive help with tools like 
>>smartctl.
>>    
>>
>
>IO errors trump any concerns for write barriers - there's no need to 
>even think about barriers or cache settings if the disk is, for instance,
>reporting media errors...
>
>  
>
Agreed again ;-)

ric


  reply	other threads:[~2006-05-06  0:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 20:01 Problem with disk David Ronis
2006-05-03 20:08 ` Ric Wheeler
2006-05-05 23:49   ` Mark Hahn
2006-05-06  0:51     ` Ric Wheeler [this message]
2006-05-06 17:11       ` Mark Hahn
2006-05-06 18:17         ` Ric Wheeler
2006-05-06 18:34           ` Mark Hahn
2006-05-06 22:56             ` Tejun Heo
2006-05-07 13:21               ` Ric Wheeler
2006-05-07 13:41                 ` Tejun Heo
2006-05-08 14:33                   ` Ric Wheeler
2006-05-10 22:21                     ` Tejun Heo
2006-05-13 19:31                       ` Ric Wheeler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=445BF302.4050709@emc.com \
    --to=ric@emc.com \
    --cc=David.Ronis@McGill.CA \
    --cc=hahn@physics.mcmaster.ca \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.