All of lore.kernel.org
 help / color / mirror / Atom feed
From: Friedrich Lobenstock <fl@fl.priv.at>
To: Linux RAID Mailing Liste <linux-raid@vger.kernel.org>
Subject: Re: [BUG?] count of "Spare Devices" wrong after fail/remove/add
Date: Wed, 22 Jan 2003 09:46:24 +0100	[thread overview]
Message-ID: <3E2E5A60.5070309@fl.priv.at> (raw)
In-Reply-To: <15918.7346.888218.690481@notabene.cse.unsw.edu.au>

Neil Brown wrote:
> On Tuesday January 21, fl@fl.priv.at wrote:
>>  Active Devices : 2
>>Working Devices : 2
>>  Failed Devices : 0
>>   Spare Devices : 2
>>
>>
>>     Number   Major   Minor   RaidDevice State
>>        0       3        1        0      active sync   /dev/hda1
>>        1      22        1        1      active sync   /dev/hdc1
>>            UUID : d876333b:694e852b:e9a6f40f:0beb90f9
>>
>>I do wounder why I've got 2 spare drives despite the fact that I
>>did not add any. I've just got two drives in this raid1 that's it.
> 
> Yes, it's probably a bug in the kernel code. The counting in the 2.4 code is very
> clumsy.  I think it is benign so it wont be fixed.  The code in 2.5 is
> very different and shouldn't have this problem.

Ok. Just wanted to let you know.


>>PS: Array Size : 40209024 (38.35 GiB 41.22 GB)
>>should IMHO be
>>     Array Size : 40209024 (38.35 GiB 40.21 GB)
> 
> I disgree. An array side of 40209024 means that many kibibytes.
> i.e. 40209024 * 1024 which is
>    41174040576  bytes.
> 

Hmmm...why don't we forget about this kibibytes sh.. anyways,
it's not worth the troubles IMHO.

-- 
MfG / Regards
Friedrich Lobenstock


      reply	other threads:[~2003-01-22  8:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-21  1:20 [BUG?] count of "Spare Devices" wrong after fail/remove/add Friedrich Lobenstock
2003-01-22  4:23 ` Neil Brown
2003-01-22  8:46   ` Friedrich Lobenstock [this message]

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=3E2E5A60.5070309@fl.priv.at \
    --to=fl@fl.priv.at \
    --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.