edit /etc/fstab and change all occurences of ext2 to ext3 and then reboot David Baron wrote:>I have a Debian system from a Knoppix distribution. I started out with ext2 >but decided to change to ext3. > >tune2fs -j OK. > >However the system boots with a warning ....ext3 mounted as ext2. >proc/mounts confirms this and no journal is running. > >So I have to make an initrd. Did so using instructions in the Debian Reference >and this did not change anything. Any attempt to use the img produced was a >kernel boot panic. Also, this intrd image is very large and cannot be used as >an image on the boot menu. > >What must I do? > > >_______________________________________________ >Ext3-users mailing list >Ext3-users@redhat.com >https://www.redhat.com/mailman/listinfo/ext3-users > > >
recompile your kernel, include ext3 in the kernel instead of as a module. David Baron wrote:>On Tuesday 06 January 2004 18:48, Adam Williams wrote > >This was, of course done. There is only one partition involved and since this >was the root partition, this was set to "auto". It was tried before as ext3 >and ext3,ext2, but the reference said make it auto. > >The problem is that ext3 is NOT in the kernel but is a module. This is why an >initrd is needed. > > > >>edit /etc/fstab and change all occurences of ext2 to ext3 and then reboot >> >>David Baron wrote: >> >> >>>I have a Debian system from a Knoppix distribution. I started out with >>>ext2 but decided to change to ext3. >>> >>>tune2fs -j OK. >>> >>>However the system boots with a warning ....ext3 mounted as ext2. >>>proc/mounts confirms this and no journal is running. >>> >>>So I have to make an initrd. Did so using instructions in the Debian >>>Reference and this did not change anything. Any attempt to use the img >>>produced was a kernel boot panic. Also, this intrd image is very large >>>and cannot be used as an image on the boot menu. >>> >>>What must I do? >>> >>> >>>_______________________________________________ >>>Ext3-users mailing list >>>Ext3-users@redhat.com >>>https://www.redhat.com/mailman/listinfo/ext3-users >>> >>> > > >_______________________________________________ >Ext3-users mailing list >Ext3-users@redhat.com >https://www.redhat.com/mailman/listinfo/ext3-users > > >
David Baron schrieb:> On Tuesday 06 January 2004 18:48, Adam Williams wrote > > This was, of course done. There is only one partition involved and since this > was the root partition, this was set to "auto". It was tried before as ext3 > and ext3,ext2, but the reference said make it auto. > > The problem is that ext3 is NOT in the kernel but is a module. This is why an > initrd is needed.Look at http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html#module Hopefully this will help you. Regards, Juri
I have a Debian system from a Knoppix distribution. I started out with ext2 but decided to change to ext3. tune2fs -j OK. However the system boots with a warning ....ext3 mounted as ext2. proc/mounts confirms this and no journal is running. So I have to make an initrd. Did so using instructions in the Debian Reference and this did not change anything. Any attempt to use the img produced was a kernel boot panic. Also, this intrd image is very large and cannot be used as an image on the boot menu. What must I do?
On Tuesday 06 January 2004 18:48, Adam Williams wrote This was, of course done. There is only one partition involved and since this was the root partition, this was set to "auto". It was tried before as ext3 and ext3,ext2, but the reference said make it auto. The problem is that ext3 is NOT in the kernel but is a module. This is why an initrd is needed.> edit /etc/fstab and change all occurences of ext2 to ext3 and then reboot > > David Baron wrote: > >I have a Debian system from a Knoppix distribution. I started out with > > ext2 but decided to change to ext3. > > > >tune2fs -j OK. > > > >However the system boots with a warning ....ext3 mounted as ext2. > >proc/mounts confirms this and no journal is running. > > > >So I have to make an initrd. Did so using instructions in the Debian > > Reference and this did not change anything. Any attempt to use the img > > produced was a kernel boot panic. Also, this intrd image is very large > > and cannot be used as an image on the boot menu. > > > >What must I do? > > > > > >_______________________________________________ > >Ext3-users mailing list > >Ext3-users@redhat.com > >https://www.redhat.com/mailman/listinfo/ext3-users
cp /boot/initrd.xxx /boot/initrd.xxx.bck cp /boot/initrd.xxx /tmp mkdir /tmp/initrd_loop mount -o loop /tmp/initrd.xxx /tmp/initrd_loop cd /tmp/initrd_loop see the modules loaded by linuxrc script and corresponding .o files in lib directory remove the modules unneeded and corresponding insmod command in linuxrc umount /tmp/initrd_loop verify if size is affordable cp /tmp/initrd.xxx /boot if you have grub you are done, else run lilo reboot HIH, GIanluca -----Original Message----- From: ext3-users-admin@redhat.com [mailto:ext3-users-admin@redhat.com]On Behalf Of David Baron Sent: domenica 11 gennaio 2004 10.44 To: Matt Bernstein Cc: Adam Williams; Juri Haberland; ext3-users@redhat.com Subject: Re: Getting ext3 up and running On Thursday 08 January 2004 20:44, Matt Bernstein wrote:> On Jan 7 David Baron wrote: > >On Wednesday 07 January 2004 15:20, Matt Bernstein wrote: > >> Why not take the large initrd image and just "remove stuff"(tm) till > >> lilo will take it? Or just try grub.. > > > >By setting moduls=non and specifying jbd and ext3 in the root parameter of > > the mkinitrd.conf, I got the size down to 972k. I think it should be 1/3 > > of that. This is still too big to be on the image menu and using it as a > > lilo initrd still panics! > > I meant be dirtier than that.. take your initrd image and mount it > loopback, see what's in it that you don't need.. ;)]How do I do this? _______________________________________________ Ext3-users mailing list Ext3-users@redhat.com https://www.redhat.com/mailman/listinfo/ext3-users
I forgot an essential initial step and final step, as initrd is a compressed ext2 file system on file, sorry. The steps are: cp /boot/initrd.xxx /boot/initrd.xxx.bck gzip -dc /boot/initrd.xxx > /tmp/initrd.xxx mkdir /tmp/initrd_loop mount -o loop /tmp/initrd.xxx /tmp/initrd_loop cd /tmp/initrd_loop see the modules loaded by linuxrc script and corresponding .o files in lib directory remove the modules unneeded and corresponding insmod command in linuxrc umount /tmp/initrd_loop verify if size is affordable gzip -c /tmp/initrd.xxx > /boot/initrd.xxx if you have grub you are done, else run lilo reboot sorry -----Original Message----- From: ext3-users-admin@redhat.com [mailto:ext3-users-admin@redhat.com]On Behalf Of Cecchi, Gianluca Sent: lunedì 12 gennaio 2004 12.27 To: David Baron; Matt Bernstein Cc: Adam Williams; Juri Haberland; ext3-users@redhat.com Subject: RE: Getting ext3 up and running cp /boot/initrd.xxx /boot/initrd.xxx.bck cp /boot/initrd.xxx /tmp mkdir /tmp/initrd_loop mount -o loop /tmp/initrd.xxx /tmp/initrd_loop cd /tmp/initrd_loop see the modules loaded by linuxrc script and corresponding .o files in lib directory remove the modules unneeded and corresponding insmod command in linuxrc umount /tmp/initrd_loop verify if size is affordable cp /tmp/initrd.xxx /boot if you have grub you are done, else run lilo reboot HIH, GIanluca -----Original Message----- From: ext3-users-admin@redhat.com [mailto:ext3-users-admin@redhat.com]On Behalf Of David Baron Sent: domenica 11 gennaio 2004 10.44 To: Matt Bernstein Cc: Adam Williams; Juri Haberland; ext3-users@redhat.com Subject: Re: Getting ext3 up and running On Thursday 08 January 2004 20:44, Matt Bernstein wrote:> On Jan 7 David Baron wrote: > >On Wednesday 07 January 2004 15:20, Matt Bernstein wrote: > >> Why not take the large initrd image and just "remove stuff"(tm) till > >> lilo will take it? Or just try grub.. > > > >By setting moduls=non and specifying jbd and ext3 in the root parameter of > > the mkinitrd.conf, I got the size down to 972k. I think it should be 1/3 > > of that. This is still too big to be on the image menu and using it as a > > lilo initrd still panics! > > I meant be dirtier than that.. take your initrd image and mount it > loopback, see what's in it that you don't need.. ;)]How do I do this? _______________________________________________ Ext3-users mailing list Ext3-users@redhat.com https://www.redhat.com/mailman/listinfo/ext3-users _______________________________________________ Ext3-users mailing list Ext3-users@redhat.com https://www.redhat.com/mailman/listinfo/ext3-users
David Baron said:> On Monday 12 January 2004 15:15, you wrote: >> I used 3.2 in the past. >> I'm downloading 3.3: it seems to be worth while ... in about 1h I'd done >> And then I'll give it a try, perhaps inside VMware. >> Did you use option in desktop to install it on hd, after starting from >> live >> cd? Did you give any particular option? I never installed knoppix to hd, >> only booted and worked from cd itself. Let me know. >> Cheers, >> Gianluca > > I installed it on HD, fairly painless. If only I knew to set it up as ext3 > to > begin-with! > >I downloaded knoppix 3.3 and started it inside VMware configured with an ide hard disk of 4Gb. After starting I followed instructions given at http://download.linuxtag.org/knoppix/KNOPPIX-FAQ-EN.txt in particulare, inside knoppix: fdisk /dev/hda created a primary partition big as the whole disk (4Gb) mkfs -t ext2 -j /dev/hda1 mount /dev/hda1 /mnt/hda cp -a /KNOPPIX/* /mnt/hda (it took 11 minutes for 2Gb total) created /mnt/hda/etc/fstab like proc /proc proc defaults 0 0 pts /dev/pts devpts mode=0622 0 0 /dev/fd0 /mnt/auto/floppy auto user,noauto,exec,umask=000 0 0 /dev/cdrom /mnt/auto/cdrom auto user,noauto,exec,ro 0 0 # Added by KNOPPIX /dev/hda1 /mnt/hda1 ext3 noauto,users,exec 0 0 cp /etc/lilo.conf /mnt/hda/etc and modified it like this (basic, to improve) lba32 boot=/dev/hda timeout=30 default=Knoppix image=/vmlinuz append="lang=de apm=power-off quiet BOOT_IMAGE=knoppix" root=/dev/hda1 label=Knoppix read-write mkdir /mnt/hda/home/knoppix chown knoppix.knoppix /mnt/hda/home/knoppix chroot /mnt/hda lilo After boot, this is situation uname -a: Linux Knoppix 2.4.22-xfs #1 SMP Fr Okt 3 20:36:25 CEST 2003 i686 GNU/Linux df -k: Filesystem 1K-Bl�cke Benutzt Verf�gbar Ben% Eingeh�ngt auf /dev/hda1 4127076 2157172 1760260 56% / mount: /dev/hda1 on / type auto (rw) proc on /proc type proc (rw) usb on /proc/bus/usb type usbdevfs (rw,devmode=0666) automount(pid262) on /mnt/auto type autofs (rw,fd=4,pgrp=262,minproto=2,maxproto=4) cat /proc/mounts: rootfs / rootfs rw 0 0 /dev/root / ext2 rw 0 0 proc /proc proc rw 0 0 usb /proc/bus/usb usbdevfs rw 0 0 automount(pid262) /mnt/auto autofs rw 0 0 lsmod: Module Size Used by Not tainted autofs4 8756 1 (autoclean) af_packet 13448 0 (autoclean) agpgart 38296 0 (unused) es1371 30120 0 gameport 1388 0 [es1371] ac97_codec 11884 0 [es1371] soundcore 3428 4 [es1371] pcnet32 14304 1 mii 2240 0 [pcnet32] crc32 2816 0 [pcnet32] serial 51972 0 (autoclean) usb-uhci 21836 0 (unused) usbcore 57472 1 [usb-uhci] apm 9768 2 rtc 6908 0 (autoclean) tune2fs -l: tune2fs 1.35-WIP (21-Aug-2003) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: f08a4e05-14b5-4113-996d-c70b8a8833b5 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype sparse_super Default mount options: (none) Filesystem state: not clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 524288 Block count: 1048233 Reserved block count: 52411 Free blocks: 492479 Free inodes: 390507 First block: 0 Block size: 4096 Fragment size: 4096 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 16384 Inode blocks per group: 512 Filesystem created: Mon Jan 12 09:09:19 2004 Last mount time: Mon Jan 12 10:32:10 2004 Last write time: Mon Jan 12 09:39:06 2004 Mount count: 2 Maximum mount count: 24 Last checked: Mon Jan 12 09:09:19 2004 Check interval: 15552000 (6 months) Next check after: Sat Jul 10 10:09:19 2004 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode: 8 Default directory hash: tea Directory Hash Seed: ecdd20c9-cd8f-4227-959c-a9b9aaf35b73 Journal backup: inode blocks So it seems that ext3 support is compiled into the kernel and all is ok with journal. I can try to make the same but creating initially the filesystem without the -j switch and try to change it after, if necessary. Can you reinstall or did you customized it a lot? HIH Gianluca