Phillip Susi wrote: > On 05/31/2010 02:00 PM, Curtis Gedak wrote: >> Unfortunately I do not think that dmraid can simply be removed at >> this point in time. Following are the reasons that I believe >> DMRaid.cc is needed for at least a while longer (perhaps a year or >> more): > > Then perhaps it could be disabled by the configure script when it > detects that you have (lib)parted 2.2?
This is a good suggestion on how to address this problem. :-) >> A) If libparted device detection is used, it takes an inordinate >> amount of time to scan devices on computer systems that do not have a >> physical floppy drive installed, but do have the BIOS set to indicate >> a floppy drive is present. This problem was tracked in GParted bug >> #351753. Missing floppy causes loop on scanning devices. >> https://bugzilla.gnome.org/show_bug.cgi?id=351753 > > How long are we talking here? I would expect a few seconds to be spent > trying to access the floppy before giving up, and the proper fix to that > is not to misconfigure the bios so that it thinks it has a floppy. > Looking at the parted bug, it seems like a NOTABUG to me. If your > system has a broken floppy, then it has a broken floppy; it really isn't > (lib)parted's job to guess that it isn't really supposed to be there at > all and hide it. If the kernel says the device exists, then > lib/g/parted should list it. > > Now if it is getting stuck for more than 15 seconds or so then that > sounds like a software bug doing too many retries before giving up. My testing showed that libparted spent 33 seconds in libparted's ped_device_probe_all() when the BIOS was misconfigured. See https://bugzilla.gnome.org/show_bug.cgi?id=351753#c20 I agree that the root cause is an improperly configured BIOS. However, some users reported that some versions of Windows would not work without this BIOS setting. Since I only use GNU/Linux I was unable to confirm this claim. See https://bugzilla.gnome.org/show_bug.cgi?id=453555#c12 > Yes, there was a serious regression in lucid for dmraid devices that you > have noticed. See lp #568050, which is unfortunately full of useless > vitriol. As I said before, upstream has moved to adding the p but > Ubuntu has had a patch for a while to revert to the old behavior of not > adding the p in dmraid. The new code that came with parted 2.2 does > insert the p, which is why it shows up when you run parted but not when > dmraid creates the device. Do you know if the new dmraid always adds the letter "p", or does it only add it when the device name ends in a number? Ideally dmraid should use the same device naming scheme as parted. ** Bug watch added: GNOME Bug Tracker #453555 https://bugzilla.gnome.org/show_bug.cgi?id=453555 -- Gparted does not list dmraid devices https://bugs.launchpad.net/bugs/554582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
