Re: How to enable EXT3 FS on 2.4
On Mon, 4 Feb 2002 15:55:28 +0100, Eduard Bloch <[EMAIL PROTECTED]> wrote: [snip] > > You can't put comma separated lists of types in fstab. > > You can, but you should not. Why? -- Eric G. Miller
Re: How to enable EXT3 FS on 2.4
#include Herbert Xu wrote on Mon Feb 04, 2002 um 10:17:29PM: > > fsck 1.25 (20-Sep-2001) > > fsck.ext3,ext2 ... complain something like command does not exist. You can use "auto" (Bzzt: Herbert Xu dropped support for auto and will probably try to make everyone believe that you do not use this, you don't need this and it is generaly a-bad-idea though ext2/ext3 developer recommend to do so and thoug I provided a patch to detect the filesystem). > You can't put comma separated lists of types in fstab. You can, but you should not. > > This is not in dmesg but just on console screen. It is commint from fsck which tryies to run fsck.ext3,ext2. You could make a symlink, but it is ugly, ugly, ugly. > > 2. dmesg contain "cramfs: wrong magic" > > That's a harmless warning and will go away once mkinitrd starts using > pivot_root. Btw, if you don't have cramfs in the kernel, and forgot to remove the initrd line from the boot-loaders config, the kernel will break on mounting initrd and stop with a "cannot mount root" message. Something you should probably mention explicitely in the mkinitrd docs. Gruss/Regards, Eduard. -- Eingedeutschte Fehlermeldungen sind doch etwas schoenes: "Kein Weltraum links auf dem Geraet"
Re: How to enable EXT3 FS on 2.4
Osamu Aoki <[EMAIL PROTECTED]> wrote:
>
> 1. Boot screen had fsck messafge printing out:
> ...
> fsck 1.25 (20-Sep-2001)
> fsck.ext3,ext2 ... complain something like command does not exist.
You can't put comma separated lists of types in fstab.
> This is not in dmesg but just on console screen.
> 2. dmesg contain "cramfs: wrong magic"
That's a harmless warning and will go away once mkinitrd starts using
pivot_root.
--
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: How to enable EXT3 FS on 2.4
On Mon, Feb 04, 2002 at 05:18:17PM +1100, Herbert Xu wrote: > On Sun, Feb 03, 2002 at 05:55:34PM -0800, Osamu Aoki wrote: > > > Because you've changed fstab which contains the root filesystem type... > mkinitrd uses fstab to find out the root file system type, which decides > what goes into the initrd image... Thanks :) Now it is crystal clear. I also added entries for /etc/mkinitrd/modules. So modules (jbd ext3 ext2) load automatically upon boot. I still have minor issues with "ext3" set-up, namely, "fsck" and "cramfs magic". Can anyone tell me what to do. I was told that using "ext3,ext2" in /etc/fstab is better than just having "ext3" for safe back drop when booting 2.2 kernel. Made sense. But reality was strange. At least keeping it as "ext3" made cleaner boot. Below are the details of trouble with "ext3,ext2" in /etc/fstab: 1. Boot screen had fsck messafge printing out: ... fsck 1.25 (20-Sep-2001) fsck.ext3,ext2 ... complain something like command does not exist. This is not in dmesg but just on console screen. 2. dmesg contain "cramfs: wrong magic" This happens right after "Partition check:" as cramfs: wrong magic kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. change_root: old root has d_count=2 Freeing unused kernel memory: 216k freed Osamu -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki <[EMAIL PROTECTED]>, GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://qref.sourceforge.net/quick/ +
Re: How to enable EXT3 FS on 2.4
On Sun, Feb 03, 2002 at 05:55:34PM -0800, Osamu Aoki wrote:
>
> > Because you've changed fstab which contains the root filesystem type...
>
> I did not remount. So root FS is still ext2 until reboot. Besides,
> file location of all files (kernel image, initrd image is stationally)
mkinitrd uses fstab to find out the root file system type, which decides
what goes into the initrd image...
> > You could also simply reinstall kernel-image of course.
>
> I did install kernel-image before editing fstab. Is not it enough?
Reinstalling kernel-image runs mkinitrd automatically.
> I greped source of lilo and I only see "fstab" in configuration scripts
> (liloconfig, lilo_find_mbr) which are not used and will not be affected
> by my fstab edit.
Try grepping /usr/sbin/mkinitrd.
--
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: How to enable EXT3 FS on 2.4
Herbert, I am confusedi by your comment. (I know you know better but it does not make sense to me.) On Sun, Feb 03, 2002 at 09:39:39AM +1100, Herbert Xu wrote: > Osamu Aoki <[EMAIL PROTECTED]> wrote: > > >> > # cd /etc; mv fstab fstab.old > >> > # sed 's/ext2/ext3,ext2/g' fstab # forged to be better :) > >> > >> mkinitrd -o /boot/initrd.img-2.4.17-686-smp /lib/modules/2.4.17-686-smp > >> lilo > > > It does not harm but kernel-image already comes with initrd image and it > > runs lilo during "install". Is there any specific reason why this > > command needs to be run again? > > Because you've changed fstab which contains the root filesystem type... I did not remount. So root FS is still ext2 until reboot. Besides, file location of all files (kernel image, initrd image is stationally) I thought lilo care only physical location. That is the reason behind why it can put kernel image in DOS partition. > You could also simply reinstall kernel-image of course. I did install kernel-image before editing fstab. Is not it enough? I greped source of lilo and I only see "fstab" in configuration scripts (liloconfig, lilo_find_mbr) which are not used and will not be affected by my fstab edit. I am sorry to bug you :-( (I think my system is working fine by the process I described.) -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki <[EMAIL PROTECTED]>, GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://qref.sourceforge.net/quick/ +
Re: How to enable EXT3 FS on 2.4
Osamu Aoki <[EMAIL PROTECTED]> wrote:
>> > # cd /etc; mv fstab fstab.old
>> > # sed 's/ext2/ext3,ext2/g' fstab # forged to be better :)
>>
>> mkinitrd -o /boot/initrd.img-2.4.17-686-smp /lib/modules/2.4.17-686-smp
>> lilo
> It does not harm but kernel-image already comes with initrd image and it
> runs lilo during "install". Is there any specific reason why this
> command needs to be run again?
Because you've changed fstab which contains the root filesystem type...
You could also simply reinstall kernel-image of course.
--
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: How to enable EXT3 FS on 2.4
On Sat, Feb 02, 2002 at 10:11:31AM +1100, Herbert Xu wrote: > Osamu Aoki <[EMAIL PROTECTED]> wrote: > > I did following to enable ext3 fs on my system. If there are better > > way, let me know. (kernel-image-2.4.17-686-smp) > > > # apt-get update; apt-get install kernel-image-2.4.17-686-smp > > ... > > # tune2fs -j -i 0 /dev/hda1 > > # tune2fs -j -i 0 /dev/hda2 # ... For all EXT2 FS which moves to EXT3 > > # cd /etc; mv fstab fstab.old > > # sed 's/ext2/ext3,ext2/g' fstab # forged to be better :) > > mkinitrd -o /boot/initrd.img-2.4.17-686-smp /lib/modules/2.4.17-686-smp > lilo It does not harm but kernel-image already comes with initrd image and it runs lilo during "install". Is there any specific reason why this command needs to be run again? Thanks anyway reminding this is needed for roll-your own kernel :) Osamu
Re: How to enable EXT3 FS on 2.4
Osamu Aoki <[EMAIL PROTECTED]> wrote:
> I did following to enable ext3 fs on my system. If there are better
> way, let me know. (kernel-image-2.4.17-686-smp)
> # apt-get update; apt-get install kernel-image-2.4.17-686-smp
> ...
> # tune2fs -j -i 0 /dev/hda1
> # tune2fs -j -i 0 /dev/hda2 # ... For all EXT2 FS which moves to EXT3
> # cd /etc; mv fstab fstab.old
> # sed 's/ext2/ext3/g' fstab
mkinitrd -o /boot/initrd.img-2.4.17-686-smp /lib/modules/2.4.17-686-smp
lilo
> # shutdown -r now
--
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: How to enable EXT3 FS on 2.4
Thanks for good comment. On Fri, Feb 01, 2002 at 09:25:14AM -0500, David Roundy wrote: > On Fri, Feb 01, 2002 at 02:17:00AM -0800, Osamu Aoki wrote: > > I did following to enable ext3 fs on my system. If there are better > > way, let me know. (kernel-image-2.4.17-686-smp) > > > > # apt-get update; apt-get install kernel-image-2.4.17-686-smp > > ... > > # tune2fs -j -i 0 /dev/hda1 > > # tune2fs -j -i 0 /dev/hda2 # ... For all EXT2 FS which moves to EXT3 > > # cd /etc; mv fstab fstab.old > > # sed 's/ext2/ext3/g' fstab > > I would make this > > # sed 's/ext2/ext3,ext2/g' fstab Good point :) Always nice to have safe fall back. > So that you can still mount the partitions as ext2 if ext3 isn't available > (e.g. using an older kernel or whatever). > > > # shutdown -r now > > ... reboot and, at prompt by initrd image, type RETURN > > # insmod jbd > > # insmod ext3 # depmod ext3 may take care all > > # insmod ext2 > > # ^D > > ... Now I get system on ext3 fs (/,...) > > Do you really need to reboot? It seems that you could just insmod ext3 and > then `mount -o remount` the relevant partitions. Good point again. But my answer is yes. See I am installing new kernel above. For this, I think my system needed to be rebooted. If one just needs to get ext3 functioning, there is no need to reboot. Cheers :) -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki <[EMAIL PROTECTED]>, GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://qref.sourceforge.net/quick/ +
Re: How to enable EXT3 FS on 2.4
On Fri, Feb 01, 2002 at 02:17:00AM -0800, Osamu Aoki wrote: > I did following to enable ext3 fs on my system. If there are better > way, let me know. (kernel-image-2.4.17-686-smp) > > # apt-get update; apt-get install kernel-image-2.4.17-686-smp > ... > # tune2fs -j -i 0 /dev/hda1 > # tune2fs -j -i 0 /dev/hda2 # ... For all EXT2 FS which moves to EXT3 > # cd /etc; mv fstab fstab.old > # sed 's/ext2/ext3/g' fstab I would make this # sed 's/ext2/ext3,ext2/g' fstab So that you can still mount the partitions as ext2 if ext3 isn't available (e.g. using an older kernel or whatever). > # shutdown -r now > ... reboot and, at prompt by initrd image, type RETURN > # insmod jbd > # insmod ext3 # depmod ext3 may take care all > # insmod ext2 > # ^D > ... Now I get system on ext3 fs (/,...) Do you really need to reboot? It seems that you could just insmod ext3 and then `mount -o remount` the relevant partitions. -- David Roundy http://civet.berkeley.edu/droundy/
How to enable EXT3 FS on 2.4
I did following to enable ext3 fs on my system. If there are better way, let me know. (kernel-image-2.4.17-686-smp) # apt-get update; apt-get install kernel-image-2.4.17-686-smp ... # tune2fs -j -i 0 /dev/hda1 # tune2fs -j -i 0 /dev/hda2 # ... For all EXT2 FS which moves to EXT3 # cd /etc; mv fstab fstab.old # sed 's/ext2/ext3/g' fstab # shutdown -r now ... reboot and, at prompt by initrd image, type RETURN # insmod jbd # insmod ext3 # depmod ext3 may take care all # insmod ext2 # ^D ... Now I get system on ext3 fs (/,...) -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki <[EMAIL PROTECTED]>, GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://qref.sourceforge.net/quick/ +
