All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henrik Holst <henrik.holst@idgmail.se>
To: James Peverill <jamespev@net1plus.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Resize on dirty array?
Date: Wed, 09 Aug 2006 16:56:53 +0200	[thread overview]
Message-ID: <44D9F7B5.1060000@idgmail.se> (raw)
In-Reply-To: <44D9C6F5.7070501@net1plus.com>

James Peverill wrote:

> I'll try the force assemble but it sounds like I'm screwed.  It 
> sounds like what happened was that two of my drives developed bad 
> sectors in different places that weren't found until I accessed 
> certain areas (in the case of the first failure) and did the drive 
> rebuild (for the second failure).

The file /sys/block/mdX/md/sync_action can be used to issue a recheck of
the data. Read Documentation/md.txt in kernel source for details about
the exact procedure. My advice (if you still want to continue using
software raid) is that you run such a check before any add/grow or other
action in the future. Also, if the raid has been unused for a long while
it might be a good idea to recheck the data.

[snip]

I feel your pain. Massive data loss is the worst. I have had my share of
crashes. Once due to bad disk and no redundancy, the other time due to
good old stupidity.

Henrik Holst

  parent reply	other threads:[~2006-08-09 14:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08  0:36 Resize on dirty array? James Peverill
2006-08-08  0:46 ` Neil Brown
2006-08-08 19:25   ` James Peverill
2006-08-09  4:09     ` Neil Brown
2006-08-09 11:28       ` James Peverill
2006-08-09 11:37         ` Martin Schröder
2006-08-09 13:05           ` Mark Hahn
2006-08-09 13:33             ` James Peverill
2006-08-09 21:17               ` David Greaves
2006-08-10 17:44               ` dean gaudet
2006-08-12  1:11                 ` David Rees
     [not found]                 ` <72dbd3150608111810m4e4a2e07r5ddcee2132dd6d9a@mail.gmail.com>
     [not found]                   ` <Pine.LNX.4.64.0608111813250.29322@twinlark.arctic.org>
2006-08-12  2:05                     ` David Rees
2006-08-12  4:36                       ` Brad Campbell
2006-08-13 16:02                       ` dean gaudet
2006-08-30  7:30                         ` dean gaudet
2006-08-11 17:34             ` John Stoffel
2006-08-09 14:56         ` Henrik Holst [this message]
2006-08-12  7:22         ` Tuomas Leikola
2006-08-28  4:55           ` Neil Brown
2006-08-28  6:36             ` Mario 'BitKoenig' Holbe

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=44D9F7B5.1060000@idgmail.se \
    --to=henrik.holst@idgmail.se \
    --cc=jamespev@net1plus.com \
    --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 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.