All of lore.kernel.org
 help / color / mirror / Atom feed
From: Madison Kelly <linux@alteeve.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Ext3 -> ReiserFS on '/' convertion prob
Date: Fri Dec 19 16:31:02 2003	[thread overview]
Message-ID: <3FE37C0B.2080609@alteeve.com> (raw)
In-Reply-To: <3FE36BAF.7030406@stercomm.com>

I will investigate that further... May I make one more comment that may 
help me solve this? Quick note, since the last post I wiped the test 
server and re-installed, just in case I had foobar'ed something along 
the way.

I have made a backup of '/' (from '/dev/vg0/root') to the backup drive 
(/dev/sdd1) and edited '/etc/fstab', '/etc/mtab' and deleted 
'/etc/blkid.tab' (which, if I understand is just a cache). I did this on 
both the '/' (/dev/vg0/root and /dev/sdd1) while under the Linux Rescue 
disk (Fedora Core 1 install in 'linux rescue') and finally I updated 
'/boot/grub/grub.conf' on both partitions as well to contain entries 
pointing '/' to '/dev/sdd1'. When I reboot (before converting the LVM LV 
to ReiserFS) and choose to boot into '/dev/sdd1' as root it -seems- to 
work. When I type:

# df

It shows '/' to be '/dev/sdd'. Now to verify this I did:

# cd /
# touch test.txt
# mkdir vg0
# mount /dev/vg0/root /vg0

I then checked to see if the 'test.txt' file was there, and it was. How 
the heck can the original settings for '/dev/vg0/root' be -SO- 
persistent that even 'df' thinks that the wrong partition is mounted?!? 
Where are these settings stored?

Side note: When I boot again off the rescue disk and run the same test 
(with '/dev/sdd1' mounted as '/') then it is fine, there '/' really is 
'/dev/sdd1'...)

Anyway, I am off to try converting again now that I know to try passing 
"init=reiserfs" in grub (will it work though?... Off to see!)

Thank you for being so helpful and patient while I pound my head through 
this!

Madison

Chris Cox wrote:
> Madison Kelly wrote:
> 
>> I am so sorry for asking but how would I check?
>>
> 
> I'm a SUSE user myself.  It's mkinitrd script
> makes it pretty easy to add modules to your
> initrd.  I'd check that lvm_mkinitrd script
> of yours... you may have to tweak it.
> In fact, SUSE's script detects (tries anyway) if
> your root filesystem is LVM's and automatically
> adds in the lvm_mod if it wasn't specified.
> 
> There's probably a way to find out easily if
> it's there already.. just not sure off the top of my head.

  reply	other threads:[~2003-12-19 16:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18 23:15 [linux-lvm] Ext3 -> ReiserFS on '/' convertion prob Madison Kelly
2003-12-19  9:07 ` Jord Tanner
2003-12-19 10:54   ` Madison Kelly
2003-12-19 11:19     ` Madison Kelly
2003-12-19 12:20     ` Jord Tanner
2003-12-19 13:55       ` Madison Kelly
2003-12-19 14:46         ` Chris Cox
2003-12-19 14:54           ` Madison Kelly
2003-12-19 15:22             ` Chris Cox
2003-12-19 16:31               ` Madison Kelly [this message]
2003-12-21 15:47                 ` [linux-lvm] Ext3 -> ReiserFS on '/' conversion problem wopp
2003-12-21 21:10                   ` Madison Kelly

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=3FE37C0B.2080609@alteeve.com \
    --to=linux@alteeve.com \
    --cc=linux-lvm@sistina.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.