"raid array not clean" messages

"raid array not clean" messages

[fibre raid]

Hi,

Right now, whenever a parity RAID (like raid5 or raid6) is created,
something (md itself or mdadm) is dumping a message to the console
about "raid array not clean, background synchronization...". I want to
disable these messages but cannot find a way to do so. Can you advise?
thanks!

-Thomas

Re: "raid array not clean" messages

[SandeepKsinha]

Hi,

On Thu, May 21, 2009 at 10:06 AM, fibre raid <fibreraid@gmail.com> wrote:
> Hi,
>
> Right now, whenever a parity RAID (like raid5 or raid6) is created,
> something (md itself or mdadm) is dumping a message to the console
> about "raid array not clean, background synchronization...". I want to
> disable these messages but cannot find a way to do so. Can you advise?
> thanks!
>

Do you mean creating a new array or assembling an existing one ?

AFAIK,
You can get this message when you are assimilating an existing array
if you array is not clean and needs recovery.

But ideally you should not get this when creating a new array.
> -Thomas
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Regards,
Sandeep.





 	
“To learn is to change. Education is a process that changes the learner.”
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: "raid array not clean" messages

[fibre raid]

I receive this message to the console when creating a new array and running it.

-Thomas

On Wed, May 20, 2009 at 11:49 PM, SandeepKsinha <sandeepksinha@gmail.com> wrote:
> Hi,
>
> On Thu, May 21, 2009 at 10:06 AM, fibre raid <fibreraid@gmail.com> wrote:
>> Hi,
>>
>> Right now, whenever a parity RAID (like raid5 or raid6) is created,
>> something (md itself or mdadm) is dumping a message to the console
>> about "raid array not clean, background synchronization...". I want to
>> disable these messages but cannot find a way to do so. Can you advise?
>> thanks!
>>
>
> Do you mean creating a new array or assembling an existing one ?
>
> AFAIK,
> You can get this message when you are assimilating an existing array
> if you array is not clean and needs recovery.
>
> But ideally you should not get this when creating a new array.
>> -Thomas
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
>
>
> --
> Regards,
> Sandeep.
>
>
>
>
>
>
> “To learn is to change. Education is a process that changes the learner.”
>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: "raid array not clean" messages

[Christopher Chen]

Just curious why you would like to disable the messages. When you  
create a raid 5/6 array, until parity is fully calculated and written  
your array /will/ be dirty!

Time flies like an arrow.
Fruit flies like a banana.

On May 20, 2009, at 21:49, SandeepKsinha <sandeepksinha@gmail.com>  
wrote:

> Hi,
>
> On Thu, May 21, 2009 at 10:06 AM, fibre raid <fibreraid@gmail.com>  
> wrote:
>> Hi,
>>
>> Right now, whenever a parity RAID (like raid5 or raid6) is created,
>> something (md itself or mdadm) is dumping a message to the console
>> about "raid array not clean, background synchronization...". I want  
>> to
>> disable these messages but cannot find a way to do so. Can you  
>> advise?
>> thanks!
>>
>
> Do you mean creating a new array or assembling an existing one ?
>
> AFAIK,
> You can get this message when you are assimilating an existing array
> if you array is not clean and needs recovery.
>
> But ideally you should not get this when creating a new array.
>> -Thomas
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux- 
>> raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
>
>
> -- 
> Regards,
> Sandeep.
>
>
>
>
>
>
> “To learn is to change. Education is a process that changes the lear 
> ner.”
> --
> To unsubscribe from this list: send the line "unsubscribe linux- 
> raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: "raid array not clean" messages

[fibre raid]

I have no problem with this message being written to
/var/log/messages, but in our case, we don't want it on the console.
We want the console to only be there for kernel crash dumps (if they
occur), nothing else.

-Thomas

On Wed, May 20, 2009 at 11:56 PM, Christopher Chen <muffaleta@gmail.com> wrote:
> Just curious why you would like to disable the messages. When you create a
> raid 5/6 array, until parity is fully calculated and written your array
> /will/ be dirty!
>
> Time flies like an arrow.
> Fruit flies like a banana.
>
> On May 20, 2009, at 21:49, SandeepKsinha <sandeepksinha@gmail.com> wrote:
>
>> Hi,
>>
>> On Thu, May 21, 2009 at 10:06 AM, fibre raid <fibreraid@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> Right now, whenever a parity RAID (like raid5 or raid6) is created,
>>> something (md itself or mdadm) is dumping a message to the console
>>> about "raid array not clean, background synchronization...". I want to
>>> disable these messages but cannot find a way to do so. Can you advise?
>>> thanks!
>>>
>>
>> Do you mean creating a new array or assembling an existing one ?
>>
>> AFAIK,
>> You can get this message when you are assimilating an existing array
>> if you array is not clean and needs recovery.
>>
>> But ideally you should not get this when creating a new array.
>>>
>>> -Thomas
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>
>>
>>
>> --
>> Regards,
>> Sandeep.
>>
>>
>>
>>
>>
>>
>> “To learn is to change. Education is a process that changes the learner.”
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: "raid array not clean" messages

[Neil Brown]

On Thursday May 21, fibreraid@gmail.com wrote:
> I have no problem with this message being written to
> /var/log/messages, but in our case, we don't want it on the console.
> We want the console to only be there for kernel crash dumps (if they
> occur), nothing else.

I feel you are a bit optimistic...

But I guess what you are really asking is for the message to be
printed with a lower priority than KERN_ERR - maybe KERN_INFO.
It is in drivers/md/md.c at the end of analyze_sbs.

You would need to compile a new kernel to achieve that.

NeilBrown

Re: "raid array not clean" messages

[Bill Davidsen]

Neil Brown wrote:
> On Thursday May 21, fibreraid@gmail.com wrote:
>   
>> I have no problem with this message being written to
>> /var/log/messages, but in our case, we don't want it on the console.
>> We want the console to only be there for kernel crash dumps (if they
>> occur), nothing else.
>>     
>
> I feel you are a bit optimistic...
>
> But I guess what you are really asking is for the message to be
> printed with a lower priority than KERN_ERR - maybe KERN_INFO.
> It is in drivers/md/md.c at the end of analyze_sbs.
>
> You would need to compile a new kernel to achieve that.
>   

Since it is actually informational rather than an error, I would think 
KERN_INFO would be more correct for all users. Then people who want 
stuff like that can play with their syslog configuration to see it if 
they want. I agree that conditions which do not require intervention to 
correct them are not errors, messages about them are for informational 
purposes. Hardware errors and failure in unexpected places don't need to 
bother the operator (for whatever definition of operator you like).

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc

"You are disgraced professional losers. And by the way, give us our money back."
    - Representative Earl Pomeroy,  Democrat of North Dakota
on the A.I.G. executives who were paid bonuses  after a federal bailout.