From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: Tom Vier <tmv@comcast.net>, reiserfs-list@namesys.com
Subject: Re: anyone port data-logging patches to -rc3?
Date: 23 May 2003 08:28:19 -0400 [thread overview]
Message-ID: <1053692899.5455.44.camel@tiny.suse.com> (raw)
In-Reply-To: <20030523094633.GA1005@namesys.com>
On Fri, 2003-05-23 at 05:46, Oleg Drokin wrote:
> Hello!
>
> On Thu, May 22, 2003 at 08:30:33PM -0400, Tom Vier wrote:
>
> > i started to, but the change in reiserfs/inode.c:reiserfs_truncate_file() is
> > more than i want to play w/ (my first time looking at reiserfs code). i
> > don't want to trash my fs. 8)
>
> Ok, replacement patches are in
> ftp://ftp.namesys.com/pub/reiserfs-for-2.4/testing/data-logging-and-quota-2.4.21-rc3/
>
> I tested it in all journaling modes and found zero problems. (have not tried crashing it,
> though).
>
Thanks Oleg, I'm integrating all of this today.
> Chris: I optimized reiserfs_truncate_file() a bit so that it won't do kmap() on the same page twice.
> Also I think I did correct thing with reiserfs_commit_for_tail/reiserfs_commit_for_inode stuff,
> but I want you to take a look anyway.
Will do.
> And BTW, I think this "do O_DIRECT stuff on ordered/datalogging fs, receive error from write(2)" is counter-intuitive.
> what do you think about just only setting reiserfs_address_space_operations->direct_IO to non-NULL
> in case of writeback mount?
They'd get the same error, just sooner. I'm more inclined to fix things
so that data=ordered works with O_DIRECT, lets see what I can come up
with.
> Also probably we do not want to allow remounting with different data-logging mode,
> may be we should even add a check in reiserfs_remount() and spit out an error in such a case?
Jeff Mahoney managed to trigger a race by switching between data=journal
and the other modes. All we really need to do is be able to switch data
mode when remounting from readonly to rw (as in for the root FS), so
I'll limit the remounting code to that.
-chris
next prev parent reply other threads:[~2003-05-23 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 0:30 anyone port data-logging patches to -rc3? Tom Vier
2003-05-23 9:46 ` Oleg Drokin
2003-05-23 12:28 ` Chris Mason [this message]
2003-05-23 12:36 ` Oleg Drokin
2003-05-23 12:44 ` Chris Mason
2003-05-23 12:54 ` Oleg Drokin
2003-05-23 16:15 ` Philippe Gramoullé
2003-05-23 16:24 ` Oleg Drokin
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=1053692899.5455.44.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=tmv@comcast.net \
/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.