Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Daniel Reurich <daniel@centurion.net.nz>
To: linux-raid@vger.kernel.org
Subject: smartchecks of raid members
Date: Tue, 22 Dec 2009 10:00:50 +1300	[thread overview]
Message-ID: <1261429250.7944.2249.camel@ezra> (raw)

Hi,

Is it safe and can it easily be done to put a raid1 member volume into
"write mostly && write behind" mode temporarily while doing a SMART full
disk check on that disk?

I believe this may help with the smart check as it stops the
interruptions caused by reads from the disk, and the writes will be
delayed and hopefully committed in larger chunks less often.  I also
this will allow the server to perform better by not blocking until the
writes on the disk being checked return.

Is the only risk the delay between a write being completed as far as the
process is concerned and the write being committed to the disk being
smart checked?

Daniel Reurich




             reply	other threads:[~2009-12-21 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 21:00 Daniel Reurich [this message]
2009-12-22  0:45 ` smartchecks of raid members John Robinson

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=1261429250.7944.2249.camel@ezra \
    --to=daniel@centurion.net.nz \
    --cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox