From: Hans Reiser <reiser@namesys.com>
To: David Dabbs <david@dabbs.net>
Cc: 'ReiserFS List' <reiserfs-list@namesys.com>
Subject: Re: Was able to reproduce "cp: cannot stat file.x: Input/output error"
Date: Sat, 07 Aug 2004 00:49:43 -0700 [thread overview]
Message-ID: <41148997.4070404@namesys.com> (raw)
In-Reply-To: <20040807065039.5BF4E15CBC@mail03.powweb.com>
David Dabbs wrote:
>
>
>>-----Original Message-----
>>From: Hans Reiser [mailto:reiser@namesys.com]
>>Sent: Friday, August 06, 2004 11:16 PM
>>To: David Dabbs
>>Cc: 'Philippe Gramoullé'; 'ReiserFS List'
>>Subject: Re: Was able to reproduce "cp: cannot stat file.x: Input/output
>>error"
>>
>>David Dabbs wrote:
>>
>>
>>
>>>i.e.
>>>
>>> "%.c", '`' + (char) rnd
>>>
>>>If you exceed 26 then you will generate filenames that may cause
>>>
>>>
>>problems.
>>
>>
>>>
>>>
>>Problems that indicate reiser4 bugs or mongo bugs?
>>
>>
>>
>
>Mongo. The pipe character is not legal in a filename as an example.
>
>I think I have discovered the problem - unless there was a reason mongo was
>issuing mount/unmount commands at the start/end of a mongo 'run' as well as
>before/after _each phase_. I just removed the mount/unmount calls that
>bracket each phase execution and I am not seeing the errors. In addition,
>reiser4 is running much faster. For instance, with the 'extra'
>mount/unmounts r4 reported a REAL TIME stats of approximately 700 & 40 for
>CREATE and MKFILES. After removing the mount/un calls it is reporting 224 &
>50 REAL TIME.
>
>
can you quote code more in these emails?
>I will reboot and run a sequence of each of the filesystem configs overnight
>and see what happens.
>
>David
>
>
>
>
>
>
>
Probably someone wanted to separate the measurement of the phases. It
has been a while since I read mongo.....
next prev parent reply other threads:[~2004-08-07 7:49 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 6:53 Was able to reproduce "cp: cannot stat file.x: Input/output error" 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 [this message]
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] <411944EF.7000504@namesys.com>
2004-08-10 22:05 ` David Dabbs
[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] <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
-- strict thread matches above, loose matches on Subject: below --
2004-08-06 4:54 David Dabbs
2004-08-06 7:31 ` 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=41148997.4070404@namesys.com \
--to=reiser@namesys.com \
--cc=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.