From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: David Dabbs <david@dabbs.net>,
"'Vladimir V. Saveliev'" <vs@namesys.com>,
reiserfs-list@namesys.com
Subject: Re: mongo_copy: cp: cannot stat `/mnt/testfs/testdir0-0-0/f92': Input/output error
Date: Wed, 04 Aug 2004 13:46:41 -0400 [thread overview]
Message-ID: <1091641601.4791.50.camel@watt.suse.com> (raw)
In-Reply-To: <41111F2C.6090805@namesys.com>
On Wed, 2004-08-04 at 13:38, Hans Reiser wrote:
> Please do whatever you can to reproduce this. We are going to delay
> release by one day to see if it can be reproduced. Vs thinks it might
> be a hardware problem, I am not so optimistic, what are your thoughts?
>
If it currently passes all of your internal tests, and the disk format
is fixed, I'd release it. There are going to be bugs found, pretty much
everyone expects v4 to go through a churning period.
-chris
next prev parent reply other threads:[~2004-08-04 17:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 6:55 mongo_copy: cp: cannot stat `/mnt/testfs/testdir0-0-0/f92': Input/output error 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 [this message]
2004-08-04 18:24 ` David Dabbs
2004-08-04 10:02 ` mjt
-- strict thread matches above, loose matches on Subject: below --
2004-08-04 17:41 David Dabbs
2004-08-04 18:11 ` Hans Reiser
2004-08-04 18:29 ` 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=1091641601.4791.50.camel@watt.suse.com \
--to=mason@suse.com \
--cc=david@dabbs.net \
--cc=reiser@namesys.com \
--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.