All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Dabbs" <david@dabbs.net>
To: 'ReiserFS List' <reiserfs-list@namesys.com>
Subject: Was able to reproduce "cp: cannot stat file.x: Input/output error"
Date: Thu, 5 Aug 2004 23:54:38 -0500	[thread overview]
Message-ID: <20040806045809.E195B15C9F@mail03.powweb.com> (raw)


Ran 

./mongo.pl INFO_R4=rc2-mm2 FSTYPE=reiser4 LOG=/home/ddabbs/mongo/reiser4.log
dev=/dev/hdb1 dir=/mnt/testfs file_size=8000 bytes=512000000 NPROC=3
REP_COUNTER=3 SYNC=off WRITE_BUFFER=4096 GAMMA=0.0 DD_MBCOUNT=768
PHASE_MKDIRS=on PHASE_MKFILES=on PHASE_COPY=cp PHASE_OVERWRITE=on
PHASE_APPEND=on PHASE_READ=find PHASE_DELETE=rm PHASE_MODIFY=on
MAX_FNAME_LEN=23 RUN

Somewhere during PHASE_COPY, errors similar to the following (the ones I saw
the other day) spewed across the terminal:

cp: cannot stat
`/mnt/testfs/testdir0-0-0/d00000000/d000000000000000022/d0000000000023/f1461
8.d': Input/output error

I can cat and ls the file:

-rw-r--r--  1 root root 7512 2004-08-05 21:54
/mnt/testfs/testdir0-0-0/d00000000/d000000000000000022/d0000000000023/f14622
.c

Other than the following log items

...
Aug  5 22:06:09 linux kernel: reiser4[cp(1088)]: cbk_level_lookup
(fs/reiser4/search.c:1033)[vs-3533]:
Aug  5 22:06:09 linux kernel: WARNING: Keys are inconsistent. Fsck?
Aug  5 22:06:09 linux kernel: ]: key_warning
(fs/reiser4/plugin/object.c:97)[nikita-717]:
Aug  5 22:06:09 linux kernel: WARNING: Error for inode 137388 (-5)
Aug  5 22:06:09 linux kernel: reiser4[cp(1087)]: cbk_level_lookup
(fs/reiser4/search.c:1033)[vs-3533]:
Aug  5 22:06:09 linux kernel: WARNING: Keys are inconsistent. Fsck?
Aug  5 22:06:09 linux kernel: reiser4[cp(1087)]: key_warning
(fs/reiser4/plugin/object.c:97)[nikita-717]:
Aug  5 22:06:09 linux kernel: WARNING: Error for inode 137404 (-5)
Aug  5 22:06:09 linux kernel: reiser4[cp(1087)]: cbk_level_lookup
(fs/reiser4/search.c:1033)[vs-3533]:
Aug  5 22:06:09 linux kernel: WARNING: Keys are inconsistent. Fsck?
...

I could find nothing to indicate there was any sort of disk/ide hardware
error. Yes, there were some of the (apparently) innocuous driver artifacts
as Nikita called them.

All the relevant info I could pull together is available at
http://dabbs.net/reiser4/stat_error_mongo.tar.bz2. Other than gathering this
info, I have left the system as is. Let me know if you need more info, for
me to poke around or run commands, retest, etc.

BTW, built with yesterday's r4 snapshot.

David



             reply	other threads:[~2004-08-06  4:54 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-06  4:54 David Dabbs [this message]
2004-08-06  7:31 ` Was able to reproduce "cp: cannot stat file.x: Input/output error" mjt
  -- strict thread matches above, loose matches on Subject: below --
2004-08-06  6:53 David Dabbs
2004-08-06 15:51 ` Vladimir V. Saveliev
2004-08-06 17:10   ` Philippe Gramoullé
2004-08-06 17:39     ` Vladimir V. Saveliev
2004-08-06 19:06       ` Philippe Gramoullé
2004-08-07  4:14       ` Hans Reiser
2004-08-06 17:46     ` David Dabbs
2004-08-06 19:11       ` Philippe Gramoullé
2004-08-07  4:15       ` Hans Reiser
2004-08-07  6:46         ` David Dabbs
2004-08-07  7:49           ` Hans Reiser
2004-08-08  2:54             ` David Dabbs
2004-08-10  3:21             ` Valdis.Kletnieks
2004-08-10  8:31               ` Hans Reiser
2004-08-10 15:41                 ` Valdis.Kletnieks
2004-08-10  9:20               ` Alex Zarochentsev
2004-08-10 17:35                 ` Hans Reiser
2004-08-10 17:42                   ` David Dabbs
2004-08-10 17:46                     ` Hans Reiser
2004-08-10 18:05                   ` Alex Zarochentsev
2004-08-10 19:55                     ` Hans Reiser
2004-08-10 20:41                       ` Alex Zarochentsev
2004-08-06 17:51     ` Alex Zarochentsev
2004-08-06 19:10       ` Philippe Gramoullé
     [not found] <4115A979.5090002@namesys.com>
2004-08-08  7:07 ` David Dabbs
2004-08-08 18:08   ` Hans Reiser
2004-08-08 19:09     ` David Dabbs
2004-08-09  6:17       ` Hans Reiser
2004-08-08 21:40         ` David Dabbs
2004-08-09  0:01           ` Hans Reiser
2004-08-09  1:55             ` David Dabbs
2004-08-09 17:43               ` Hans Reiser
2004-08-09 18:32                 ` David Dabbs
2004-08-09  2:38             ` David Dabbs
2004-08-09 17:59               ` Alex Zarochentsev
2004-08-09 18:22                 ` David Dabbs
2004-08-09 18:42                   ` Alex Zarochentsev
2004-08-09 15:13     ` Nikita Danilov
2004-08-09 17:48       ` Hans Reiser
     [not found] <20040810205450.GU9811@backtop.namesys.com>
2004-08-10 21:06 ` David Dabbs
2004-08-10 21:06   ` Alex Zarochentsev
2004-08-10 21:19     ` David Dabbs
2004-08-11 10:03       ` Vladimir V. Saveliev
2004-08-10 21:26     ` David Dabbs
     [not found] <411944EF.7000504@namesys.com>
2004-08-10 22:05 ` David Dabbs

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=20040806045809.E195B15C9F@mail03.powweb.com \
    --to=david@dabbs.net \
    --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.