|
|
Subscribe / Log in / New account

Fedora 17 released

Fedora 17 released

Posted May 29, 2012 19:43 UTC (Tue) by drag (guest, #31333)
Parent article: Fedora 17 released

FYI

I noticed that they strongly recommend using a anaconda upgrade for Fedora 17 as it's 'special'.

http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
> There is a general warning about upgrading via. yum being unsupported at the top of this page. However Fedora 17 is very special. You should seriously consider stopping now and just using anaconda via. DVD or preupgrade, unlike all previous releases it's what the yum/rpm developers recommend. Continue at your own risk.

I was going to try to use yum because I am using btrfs subvolumes for root and home, but I'll guess I'll have to take my chances with anaconda.


to post comments

Fedora 17 released

Posted May 29, 2012 19:57 UTC (Tue) by tnluker (guest, #1086) [Link]

"2.4.3. btrfs
btrfs is not available as a target file system during installation. This is a temporary situation and will be resolved in Fedora 18. btrfs is still available after installation."

I don't know if this affects upgrades but something to be aware of in case you need to reinstall.

Fedora 17 released

Posted May 29, 2012 19:59 UTC (Tue) by kalev (guest, #58246) [Link]

Yum upgrades actually work fine, just need to follow special instructions at https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum...

Fedora 17 released

Posted May 29, 2012 22:51 UTC (Tue) by bojan (subscriber, #14302) [Link]

Not sure whether a problem with "kernel panic" on reboot was fixed, but here is a heads up for you anyway. I hit it on 3 machines where I did upgrade using yum:

http://lists.fedoraproject.org/pipermail/devel/2012-May/1...

Just in case you don't have "hands" to push that power button for you.

Fedora 17 released

Posted May 30, 2012 10:48 UTC (Wed) by marcH (subscriber, #57642) [Link] (1 responses)

> I was going to try to use yum because I am using btrfs subvolumes for root and home, but I'll guess I'll have to take my chances with anaconda.

Could you please elaborate? Maybe explain a tiny bit what brtfs subvolumes are.

It's definitely possible to preserve "normal" disk partitions with Anaconda.

Fedora 17 released

Posted May 30, 2012 14:09 UTC (Wed) by drag (guest, #31333) [Link]

> Maybe explain a tiny bit what brtfs subvolumes are.

Btrfs allows you to pool storage volumes together in a manner similar to LVM.

Although, I believe, it operates at a logical data/file system layer rather then block layer like LVM does. This allows you to do fancy things like stripe your metadata using a 'RAID10' and make your data 'RAID1'. Another distinct advantage to this is that your volumes don't have to match sizes or be of even numbers. So I can create a 'RAID1' array of a 500GB disk drive with a 1TB disk drive and a third 2TB disk drive. The file system just logically makes sure that any hunk of data is available on at least two devices. Newer versions of Btrfs allow you to rebalance and restripe your volumes on the fly in addition to being able to remove and add storage devices whenever you feel like it.

Btrfs allows you to break up your pool into separate file systems. Each with their own metadata and other such things in their own namespace. These divisions are called 'subvolumes'. By using subvolumes you can take easier advantage of features like snapshotting, different mount options, quotas, and the like.

If you look at the 'root' btrfs volume then subvolumes will show up as things that are like "/.subvolname". Although you can individually mount them and access them without first mounting the root subvolume.

So on my 'home system' which I use to house many KVM guests in addition to being my main desktop system I have, IIRC, 3 1TB drives combined with 2 2TB drives in a BTRFS storage pool.

The various file systems that I use shows up on the btrfs root volume as:
/.rootfs
/.homefs
/.imagefs
etc etc.

The initrd for Fedora is sufficiently btrfs-aware that I can specify that it use a subvolume to be mounted as '/' for my OS during boot up.

Now the problem with Anaconda that I have ran into the past is that is unless it's able to support the file systems I am using that I cannot seem to be able to use it to install or upgrade Fedora.

I would like it if I could just tell Anaconda to skip the whole disk formatting and mounting BS and just use something like /mount/target/ and let me figure out how to setup the file systems after it's done it's install. If I could do that then that would be the preferred method for upgrading my OS as I can use a live CD to setup the volumes how I want it and then just use Anaconda from there.

I haven't really looked into it too deeply right now and as far as I know the 'target' option may exist. I just am not that familiar with it. I haven't had time to download the Fedora 17 installer and play around with it since my original post.

Fedora 17 released

Posted Jun 1, 2012 18:40 UTC (Fri) by charris (guest, #13263) [Link]

I didn't find either preupgrade or the DVD route to be hassle free. Preupgrade refused to work, finding the wrong boot partition sitting on another disk, unmounted at that. The DVD route put grub on the wrong disk and I wasn't able to make it do otherwise. It also left yum in dependency Heck, as apparently some *.i686 libraries I had installed weren't upgraded and some apps disappeared. Among other things, the kernel wasn't upgraded. By installing/erasing things in bits and pieces I was able to get back to a usable system but it took some work.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds