public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Shailendra Tripathi <stripathi@agami.com>
To: Timothy Shimmin <tes@sgi.com>
Cc: cousins@umit.maine.edu,
	"\"xfs@oss.sgi.com\" <xfs@oss.sgi.com>" <xfs@oss.sgi.com>
Subject: Re: swidth with mdadm and RAID6
Date: Tue, 19 Sep 2006 12:14:36 +0530	[thread overview]
Message-ID: <450F91D4.1030606@agami.com> (raw)
In-Reply-To: <450F7C1E.5020300@sgi.com>


Hi Tim,

> I'm not that au fait with RAID and md, but looking at what you wrote,
> Shailendra, and the md code, instead of your suggestions
> (what I think are your suggestions:) of:
> 
> (1) subtracting parity from md.raid_disk (instead of md.nr_disks)
>     where we work out parity by switching on md.level
> or
> (2) using directly: (md.nr_disks - md.spares);
> 
> that instead we could use:
> (3) using directly:  md.active_disks
> 
> i.e.
> *swidth = *sunit * md.active_disks;
> I presume that active is the working non spares and non-parity.
> 
> Does that make sense?
       I agree with you that for operational raid since there would not 
be any faulty disks, active disks should the number of disks. However, I 
am just concerned that active disks tracks live disks (not failed 
disks). If we ever used these commands when the system has faulty drive, 
the information returned wouldn't be correct. Though, from XFS 
perspective, I can't think of where it can happen.
       I would still say that lets rely more on raid_disks to be more 
conservative, just my choice.

  reply	other threads:[~2006-09-19  6:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fc.004c4d192b2c45a93b9aca00fc3f0f38.2b2c4b4d@umit.maine.edu>
2006-09-18 20:28 ` swidth with mdadm and RAID6 Steve Cousins
2006-09-18 20:44 ` Steve Cousins
2006-09-18 21:06   ` Shailendra Tripathi
2006-09-18 22:13   ` Shailendra Tripathi
2006-09-19  5:11     ` Timothy Shimmin
2006-09-19  6:44       ` Shailendra Tripathi [this message]
2006-09-19  7:02         ` Timothy Shimmin
     [not found] <fc.004c4d192b3470d73b9aca0029fcf469.2b349301@umit.maine.edu>
2006-09-19 17:52 ` Steve Cousins
2006-09-19 19:22   ` Steve Cousins
2006-09-19 20:19     ` Shailendra Tripathi
     [not found] <fc.004c4d192b2da8e03b9aca0078918430.2b2da8e5@umit.maine.edu>
2006-09-19 16:36 ` Steve Cousins
2006-09-19 16:58   ` Shailendra Tripathi
2006-09-19 17:13   ` Steve Cousins
     [not found] <fc.004c4d192b2a17d13b9aca00b4f73745.2b2a26d7@umit.maine.edu>
2006-09-18 15:33 ` Steve Cousins
2006-09-18 18:10   ` Shailendra Tripathi
2006-09-18 18:19     ` Shailendra Tripathi
2006-09-15 21:07 Steve Cousins
2006-09-15 23:49 ` Peter Grandi
2006-09-18 14:50 ` Shailendra Tripathi

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=450F91D4.1030606@agami.com \
    --to=stripathi@agami.com \
    --cc=cousins@umit.maine.edu \
    --cc=tes@sgi.com \
    --cc=xfs@oss.sgi.com \
    /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