Jan Engelhardt wrote:
> Hi list,
>
>
> when a user does `mdadm -C /dev/md0 -l -n
> `, the array gets rebuilt for at least RAID1 and RAID5, even if
> the disk contents are most likely not of importance (otherwise we would
> not be creating a raid array right now). Could not this needless resy
On Apr 30 2007 13:54, [EMAIL PROTECTED] wrote:
>
>But then the array needs to keep track of where data is so that it knows
>what is "good" and what is "bad."
I assume it knows that, because you can reboot while an array is still
syncing and it Does The Right Thing. Furthermore, there is also the
But then the array needs to keep track of where data is so that it knows
what is "good" and what is "bad." Instead it takes the array to a known
good state to start out with and you don't have to start out with blank
disks.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECT
On Apr 30 2007 11:19, Dan Williams wrote:
>>
>> when a user does `mdadm -C /dev/md0 -l -n
>> `, the array gets rebuilt for at least RAID1 and RAID5, even if
>> the disk contents are most likely not of importance (otherwise we would
>> not be creating a raid array right now). Could not this need
On 4/30/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
Hi list,
when a user does `mdadm -C /dev/md0 -l -n
`, the array gets rebuilt for at least RAID1 and RAID5, even if
the disk contents are most likely not of importance (otherwise we would
not be creating a raid array right now). Could not t
Hi list,
when a user does `mdadm -C /dev/md0 -l -n
`, the array gets rebuilt for at least RAID1 and RAID5, even if
the disk contents are most likely not of importance (otherwise we would
not be creating a raid array right now). Could not this needless resync
be skipped - what do you think?
Change Kconfig objects from "menu, config" into "menuconfig" so
that the user can disable the whole feature without having to
enter the menu first.
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
drivers/md/Kconfig | 15 +--
1 file changed, 5 insertions(+), 10 deletions(-)
