linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steve Fairbairn" <steve@fairbairn-family.com>
To: 'Steve Fairbairn' <steve@fairbairn-family.com>,
	linux-raid@vger.kernel.org
Subject: RE: Disk failure during grow, what is the current state.
Date: Wed, 6 Feb 2008 17:55:42 -0000	[thread overview]
Message-ID: <058101c868e9$7dc636f0$0603a8c0@meanmachine> (raw)
In-Reply-To: <047a01c868d1$821f92e0$0603a8c0@meanmachine>

> > -----Original Message-----
> > From: Steve Fairbairn [mailto:steve@fairbairn-family.com]
> > Sent: 06 February 2008 15:02
> > To: 'Nagilum'
> > Subject: RE: Disk failure during grow, what is the current state.
> > 
> > 
> >      Array Size : 1953535744 (1863.04 GiB 2000.42 GB)
> >   Used Dev Size : 488383936 (465.76 GiB 500.11 GB)
> > 
> > Surely the added disk should now been added to the Array
> > Size?  5 * 500GB is 2500GB, not 2000GB.  This is why I don't 
> > think the reshape has continued.  As for speeding up because 
> > of no IO badwidth, this also doesn't actually hold very true, 
> > because the system was at a point of not being used anyway 
> > before I added the disk, and I didn't unmount the drive until 
> > this morning after it claimed it had finished doing anything.
> > 

Thanks again to Alex for his comments.  I've just rebooted the box, and
the reshape has continued on the degraded array and an RMA has been
raised for the faulty disk.

Thanks,

Steve.

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.19.20/1261 - Release Date:
05/02/2008 20:57
 


  reply	other threads:[~2008-02-06 17:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 15:04 FW: Disk failure during grow, what is the current state Steve Fairbairn
2008-02-06 17:55 ` Steve Fairbairn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-06 12:58 Steve Fairbairn
2008-02-06 14:34 ` Nagilum

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='058101c868e9$7dc636f0$0603a8c0@meanmachine' \
    --to=steve@fairbairn-family.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).