From: "David Dabbs" <david@dabbs.net>
To: 'Alex Zarochentsev' <zam@namesys.com>
Cc: 'Hans Reiser' <reiser@namesys.com>,
'ReiserFS List' <reiserfs-list@namesys.com>
Subject: RE: Was able to reproduce "cp: cannot stat file.x: Input/output error"
Date: Tue, 10 Aug 2004 16:19:29 -0500 [thread overview]
Message-ID: <20040810212733.4BA8315C56@mail03.powweb.com> (raw)
In-Reply-To: <20040810210630.GV9811@backtop.namesys.com>
> -----Original Message-----
> From: Alex Zarochentsev [mailto:zam@namesys.com]
> Sent: Tuesday, August 10, 2004 4:07 PM
> To: David Dabbs
> Cc: 'Hans Reiser'; 'ReiserFS List'
> Subject: Re: Was able to reproduce "cp: cannot stat file.x: Input/output
> error"
>
> On Tue, Aug 10, 2004 at 04:06:24PM -0500, David Dabbs wrote:
> >
> > I have been running benchmarks with SYNC=off, as the mongo page
> > recommends against doing so. In configs where SYNC=ON we would
> > omit the syncs/waits, yes?
>
> not sure. metadata need to be synched still.
>
> Alex.
Saw following recently on LKML re. ext3. Does r4 O_SYNC not sync metadata?
From Theodore Ts'o
Subject Re: ext3 and SPEC SFS Run rules.
On Mon, Jul 26, 2004 at 10:12:01AM +0100, Tigran Aivazian wrote:
> On Mon, 26 Jul 2004, Andrew Morton wrote:
> > ext3 should be fully syncing data and metadata for both fsync()
> > and O_SYNC writes in all three journalling modes.
> > If not, that's a big bug.
David
next prev parent reply other threads:[~2004-08-10 21:19 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040810205450.GU9811@backtop.namesys.com>
2004-08-10 21:06 ` Was able to reproduce "cp: cannot stat file.x: Input/output error" David Dabbs
2004-08-10 21:06 ` Alex Zarochentsev
2004-08-10 21:19 ` David Dabbs [this message]
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
[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
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é
-- 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=20040810212733.4BA8315C56@mail03.powweb.com \
--to=david@dabbs.net \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=zam@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.