Created attachment 523963 [details] screenshot with loop devices Description of problem: When running graphical (vnc) installation of F16 on s390x, filtering UI shows loop devices (loop0 - loop2) in addition to DASD drives. See attached screenshot. These loop devices are: -bash-4.2# losetup -a /dev/loop0: [0001]:5674 (/squashfs.img) /dev/loop1: [0700]:3 (/run/initramfs/squashfs/LiveOS/rootfs.img) /dev/loop2: [0001]:6012 (/overlay) Version-Release number of selected component (if applicable): anaconda-16.17 How reproducible: always Steps to Reproduce: 1. start the installation in vnc mode 2. proceed to "Specialized Storage Devices" 3. inspect "Basic Devices" tab Actual results: loop devices are available to be used for the installation Expected results: loop devices are not shown
I can see this on x86_64, both alpha and beta-tc2.
David, I can reproduce this easily so in case you haven't started working on this yet you can assign it to me.
Patch proposed: https://www.redhat.com/archives/anaconda-devel-list/2011-September/msg00206.html
Discussed in the 2011-09-30 blocker bug review meeting. Rejected as a blocker bug for Fedora 16 final because it doesn't hit any release criteria, only shows up with advanced storage devices and doesn't prevent installation. However, it can't be fixed post-release and it does look bad to have non-usable devices in the installer. Accepted as NTH for Fedora 16 final.
Fixed by 9936f7037d4fbcb1401e5b5e0c46043d80b8b43f (2f133582caf371d4a21ef15d8b73093ac6d65e2d on master).
*** Bug 743858 has been marked as a duplicate of this bug. ***
I can confirm that loop devices are not shown with anaconda-16.22
let's close this, then, as anaconda is well past 16.22. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers