I think just "ext4" is enough at this point...
migration seems totally busted; the root fs and everything in its fstab is mounted before the migration routine runs, so it doesn't get its fs type changed until the *next* mount, which for this migration path pretty well misses the window of opportunity. :(
So I figure maybe "ext4migrate" to enable it, but it's not really going to do what you might hope...
Thanks, -Eric
Index: anaconda-11.4.0.64/fsset.py =================================================================== --- anaconda-11.4.0.64.orig/fsset.py +++ anaconda-11.4.0.64/fsset.py @@ -722,7 +722,7 @@ class ext3FileSystem(extFileSystem): self.name = "ext3" self.extraFormatArgs = [ "-j" ] self.partedFileSystemType = parted.file_system_type_get("ext3") - if flags.cmdline.has_key("iamanext4developer"): + if flags.cmdline.has_key("ext4migrate"): self.migratetofs = ['ext4dev']
def formatDevice(self, entry, progress, chroot='/'): @@ -758,7 +758,7 @@ class ext4FileSystem(extFileSystem): self.extraFormatArgs = [ "-j", "-I", "256", "-E", "test_fs" ]
# this is way way experimental at present... - if flags.cmdline.has_key("iamanext4developer"): + if flags.cmdline.has_key("ext4") or flags.cmdline.has_key("ext4migrate"): self.supported = -1 else: self.supported = 0
On Mon, 2008-03-31 at 17:15 -0500, Eric Sandeen wrote:
I think just "ext4" is enough at this point...
Oh, why's that? ;-) I'm okay with this part
migration seems totally busted; the root fs and everything in its fstab is mounted before the migration routine runs, so it doesn't get its fs type changed until the *next* mount, which for this migration path pretty well misses the window of opportunity. :(
I think we're better off fixing the bug here... I saw your note in bugzilla earlier but haven't had a chance to take a look today. I'll get to it hopefully tonight or tomorrow
Jeremy
Jeremy Katz wrote:
On Mon, 2008-03-31 at 17:15 -0500, Eric Sandeen wrote:
I think just "ext4" is enough at this point...
Oh, why's that? ;-) I'm okay with this part
migration seems totally busted; the root fs and everything in its fstab is mounted before the migration routine runs, so it doesn't get its fs type changed until the *next* mount, which for this migration path pretty well misses the window of opportunity. :(
I think we're better off fixing the bug here... I saw your note in bugzilla earlier but haven't had a chance to take a look today. I'll get to it hopefully tonight or tomorrow
ok, I'm too much of an anaconda/python n00b that I couldn't figure it out, but I'm sure that in your capable hands... ;)
Thanks, -Eric
anaconda-devel@lists.stg.fedoraproject.org