All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Phillips <a.phillips@met.no>
To: reiserfs-list@namesys.com
Subject: 3.5.34: reiserfs_file_write: item has been moved
Date: 14 Aug 2002 07:49:23 +0200	[thread overview]
Message-ID: <wvu1ly56sc.fsf@freeze.oslo.dnmi.no> (raw)


Kernel 2.2.20 with the following patches :-
 linux_patches/patch-2.2.21-rc4.bz2
 reiserfs/linux-2.2.19-reiserfs-3.5.34-patch-buffer-300.bz2
 linux-2.2.18-rawio.patch
 lvm/lvm-1.0.4-2.2.21-rc4.patch
 ide-2.2.21-rc4.patch.bz2
 max_tasks.patch

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 ? :-)

[I'll can schedule a reiserfsck early tomorrow morning if this is
necessary but I'd rather wait to hear if this indicates corruption
before doing that]

Sincerely,

Adrian Phillips

-- 
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now?  [OK]

             reply	other threads:[~2002-08-14  5:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14  5:49 Adrian Phillips [this message]
2002-08-14  8:50 ` 3.5.34: reiserfs_file_write: item has been moved Oleg Drokin
2002-08-14  9:47   ` Hans Reiser

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=wvu1ly56sc.fsf@freeze.oslo.dnmi.no \
    --to=a.phillips@met.no \
    --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.