Re: [PATCH 006 of 9] md: Remove the working_disks and failed_disks from raid5 state data.

NeilBrown wrote:
> They are not needed.
> conf->failed_disks is the same as mddev->degraded

By the way, `failed_disks' is more understandable than `degraded'
in this context.  "Degraded" usually refers to the state of the
array in question, when failed_disks > 0.

That to say: I'd rename degraded back to failed_disks, here and
in the rest of raid drivers... ;)

/mjt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 000 of 9] md: Introduction - assorted cleanup and minor fixes
    • From: NeilBrown <[email protected]>
  • [PATCH 006 of 9] md: Remove the working_disks and failed_disks from raid5 state data.
    • From: NeilBrown <[email protected]>

• Prev by Date: [PATCH 006 of 9] md: Remove the working_disks and failed_disks from raid5 state data.
• Next by Date: Re: 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
• Previous by thread: [PATCH 006 of 9] md: Remove the working_disks and failed_disks from raid5 state data.
• Next by thread: [PATCH 1/3] add-imacfb-docu-and-detection.patch
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]