All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: Adrian Phillips <a.phillips@met.no>, reiserfs-list@namesys.com
Subject: Re: 3.5.34: reiserfs_file_write: item has been moved
Date: Wed, 14 Aug 2002 13:47:45 +0400	[thread overview]
Message-ID: <3D5A2741.3010904@namesys.com> (raw)
In-Reply-To: 20020814125002.A28182@namesys.com

Oleg Drokin wrote:

>Hello!
>
>On Wed, Aug 14, 2002 at 07:49:23AM +0200, Adrian Phillips wrote:
>
>  
>
>>I have got the following error 4 times in the space of about a week :-
>>reiserfs_file_write: item has been moved while we were in copy_from_user (appending to the direct item)
>>Should I be worried ? :-)
>>    
>>
>
>This is not an error, but just a informational message instead.
>You should not be worried at all.
>
>Bye,
>    Oleg
>
>
>  
>
Of what possible value is this message?  Please remove the message in 
the next patch set.

-- 
Hans




      reply	other threads:[~2002-08-14  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14  5:49 3.5.34: reiserfs_file_write: item has been moved Adrian Phillips
2002-08-14  8:50 ` Oleg Drokin
2002-08-14  9:47   ` 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=3D5A2741.3010904@namesys.com \
    --to=reiser@namesys.com \
    --cc=a.phillips@met.no \
    --cc=green@namesys.com \
    --cc=reiserfs-list@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.