From: Hans Reiser <reiser@namesys.com>
To: "E.Gryaznova" <grev@namesys.com>
Cc: Louis-David Mitterrand <vindex+lists-reiserfs-list@apartia.org>,
reiserfs-list@namesys.com
Subject: Re: reiser4 warning?
Date: Wed, 11 Jan 2006 00:16:45 -0800 [thread overview]
Message-ID: <43C4BEED.9040503@namesys.com> (raw)
In-Reply-To: <43C4BCF2.1070000@namesys.com>
E.Gryaznova wrote:
> Hello.
>
>
> Louis-David Mitterrand wrote:
>
>> Hello,
>>
>> When rebooting a server I catched this in the logs:
>>
>> Jan 10 18:13:55 zenon kernel: <4>reiser4[apache-perl(6359)]:
>> disable_write_barrier (fs/reiser4/wander.c:233)[zam-1055]:
>> Jan 10 18:13:55 zenon kernel: WARNING: disabling write barrier
>>
>> Is it bad?
>>
>>
> No. You may ignore this warning.
>
> Thanks,
> Lena.
>
>> (using 2.6.14 patch)
>>
>>
>>
>>
>
>
>
Always explain things like this to users, don't just tell them to ignore
it, tell them why they can ignore it. Zam, please send in the patch to
change it to a notice instead of warning.
Hans
prev parent reply other threads:[~2006-01-11 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 21:18 reiser4 warning? Louis-David Mitterrand
2006-01-11 8:08 ` E.Gryaznova
2006-01-11 8:16 ` Hans Reiser [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=43C4BEED.9040503@namesys.com \
--to=reiser@namesys.com \
--cc=grev@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=vindex+lists-reiserfs-list@apartia.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.