linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Janek Kozicki <janek_listy@wp.pl>
Cc: linux-raid@vger.kernel.org
Subject: Re: some non critical problems... (1. mdadm segfault -> write-mostly, 2. smart?)
Date: Sat, 18 Sep 2010 14:01:31 -0400	[thread overview]
Message-ID: <4C94FE7B.1050009@tmr.com> (raw)
In-Reply-To: <20100914151347.3c387cbd@atak.bl.pg.gda.pl>

Janek Kozicki wrote:
> Janek Kozicki said:     (by the date of Wed, 8 Sep 2010 11:44:15 +0200)
>
>    
>> Umm... to reiterate one of my questions in above email:
>>
>>
>>      
>>> md1 : active raid1 sdc1[3](W) sdb1[5](W)
>>>        9767416 blocks super 1.0 [2/2] [UU]
>>>        bitmap: 6/150 pages [24KB], 32KB chunk
>>>        
>> Is it possible to disable that (W) --write-mostly flag? Does it
>> decrease performance or something, if both devices in the array are
>> set to (W) ?
>>      
> this seems to have fixed it:
>
>   mdadm --fail /dev/md1 /dev/sdb1
>   mdadm --remove /dev/md1 /dev/sdb1
>   mdadm --zero-superblock /dev/sdb1
>   mdadm --add --readwrite /dev/md1 /dev/sdb1
>
>
>    
Sorry for a late question, but in adding this to my notes, I realized I 
wasn't clear on why this flag moved to the other partitions. Are you, 
and if so can you clarify?


-- 
Bill Davidsen<davidsen@tmr.com>
   "We can't solve today's problems by using the same thinking we
    used in creating them." - Einstein


  reply	other threads:[~2010-09-18 18:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06 12:33 some non critical problems... (1. mdadm segfault -> write-mostly, 2. smart?) Janek Kozicki
2010-09-08  9:44 ` Janek Kozicki
2010-09-14 13:13   ` Janek Kozicki
2010-09-18 18:01     ` Bill Davidsen [this message]
2010-09-20 11:49       ` Janek Kozicki
     [not found] <20100906141324.1a19fa4d@atak.bl.pg.gda.pl>
2010-09-06 12:17 ` Janek Kozicki

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=4C94FE7B.1050009@tmr.com \
    --to=davidsen@tmr.com \
    --cc=janek_listy@wp.pl \
    --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).