Bug 196360 - ZFS installer 'Disk Info' selection lists md* temporary ramdisks
Summary: ZFS installer 'Disk Info' selection lists md* temporary ramdisks
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: CURRENT
Hardware: amd64 Any
: --- Affects Some People
Assignee: Devin Teske
Depends on:
Reported: 2014-12-29 18:00 UTC by Peter Grehan
Modified: 2018-06-21 15:26 UTC (History)
2 users (show)

See Also:

screenshot of the disk info tab (29.77 KB, image/png)
2014-12-29 18:00 UTC, Peter Grehan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Grehan freebsd_committer 2014-12-29 18:00:00 UTC
Created attachment 151082 [details]
screenshot of the disk info tab

When doing a ZFS install, selecting the 'Disk Info' tab lists the md0/md1 devices that are just temporary ramdisks used during installation.

This is a bit confusing: perhaps they could be filtered out as they seem to be when selecting the pool type.

(seen with the FreeBSD-11.0-CURRENT-amd64-20141222-r276066-disc1.iso snapshot).
Comment 1 Allan Jude freebsd_committer 2015-01-17 07:37:35 UTC
We had those masked at one point. I'll look into it. Most of this functionality comes from bsdconfig
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2015-03-07 13:17:28 UTC
Allan had indicated he would look at it.
Comment 3 Allan Jude freebsd_committer 2015-03-07 17:42:23 UTC
This functionality uses f_device_menu from bsdconfig

It shows every device that GEOM knows about. It would be nice to be able to filter the results.

Maybe f_device_menu() could be changed (or cloned with a new name) a bit to take the result of f_device_find() as its parameter, instead of the device type, so we could filter out specific devices before drawing the menu.
Comment 4 Devin Teske freebsd_committer 2015-03-23 18:20:01 UTC
I'm biased. GEOM correctly classifies md(4) as disks. Why should we prevent someone from creating an installation out of these devices? I can think of several reasons why it might be helpful to be able to perform an installation to md(4) devices. Removing or filtering-out these devices may seem like it's preventing a silly situation but I tend to believe it prevents clever applications.
Comment 5 Allan Jude freebsd_committer 2015-03-23 18:45:46 UTC
It seems probably more complicated than need be, but I think we should at least filter out the md devices that are created by the installer.

The function being called, by the function being called by bsdinstall, has a filter option, but that is not exposed to bsdinstall.
Comment 6 Devin Teske freebsd_committer 2018-06-21 15:26:21 UTC
Can I close as 'Works as Intended'?

Someone might want to do an "mdconfig -f" on a bunch of files creating a bunch of md(4) devices, and then create a ZFS pool out of those devices.