All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Christian Mayrhuber <christian.mayrhuber@gmx.net>,
	reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: Data-logging and md as / fs bug
Date: 08 May 2003 09:31:25 -0400	[thread overview]
Message-ID: <1052400685.14617.489.camel@tiny.suse.com> (raw)
In-Reply-To: <200305062156.27595.Dieter.Nuetzel@hamburg.de>

On Tue, 2003-05-06 at 15:56, Dieter Nützel wrote:
> Am Dienstag, 6. Mai 2003 21:44 schrieb Chris Mason:
> > On Tue, 2003-05-06 at 15:34, Christian Mayrhuber wrote:
> > > Hi,
> > >
> > > I've patched 2.4.21-rc1 with the following:
> 
> I have nearly the same running on-top of 2.4.21-pre6-jam1
> 
> > > 02-akpm-b_journal_head-1.diff
> 
> Needed?
> 

Yes

> > > 03-2.4.21-rc1-relocation-6.diff
> > > 04-reiserfs-sync_fs-1.diff
> > > 05-2.4.21-pre6-data-logging-36.diff
> > > 06-logging-export.diff
> 
> Needed?

06-logging-export is only needed if you want to compile reiserfs as a
module

> 
> > > 06-write_times.diff
> 
> I have -aa;-)
> 
> > > 07-quota-v2-2.4.21.diff
> > > 08-2.4.21-pre6-reiserfs-quota-26.diff
> 
> Both not, yet.
> 
> > > 09-kinoded-8.diff
> > > 10-reiserfs-quota-link-fix.diff
> 
> Needed?
> 

Only if you are using quota

> 11.dirty-inodes-for-kinoded.diff

This is flawed, since it does not include any way to throttle inode
changes.  kinoded can't keep up with an active FS, and major changes are
needed to fix that.  I've dropped it for now.

> iget5_locked_for_2.4.21-pre5-datalogging.diff

Not needed any more.

> search_reada-4.diff
> 
> Usefull?

Good for desktop workload, needs additional changes for random io.

-chris



  reply	other threads:[~2003-05-08 13:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-03  0:07 Data-logging for 2.4.21-rc1+ (again) Manuel Krause
2003-05-03 10:31 ` Oleg Drokin
2003-05-06 19:34   ` Data-logging and md as / fs bug Christian Mayrhuber
2003-05-06 19:44     ` Chris Mason
2003-05-06 19:56       ` Dieter Nützel
2003-05-08 13:31         ` Chris Mason [this message]
2003-05-09 20:21           ` Manuel Krause
2003-05-11 12:58             ` Chris Mason
2003-05-12  7:29           ` Oleg Drokin
2003-05-13 14:15             ` Manuel Krause
2003-05-13 14:25               ` Oleg Drokin
2003-05-13 15:00                 ` Manuel Krause
2003-05-13 14:59                   ` Oleg Drokin
2003-05-13 15:39                     ` Manuel Krause
2003-05-13 15:42                       ` Oleg Drokin
2003-05-15 13:31                         ` Manuel Krause
2003-05-13 21:52               ` Newsmail
2003-05-13 22:18                 ` Christian Mayrhuber
2003-05-14  5:40                 ` Oleg Drokin
2003-05-06 20:53       ` Christian Mayrhuber
2003-05-06 21:22         ` Chris Mason
2003-05-07 12:34         ` Chris Mason
2003-05-07 14:41           ` Christian Mayrhuber
2003-05-07 14:43             ` Chris Mason
2003-05-07 14:52               ` Christian Mayrhuber
2003-05-07 15:23                 ` Chris Mason
2003-05-08 13:35                   ` Chris Mason
2003-05-12  7:37                   ` Oleg Drokin
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09 11:17 Kerin Millar

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=1052400685.14617.489.camel@tiny.suse.com \
    --to=mason@suse.com \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=christian.mayrhuber@gmx.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.