From: "E.Gryaznova" <grev@namesys.com>
To: Hans Reiser <reiser@namesys.com>,
"Vladimir V. Saveliev" <vs@namesys.com>
Cc: Alexander Zarochentcev <zam@namesys.com>, reiserfs-list@namesys.com
Subject: Re: stale dk warning
Date: Wed, 25 Jan 2006 15:17:12 +0300 [thread overview]
Message-ID: <43D76C48.7060801@namesys.com> (raw)
In-Reply-To: <43D49B4C.5080406@namesys.com>
Hello,
shouldnt we also remove the warning [nikita-33281] ?
Jan 25 14:48:29 bones kernel: <4>reiser4[ent:hda8!(5047)]:
capture_anonymous_jno
des (fs/reiser4/plugin/file/file.c:1348)[nikita-33281]:
Jan 25 14:48:29 bones kernel: WARNING: anonymous jnode in writeback:
(69954 2216
63)
Jan 25 14:48:29 bones kernel:
Jan 25 14:48:29 bones kernel: <4>reiser4[ent:hda8!(5047)]:
capture_anonymous_jno
des (fs/reiser4/plugin/file/file.c:1348)[nikita-33281]:
Jan 25 14:48:29 bones kernel: WARNING: anonymous jnode in writeback:
(69954 2216
64)
Thanks,
Lena
Hans Reiser wrote:
>Hans Reiser wrote:
>
>
>
>>Vladimir V. Saveliev wrote:
>>
>>
>>
>>
>>
>>>Hello
>>>
>>>On Fri, 2006-01-20 at 14:28 -0600, Jake Maciejewski wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>>>In addition to the disable write barrier warning reported by Louis-David
>>>>Mitterrand on January 10th, with 2.6.15-1 I'm getting:
>>>>
>>>> <4>reiser4[dd(25448)]: update_stale_dk (fs/reiser4/search.c:1363)[nikita-38210]:
>>>> WARNING: stale dk
>>>>
>>>>The process varies. I've also seen the stale dk warning triggered by rsync and rm.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>This is harmless. I think we should remove this warning as well as the
>>>one about write barrier.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>Zam said he would change it
>>
>>
>>
>by "it" I refer to the write barrier warning, sorry for my imprecision....
>
>
>
>>to a notice. Zam, what happened to the patch?
>>
>>
>>
>>
>>
>>
>
>
>
>
>
prev parent reply other threads:[~2006-01-25 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 20:28 stale dk warning Jake Maciejewski
2006-01-23 8:29 ` Vladimir V. Saveliev
2006-01-23 8:59 ` Hans Reiser
2006-01-23 9:01 ` Hans Reiser
2006-01-23 22:50 ` Alexander Zarochentsev
2006-01-25 12:17 ` E.Gryaznova [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=43D76C48.7060801@namesys.com \
--to=grev@namesys.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.com \
--cc=zam@namesys.com \
/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.