Are you saying, then, that there is no way to do the migration within the kickstart part command? And if so, is that a bug or a feature? Steve Timm ------------------------------------------------------------------ Steven C. Timm (630) 840-8525 timm@xxxxxxxx http://home.fnal.gov/~timm/ Fermilab Computing Division/Core Support Services Dept. Assistant Group Leader, Scientific Computing Support Group Lead of Computing Farms Team On Wed, 12 Feb 2003, Paul Fernandes wrote: > >From a previous post about changing from ext2 to ext3: > > ============== > You could use tune2fs -j in the %post section. > > cu > > Florian Festi > ============== > Paul > ============== > Paul Fernandes > Sr. System Administrator > > LION bioscience Research, Inc. > 141 Portland Street, 10th Floor > Cambridge, MA, 02139 U.S.A. > +1-617-245-5477 > > http://www.lionbioscience.com > > -----Original Message----- > From: kickstart-list-admin@xxxxxxxxxx > [mailto:kickstart-list-admin@xxxxxxxxxx]On Behalf Of Steven Timm > Sent: Wednesday, February 12, 2003 9:20 AM > To: kickstart-list@xxxxxxxxxx > Subject: Migrating ext2 to ext3 partitions in KS > > > > Hi everyone. > > I have a bunch of systems currently running Redhat 7.1. > They are currently partitioned as follows: > > / /dev/hda1 (3 Gb) > Extended partition /dev/hda2 > swap /dev/hda5 (2 Gb) > /inst /dev/hda6 (rest of disk) > /local/stage1 /dev/hdb1 (all disk) > /local/stage2 /dev/hdd1 (all disk) > > What I want to do is: > 1) wipe out the three partitions on the system disk and install > 7.3. > > 2) Migrate the file systems on hdb1 and hdd1, which are currently > ext2, to ext3, while saving the data. > > Both of these can easily be done when doing a manual install. > If you look at the anaconda-ks.cfg file that's made when you do that, > you get the following: (with a comment that it's not guaranteed to work) > > part / --fstype ext3 --size 3000 --ondisk hda > part swap --size 2000 --ondisk hda > part /inst --size 1000 --grow --ondisk hda > part /local/stage1 --fstype ext3 --noformat --onpart hdb1 > part /local/stage2 --fstype ext3 --noformat --onpart hdd1 > > --------------------------------------------------- > > The three partitions I requested above for hda, under a clean 7.3 install > with nothing else on the machine, would all be allocated as > primary partitions. > > If I try to run a kickstart with the above, preceded by > the statement > > clearpart --drives hda > > I get the error message that it cannot allocate the partitions as > primary partitions. > > If I take any clearpart statement out, and instead use the > old partitioning exactly as it is, e.g. > > part / --fstype ext3 --onpart hda1 > part swap --size 2000 --onpart hda5 > part /inst --fstype ext3 --onpart hda6 > part /local/stage1 --fstype ext3 --noformat --onpart hdb1 > part /local/stage2 --fstype ext3 --noformat --onpart hdd1 > > then it works fine--except it doesn't migrate the > two disks that are not formatted to ext3...they stay ext2. > > So two questions: > > 1) Is there a bug in the clearpart command? If we do > clearpart --drives hda, shouldn't we be able to put any partition > structure on there we want? > > 2) Is there any way to get the disks to migrate from ext2 to ext3 > during kickstart? > > Thanks for your help. > > Steve Timm > > > > > ------------------------------------------------------------------ > Steven C. Timm (630) 840-8525 timm@xxxxxxxx http://home.fnal.gov/~timm/ > Fermilab Computing Division/Core Support Services Dept. > Assistant Group Leader, Scientific Computing Support Group > Lead of Computing Farms Team > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list >
