mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikita Danilov <NikitaDanilov@Yahoo.COM>
To: Vasil Kolev <lnxkrnl@mail.ludost.net>
Cc: <reiserfs-list@namesys.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [reiserfs-list] Incompatibility between the reisrefs patches for 2.2.x and 2.4.x
Date: Fri, 22 Jun 2001 17:20:03 +0400	[thread overview]
Message-ID: <15155.17923.423044.21965@beta.namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0106221603590.24521-100000@doom.bastun.net>
In-Reply-To: <Pine.LNX.4.33.0106221603590.24521-100000@doom.bastun.net>

Vasil Kolev writes:
 > Maybe this is a know issue, but nonetheless.....
 > I have dual coppermine/930 machine with 1.2G ram, kernel 2.4.5. I used
 > reiserfs for my  /home and /var partitions. When tried downgrading to
 > 2.2.19, I got errors  in syslog like 'can't find superblock' ... ( I don't
 > have them, /var wasn't mounted, and i had to return the machine in
 > production state... ). Does someone has any idea about this, how could I
 > downgrade to 2.2.19 ?

2.4 kernels can work with both 3.5 reiserfs disk format (old) and 3.6
(new). 2.2 kernels---only with 3.5. Probably, you have created your
file-systems in the new format.

You can boot 2.4 kernel, create new file-system large enough with
/sbin/mkreiserfs -v1 (old format), copy existing files there by tar or
cpio and then update /etc/fstab to mount file-system just created. Now,
you can work both with 2.2 and 2.4 kernels.

Keep in mind, that 3.5 format has some limitations concerning file size
etc. Check faq at namesys.com for details. On the other hand, 3.5 often
considered more stable.

Nikita.

  reply	other threads:[~2001-06-22 13:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-22 13:08 Vasil Kolev
2001-06-22 13:20 ` Nikita Danilov [this message]
2001-06-22 13:23   ` [reiserfs-list] " Vasil Kolev
2001-06-22 14:00   ` Nikita Danilov

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=15155.17923.423044.21965@beta.namesys.com \
    --to=nikitadanilov@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnxkrnl@mail.ludost.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®