You are not logged in.
What is the preferred way to install ext4 right now. I have to reinstall arch on my laptop and would like to have ext4 if possible?
Thanks
Can you wait a few days? We're close to an official release with 2.6.28/ext4
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
cu3edweb wrote:What is the preferred way to install ext4 right now. I have to reinstall arch on my laptop and would like to have ext4 if possible?
Thanks
Can you wait a few days? We're close to an official release with 2.6.28/ext4
Great News!
Excuse my poor English.
Offline
In fact, changes have been made to git projects to make the best out of detecting and using ext4 in the root/boot partition, after all this git changes have been released, shortly we expect to have a new installer with ext4 support.
Tough be advised a reinstall is not needed a migration to the new filesystem is smooth and after running the e4defrag that will be available, hopefully, in the upcoming kernel version, all your files will be ext4 optimized. And your partititons will be as clean as new.
Offline
cu3edweb wrote:What is the preferred way to install ext4 right now. I have to reinstall arch on my laptop and would like to have ext4 if possible?
Thanks
Can you wait a few days? We're close to an official release with 2.6.28/ext4
In fact, changes have been made to git projects to make the best out of detecting and using ext4 in the root/boot partition, after all this git changes have been released, shortly we expect to have a new installer with ext4 support.
Tough be advised a reinstall is not needed a migration to the new filesystem is smooth and after running the e4defrag that will be available, hopefully, in the upcoming kernel version, all your files will be ext4 optimized. And your partititons will be as clean as new.
I needed to get it reinstalled so I just went with ext3 hoping that I can change that soon when the time comes. According to kensai that seems fairly easy. Is that right?
Offline
Actually used reiserfs for / and ext3 for /home.
So I think I should just reinstall, and since I have ~60GB of space that I can't do anything with. (Unformatted, between /home which is already too big and /swap)
Plus I already have everything I need backed up.
Offline
kensai wrote:In fact, changes have been made to git projects to make the best out of detecting and using ext4 in the root/boot partition, after all this git changes have been released, shortly we expect to have a new installer with ext4 support.
Tough be advised a reinstall is not needed a migration to the new filesystem is smooth and after running the e4defrag that will be available, hopefully, in the upcoming kernel version, all your files will be ext4 optimized. And your partititons will be as clean as new.
I needed to get it reinstalled so I just went with ext3 hoping that I can change that soon when the time comes. According to kensai that seems fairly easy. Is that right?
Of course,
umount /dev/filesystem
tune2fs -O extents,uninit_bg,dir_index /dev/filesystem
tune2fs -pf /dev/filesystem
And there you are after that, just change to ext4 in fstab.
After that, just wait for e4defrag to be included upstream and it will change your old files to ext4 optimizations.
Last edited by kensai (2008-12-31 19:08:47)
Offline
Of course,
umount /dev/filesystem
tune2fs -O extents,uninit_bg,dir_index /dev/filesystem
tune2fs -pf /dev/filesystemAnd there you are after that, just change to ext4 in fstab.
I am assuming that I should use a livecd for that? And that is about the same as starting fresh? Still all the nice bells and whistles and nothing lost?
Thanks
Offline
I installed dbus-core during initial installation, I might have selected it explicitly, not sure if it was check by default... In either case, when I booted to the installed system dbus group/user entries were not created and dbus daemon would not start. I had to reinstall dbus-core to get this to work. BUG?
Other than that -- worked beautifully!
Offline
kensai wrote:Of course,
umount /dev/filesystem
tune2fs -O extents,uninit_bg,dir_index /dev/filesystem
tune2fs -pf /dev/filesystemAnd there you are after that, just change to ext4 in fstab.
I am assuming that I should use a livecd for that? And that is about the same as starting fresh? Still all the nice bells and whistles and nothing lost?
Thanks
A live cd just for the rot partition, my data and home partition, I just unmounted while using the system and did the above. I recommend for the root partition you use system rescue cd 1.1.3 or later, which has ext4 back-ported from 2.6.28. And yes, it will be as good as a reinstall all the bells and whistles on all your new data, for the already existing data, you will have to wait until e4defrag gets merged upstream, which should happen soon, that utility will change your old data to have all the bells and whistles of ext4.
Offline
In fact, changes have been made to git projects to make the best out of detecting and using ext4 in the root/boot partition, after all this git changes have been released, shortly we expect to have a new installer with ext4 support.
Tough be advised a reinstall is not needed a migration to the new filesystem is smooth and after running the e4defrag that will be available, hopefully, in the upcoming kernel version, all your files will be ext4 optimized. And your partititons will be as clean as new.
Does this switch the files in those old ext3 filesystems to use extents?
Offline
kensai wrote:In fact, changes have been made to git projects to make the best out of detecting and using ext4 in the root/boot partition, after all this git changes have been released, shortly we expect to have a new installer with ext4 support.
Tough be advised a reinstall is not needed a migration to the new filesystem is smooth and after running the e4defrag that will be available, hopefully, in the upcoming kernel version, all your files will be ext4 optimized. And your partititons will be as clean as new.
Does this switch the files in those old ext3 filesystems to use extents?
Yep.
For the others, don't make the same mistake I did, I installed the latest mkinitcpio so I can have a root ext4 filesystem, but forgot to run mkinitcpio -g /boot/kernel26.img after installation, leaving me with an unbootable system, so good fallback, is always there to help us.
Offline
Of course,
umount /dev/filesystem
tune2fs -O extents,uninit_bg,dir_index /dev/filesystem
tune2fs -pf /dev/filesystemAnd there you are after that, just change to ext4 in fstab.
After that, just wait for e4defrag to be included upstream and it will change your old files to ext4 optimizations.
When I run "tune2fs -pf /dev/filesystem" it says invalid option -- p? I am using system rescue 1.1.3
Last edited by cu3edweb (2009-01-01 18:38:51)
Offline
My guess is that kensai meant to say:
tune2fs -O extents,uninit_bg,dir_index /dev/filesystem
fsck.ext4 -pf /dev/filesystem
This is what is suggested in the various articles about ext4 around the web.
Last edited by patroclo7 (2009-01-01 19:10:21)
Mortuus in anima, curam gero cutis
Offline
Just finished an x86_64 basic install using the test img files (usbstick) on my acer aspire 5300 .
atm i have only 1 wired connection (used for my desktop), so i had to get wireless up with wpa2 encryption.
i created a temporary file in /etc/networks.d/ for netcfg and had wireless access.
This laptop has an atheros AR2413 chipset, which uses the ath5k kernel module.
After boot i got errors about missing modules : ath_hal , ath_pci and wlan were not available.
A bit of searching revealed that those were in the madwifi package, also wireless_tools and wpa_supplicant packages were not present.
I mounted the usbstick and used pacman -U to install the packages, then i had internet access.
If you choose http/ftp as source, you can only select the base packages, and the wireless packages are in support .
The only way to get them during install is to mount the cdrom/usbstick and install from those, then you can also select the development and support category.
Could these categories be added as optional to the http/ftp-install ?
Last edited by Lone_Wolf (2009-01-01 19:41:57)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
My guess is that kensai meant to say:
tune2fs -O extents,uninit_bg,dir_index /dev/filesystem fsck.ext4 -pf /dev/filesystem
This is what is suggested in the various articles about ext4 around the web.
Great thanks for that. Is ext4 already built into the 2.6.28 kernel26 in testing. I set the fstab to ext4 with defaults as the option and I get a kernel panic?
Offline
Great thanks for that. Is ext4 already built into the 2.6.28 kernel26 in testing. I set the fstab to ext4 with defaults as the option and I get a kernel panic?
Yes, ext4 is included in 2.6.28. I was getting a kernel panic as well; I assume it was because my initramfs image didn't have ext4 support and therefore was unable to mount the root partition.
Try booting with the fallback kernel and then run `mkinitcpio -p kernel26' as root.
Offline
Is ext4 already built into the 2.6.28 kernel26 in testing. I set the fstab to ext4 with defaults as the option and I get a kernel panic?
Support for ext4 is built as a module, so initrd image most likely has to be rebuilt so that the ext4 module is included in it. Can you boot with the fallback image?
Offline
My guess is that kensai meant to say:
tune2fs -O extents,uninit_bg,dir_index /dev/filesystem fsck.ext4 -pf /dev/filesystem
This is what is suggested in the various articles about ext4 around the web.
Not needed to specify fsck.ext4 fsck only will do the same, as it will auto detect the optimizations are for ext4.
EDIT: OMG, sorry I said tune2fs -pf, very sorry about that
is fsck -pf /dev/filesystem
Sorry again.
Last edited by kensai (2009-01-01 21:28:31)
Offline
patroclo7 wrote:My guess is that kensai meant to say:
tune2fs -O extents,uninit_bg,dir_index /dev/filesystem fsck.ext4 -pf /dev/filesystem
This is what is suggested in the various articles about ext4 around the web.
Great thanks for that. Is ext4 already built into the 2.6.28 kernel26 in testing. I set the fstab to ext4 with defaults as the option and I get a kernel panic?
you need to run mkinitcpio -g /boot/kernel26.img after installing mkinitcpio from testing, that will include ext4 built in support and the kernel won't panic.
If you can't access your system, boot fallback appending rootfstype=ext4 in the kernel line.
Offline
cu3edweb wrote:Is ext4 already built into the 2.6.28 kernel26 in testing. I set the fstab to ext4 with defaults as the option and I get a kernel panic?
Support for ext4 is built as a module, so initrd image most likely has to be rebuilt so that the ext4 module is included in it. Can you boot with the fallback image?
No I get a kernel panic with my fallback kernel also. I am not much of a kernel guy not sure where to go from here. The panic happens right after initramfs.
Last edited by cu3edweb (2009-01-01 21:32:35)
Offline
you need to run mkinitcpio -g /boot/kernel26.img after installing mkinitcpio from testing, that will include ext4 built in support and the kernel won't panic.
If you can't access your system, boot fallback appending rootfstype=ext4 in the kernel line.
sorry posted before I saw your post fixing now.
##Edit##
Thanks for the help ext4 is up and running. what are the best options for the fstab? I just have default right now. Is there noatime and such like ext3?
Thanks again
Last edited by cu3edweb (2009-01-01 21:45:32)
Offline
I'd try kensai's suggestion first.
If that doesn't work then you'd have to boot with an install cd, chroot to your system, edit mkinitcpio.conf to explicitly enable ext4 module in the MODULES array, and regenerate initramfs images with mkinitcpio.
See this wiki article for info on booting/chrooting: http://wiki.archlinux.org/index.php/Ker … llation_CD
I think that "mkinitcpio -p kernel26" is all that will be needed after you edit mkinitcpio.conf, or maybe something like:
mkinitcpio -k 2.6.28-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
Offline
kensai wrote:you need to run mkinitcpio -g /boot/kernel26.img after installing mkinitcpio from testing, that will include ext4 built in support and the kernel won't panic.
If you can't access your system, boot fallback appending rootfstype=ext4 in the kernel line.
sorry posted before I saw your post fixing now.
##Edit##
Thanks for the help ext4 is up and running. what are the best options for the fstab? I just have default right now. Is there noatime and such like ext3?Thanks again
Offline
Good to know your problem was fixed. Anyways I got trhough a stormy way while converting the root partition because I forgot to run mkinitcpio after the upgrade. And sorry for mistyping about tune2fs -pf instead of fsck -pf.
Offline
I know that I already said this but it was in an edit and a quote so not sure if anyone really read it. Thanks for the help ext4 is up and running. what are the best options for the fstab? I just have default right now. Is there noatime and such like ext3?
Thanks again
Offline