From: Alex Walker <alex@x3ja.co.uk>
To: Oleg Drokin <green@namesys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.5.6 and 2.5.7-pre1 - reiserfs?
Date: Thu, 14 Mar 2002 17:40:27 +0000 [thread overview]
Message-ID: <20020314174027.H9664@x3ja.co.uk> (raw)
In-Reply-To: <20020314162009.F9664@x3ja.co.uk> <20020314192916.A1929@namesys.com> <20020314170123.G9664@x3ja.co.uk> <20020314200337.A2186@namesys.com>
In-Reply-To: <20020314200337.A2186@namesys.com>; from green@namesys.com on Thu, Mar 14, 2002 at 08:03:37PM +0300
On Thu, Mar 14, 2002 at 08:03:37PM +0300, Oleg Drokin wrote:
> > Whilst I'm here... Is there a neat way to convert your root system
> > from 3.5 to 3.6? I tried "mount -o remount,conv /" which gave no
> > errors, but didn't actually convert it. I also tried adding conv to
> > the options in /etc/fstab, but to similar effect... Do I have to
> > copy to a different partition with a 3.6 format and use that as my
> > root to do it?
> I think you need to pass "rootflags=conv" option to your kernel. That
> should work. Esp. if you do not use any kind of initrd.
This doesn't work, sorry.
I get:
EXT3-fs: Unrecognized mount option conv
EXT2-fs: Unrecognized mount option conv
found reiserfs format "3.5" with standard journal
[Usual boot messages]
on boot, which is odd. I do have some EXT3 partitions too, but my root
is certainly reiserfs.
This probably isn't the right place to be asking for this kind of help I
guess, but if anyone can shed any light - I would appreciate it.
However I am in the process of creating some reiserfs boot disks so I
can convert it...
Alex
--
ALEX|X3JA
alex@x3ja.co.uk
ICQ: 1523424
MSN: x3ja@hotmail.com
next prev parent reply other threads:[~2002-03-14 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 16:20 Oops in 2.5.6 and 2.5.7-pre1 - reiserfs? Alex Walker
2002-03-14 16:29 ` Oleg Drokin
2002-03-14 17:01 ` Alex Walker
2002-03-14 17:03 ` Oleg Drokin
2002-03-14 17:40 ` Alex Walker [this message]
2002-03-15 5:44 ` 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=20020314174027.H9664@x3ja.co.uk \
--to=alex@x3ja.co.uk \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
/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.