From: Oleg Drokin <green@namesys.com>
To: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: datalogging and quota patches port to 2.4.21-pre6
Date: Sat, 22 Mar 2003 10:29:31 +0300 [thread overview]
Message-ID: <20030322102931.A7246@namesys.com> (raw)
In-Reply-To: <3E7BA735.5090604@mb.tu-ilmenau.de>
Hello!
On Sat, Mar 22, 2003 at 12:58:45AM +0100, Manuel Krause wrote:
> GRIN !!! I really would like to enjoy these, but you seem to be far
> away in future. Still no "official" patch seems to be out -- at least
> for me on here. (Yes, I'll wait and would not use bk.)
> Have your previously pending patches been included into 2.4.21-pre6
> (they are: 02-trivial1.diff
> 03-more-mount-checks.diff
> 01-journal-overflow-fix.diff
> from ftp://ftp.namesys.com/pub/reiserfs-for-2.4/testing :
> iget5_locked_for_2.4.21-pre5-datalogging.diff.gz
> and posted to our ML @ "Wed, 12 Mar 2003 10:46:42 +0300" :
> direct-io-fix-II.diff
> ) ?
Only patches that are visible at
ftp://ftp.namesys.com/pub/reiserfs-for-2.4/2.4.20-pending
were included into 2.4 tree.
iget5_locked patch is in testing right now.
direct-io-fix-II.diff have triggered some old long known minor metadata
updating problems in case of unexpected crash and I am looking how to resolve
that and trying various stuff.
> My question only results from beeing unable to get them all applied to
> 2.4.21-pre5 with data-logging without rejects and me feeling unsafe to
> adjust them manually.
Well, if you apply all of those patches from
ftp://ftp.namesys.com/pub/reiserfs-for-2.4/2.4.20-pending on clean 2.4.20
(or whatever is needed for 2.4.21-pre5 only frpm
ftp://ftp.namesys.com/pub/reiserfs-for-2.4/2.4.21-pre5.pending)
and then apply data logging patches as if you have 2.4.21-pre6,
and then iget5_locked stuff, it should work.
Bye,
Oleg
next prev parent reply other threads:[~2003-03-22 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 15:13 datalogging and quota patches port to 2.4.21-pre6 Oleg Drokin
2003-03-21 23:58 ` Manuel Krause
2003-03-22 7:29 ` Oleg Drokin [this message]
2003-03-22 19:07 ` Manuel Krause
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=20030322102931.A7246@namesys.com \
--to=green@namesys.com \
--cc=manuel.krause@mb.tu-ilmenau.de \
--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.