From: Alex Zarochentsev <zam@namesys.com>
To: "Raymond A. Meijer" <rmeijer@internet.gr>
Cc: reiserfs-list@namesys.com
Subject: Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?
Date: Thu, 3 Jun 2004 19:22:08 +0400 [thread overview]
Message-ID: <20040603152207.GO8091@backtop.namesys.com> (raw)
In-Reply-To: <20040603143057.GN8091@backtop.namesys.com>
On Thu, Jun 03, 2004 at 06:30:57PM +0400, Alex Zarochentcev wrote:
> On Thu, Jun 03, 2004 at 05:04:09PM +0300, Raymond A. Meijer wrote:
> > On Thu 3 June 2004 15:51, Raymond A. Meijer wrote:
> >
> > > So, I'll recompile a vanilla kernel with no optimisations and only the mm
> > > and Reiser4 patches applied...
> >
> > No, still the same: Oops errors when the kernel tries to mount Reiser4
> > filesystems...
> >
> > ...but then I converted most of the system partitions (/var, /home, /usr) to
> > ReiserFS and kept some other partitions in Reiser4 format (/backup, /tmp,
> > /var/spool/squid) and now it DOES work properly!
> >
> > 2.6.6-mm2 boots up fine, mounts everything and starts everything. I'm actually
> > sending this mail with KMail on KDE 3.2.2 on kernel 2.6.6-mm2...
> >
> > Any ideas as to what happened?! :)
>
> Seems we made a disk format change accidentally.
> details later. or a fix may be.
please try this patch:
=================================================
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/06/03 19:04:55+04:00 zam@crimson.namesys.com
# enum item_id: restore disk format.
#
# forward.h
# 2004/06/03 19:04:51+04:00 zam@crimson.namesys.com +10 -9
# enum item_id: restore disk format.
#
diff -Nru a/forward.h b/forward.h
--- a/forward.h Thu Jun 3 19:20:36 2004
+++ b/forward.h Thu Jun 3 19:20:36 2004
@@ -174,16 +174,17 @@
SQUEEZE_CONTINUE = 3
} squeeze_result;
+/* Do not change items ids. If you do - there will be format change */
typedef enum {
- STATIC_STAT_DATA_ID,
- SIMPLE_DIR_ENTRY_ID,
- COMPOUND_DIR_ID,
- NODE_POINTER_ID,
- EXTENT_POINTER_ID,
- FORMATTING_ID,
- CTAIL_ID,
- BLACK_BOX_ID,
- LAST_ITEM_ID
+ STATIC_STAT_DATA_ID = 0x0,
+ SIMPLE_DIR_ENTRY_ID = 0x1,
+ COMPOUND_DIR_ID = 0x2,
+ NODE_POINTER_ID = 0x3,
+ EXTENT_POINTER_ID = 0x5,
+ FORMATTING_ID = 0x6,
+ CTAIL_ID = 0x7,
+ BLACK_BOX_ID = 0x8,
+ LAST_ITEM_ID = 0x9
} item_id;
/* Flags passed to jnode_flush() to allow it to distinguish default settings based on
=================================================
>
> > Ray
>
> --
> Alex.
--
Alex.
next prev parent reply other threads:[~2004-06-03 15:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 12:54 Working Reiser4 patch for kernel 2.6.6(-mm2)? Raymond A. Meijer
2004-06-02 12:56 ` Alex Zarochentsev
2004-06-02 13:03 ` Raymond A. Meijer
2004-06-02 16:02 ` Alex Zarochentsev
2004-06-02 16:23 ` mjt
2004-06-02 16:34 ` Alex Zarochentsev
2004-06-02 16:39 ` Alex Zarochentsev
2004-06-02 16:52 ` mjt
2004-06-03 11:07 ` Raymond A. Meijer
2004-06-03 11:17 ` Raymond A. Meijer
2004-06-03 12:51 ` Raymond A. Meijer
2004-06-03 14:04 ` Raymond A. Meijer
2004-06-03 14:30 ` Alex Zarochentsev
2004-06-03 15:22 ` Alex Zarochentsev [this message]
2004-06-04 7:29 ` Raymond A. Meijer
2004-06-04 9:44 ` Raymond A. Meijer
2004-06-04 9:54 ` Alex Zarochentsev
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 12:14 Marcel Hilzinger
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=20040603152207.GO8091@backtop.namesys.com \
--to=zam@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=rmeijer@internet.gr \
/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.