I had 5.4 machine. Upgraded to 5.5 today via yum upgrade. All went fine. Rebooted. Wanted to convert root partition to ext4 (I have three partitions: /boot, / and swap). All of them on software RAID 1 (root is /dev/md2). I did the following for converting
yum install e4fsprogs tune2fs -O extents,uninit_bg,dir_index /dev/md2 nano /etc/fstab # I indicated here that my /dev/md2 is of ext4
Is there guide for converting ext3 to ext4 on Fedora? I use Fedora 12 which is regularly updated. How safe is procedure for data, I have only one ext3 partition on disk which has one ntfs and that ext3 partition (and also one small swap partition).
It has crashed or failed to install on a known good system for the 5th time now. I have never had that problem with fedora before. I am now installing with ext3 instead of ext4. I am hoping for better success with it and will update. I was able to try MinGW with WINE before the first crash and I liked what I saw there. Only hoping to be able to get a good install this time.
Is that possible, I mean when I upgrade F10 to F11 with yum upgrade is there a way to 'upgrade' the filesystem to ext4 for example (with the exception of boot partition)? Or I have to reinstall fedora like new?
While changing the filesystem can I do it by parts? what I mean is for example: I have 2 partitions like '/' and '/home' with ext3, so I backup data in '/home', change '/' to ext4 then mv files from '/home' to '/' and change '/home' to ext4 and finally mv those files from '/' to '/home'. Is that possible?
Then I convert the / partition filesystem by the following steps:login as root user in multi user mode read [url], and execute tune2fs -O extents,uninit_bg,dir_index /dev/mapper/VolGroup01-LogVol00 modify /etc/fstab, change the type of / to ext4
reboot (because fsck say running it on a mounted filesystem can cause filesystem damage, so i decide to reboot to single user mode first. maybe it's a mistake here) try to boot F11 to single user mode, failed
reboot from a SystemRescueCD-1.2.0 LiveCD run e2fsck -fpDC0 /dev/mapper/VolGroup01-LogVol00 in SystemRescueCD-1.2.0 LiveCD, no error reported
reboot try to boot F11 normally(multi user mode), but it failed at: EXT3-fs: dm-0: couldn't mount because of unsupported optional features (40).
I tried rescue mode of Fedora-11-i386-netinst.iso after these steps above. The / partition can be found and mounted to /mnt/sysimage correctly. I can read/write files in / partition, and i can even yum new softwares in rescue mode, but it just can't be mounted when booting.
I'm using CentOs 5.4 (2.6.18-164.15.1.el5 #1 SMP Wed Mar 17 11:30:06 EDT 2010 x86_64). I tested out ext4 on a partition for the last few months and it seems to work fine. The issue is that quotas dont seem to work correctly on it. Is there a way to revert back to ext3? Mainly the quota tools do not work on it.
I run an upgrade and an update on a lucid lynx beta 2. --- got no problems. but about the filesystems i have some questions because it seems for me that at every system boot the system will run an fsck. somtimes it's shown up, somtimes not. but in /var/log/messages and in syslog
I have always following messages ( occured in beta 2 too ).
But first before i continue - here my disk layout:
And here my filesystem types:
This is my problem because those values are seems to be static ! ( note: this partiton is mounted but not in use ) and last not least: the drive is an external usb scsi disk. but on the other side lucid lynx is running fine on my box.
I am going to do network upgrade of my 8.04 to 10.04 LTS. I have a dual boot with Vista, and currently I can read Ubuntu partition from Vista using Ext2fsd. However, I read that using Ext2fsd with ext4 (default in 10.04) is problematic because of "extents".
My questions: Will the upgrade convert my current ext3 partition into an ext4 one? How can I keep the ext3 partition? The release notes for 10.04 say:
The simplest way to select a different file system such as ext3 at installation time is to add the partman/default_filesystem=ext3 boot parameter when starting the installer.
I have a drive with ext3 that was my old /home drive.When I moved to 9.04 I went with ext4 and just linked to my old home drive.My old ext3 drive is becoming unstable so I want to back it up.I have a 500gb ata drive (unfortunately not a sata drive) thatto wipe and put 10.04 on. I want to move my data from this backup driveIm going to back up to, to the new 10.04 until I get another hd as abackup drive.My question is, I know there is some issue between ext3 and 4 and I dontwant to get into a bind. What would be the best format for moving
I have Debian Squeeze with linux-2.6.32-5-amd64Ok, so what I did is first changed fstab ext3 to ext4, rebooted, everything looked good. Then I enabled extents and other ext4 features on my root and home partitions using commands
tune2fs -O extents,uninit_bg,dir_index /dev/sda3 tune2fs -O extents,uninit_bg,dir_index /dev/sda4 then I ran e2fsck -fDC0 /dev/sda3
I've recently installed Ubuntu 10.10 on a machine, unfortunately, the hard drive was ext3 partitioned. Is there a way of converting this partition to ext4 without having to re-format and hence reinstall the entire OS ?
I have installed ubuntu to my pc. i made 3 partitions. one for system, one for data and one for swap. two of them were ext4. after some time i have reinstalled ubuntu again. but this time i didn't put to format the second partition, but just mount it using ext4. after that i cannot open my files. checked with gparted shows that 2GB used, but with df 188MB. and in properties writes ext3/ext4 filesystem. i used chown, chgrp but didn't help. please help, these data are ver important. i cannot lose them.
How can I format a USB hard drive to ext3/ext4 or whatever file format and have full permission to read, write and execute all files afterwards? When using the command line (as ROOT of course) mkfs.ext3 /dev/sdb? Restricts the rights to ROOT as does the procedure gParted. The man mkfs did not help much. Configuring the fstab- file is a bit of a hassle, so it would be nice, if there was an option to set the permissions "correctly" right from the beginning. Setting Ubuntu (I'm using Ubuntu 9.10) up, so that it mounts USB devices not as ROOT as default but giving all users all permissions seems to be really complicated, as a guy from my local LUG told me.
I compiled a kernel using a previous kernel config after I switched to the ext4 file system. Previously it was using ext3 and the kernel compiled and ran fine. I added support for ext4 to the config but when I went to boot I had a kernel panic. The error was "kernel can't mount vfs on (8,5)". Root is on sda5, I don't know what the 8 is. I started over, using mrproper and made a new config, but got the same error. I created an initrd with the ext4 file system but then the kernel said it couldn't mount root on ext3 because of unique options. (something along those lines) I booted back into the default kernel and saw that it had a similar error right after the bios check, but it loaded fine. I'm wondering why the kernel is saying that the ext4 file system is ext3.
With the release of CentOS 5.5 ext4 is considered stable in this distribution so I decided to migrate to it. Luckily I started from migrating fresh server with CentOS 5.5 using some instruction I found on the internet. I think I shouldn�t say, that I screwed the whole thing up ;) After about 6 hours cursing, kicking, and crying I solved the task and figured the correct sequence of actions. The small problem with migrating root partition is that you can�t unmount it BTW.
During migration task, I found, that CentOS 5.5 rescue mode is somewhat broken a little in terms of ext4 support. It can mount ext4 partitions successfully. But its e2fsprogs package (tune2fs, e2fsck etc.) doesnt see ext4 partitions and say, that superblock is corrupted on a partition once is converted to ext4 (at least it did it for me. May be I should force filesystem type with -t ext4 switch?). Keep in mind, that if you screw your system up too badly, you will not be able to run tune2fs and e2fsck on it from rescue modeBut you will still able to mount it if it is not corrupted badly. In all below examples,Boot your system normally and login as root. Upgrade kernel if you wish (I usually use yum upgrade to upgrade all on new machines). Then upgrade/install some other packages