All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Dabbs" <david@dabbs.net>
To: "'Vladimir V. Saveliev'" <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: RE: mongo_copy: cp: cannot stat `/mnt/testfs/testdir0-0-0/f92': Input/output error
Date: Wed, 4 Aug 2004 12:41:31 -0500	[thread overview]
Message-ID: <20040804174440.534DD15C57@mail03.powweb.com> (raw)
In-Reply-To: 


Something to add regarding the following errors from last night:

cp: cannot stat `/mnt/testfs/testdir0-0-0/f92': Input/output error

As part of my mongo benchmarking, I have added two steps before all other
processing:

1. Create a large number of directories on the benchmark device. These are
taken from a list of actual directories on my machine and are created under
the mount point for the test device e.g. my /etc becomes /mnt/testfs/etc. 

2. Create a large number of files on the test device. This is done using a
modified version of one of the mongo_ programs. Each file is simply created
by open(O_CREAT) then closed immediately. I can't tell you how many files
are created right now because I'm in the middle of running an ext3
benchmark, but it is a large number of files, each zero length. No shipped
mongo sources were changed, save mongo.pl (to include the new phases) and an
added LOG statement so I can watch each iteration command execute.

I spend a long time last night retesting mongo runs with and without the
MKDIRS and MKFILES phases to see if they had contributed to the errors, but
could not find any relationship.

I hope this helps in some way.


David






             reply	other threads:[~2004-08-04 17:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 17:41 David Dabbs [this message]
2004-08-04 18:11 ` mongo_copy: cp: cannot stat `/mnt/testfs/testdir0-0-0/f92': Input/output error Hans Reiser
2004-08-04 18:29   ` David Dabbs
  -- strict thread matches above, loose matches on Subject: below --
2004-08-04  6:55 David Dabbs
2004-08-04  8:40 ` Hans Reiser
2004-08-04  8:51   ` Vladimir V. Saveliev
2004-08-04  8:59     ` Hans Reiser
2004-08-04 12:51       ` Vladimir V. Saveliev
2004-08-04 18:38         ` mjt
2004-08-04 21:47           ` Hans Reiser
2004-08-04 22:46             ` Christophe Saout
2004-08-04 23:57               ` Hans Reiser
2004-08-05  0:06                 ` Christophe Saout
2004-08-05  0:14                   ` Lamont R. Peterson
2004-08-05  1:44                   ` Hans Reiser
2004-08-05  2:24                     ` Carl-Daniel Hailfinger
2004-08-05 13:38             ` Chris Mason
2004-08-04 14:14       ` David Dabbs
2004-08-04 17:38         ` Hans Reiser
2004-08-04 17:46           ` Chris Mason
2004-08-04 18:24           ` David Dabbs
2004-08-04 10:02     ` mjt

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=20040804174440.534DD15C57@mail03.powweb.com \
    --to=david@dabbs.net \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@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.