On Fri, Dec 05, 2014 at 08:51:51PM +0100, Goffredo Baroncelli wrote: > > From there if we really need a mount helper, it can either use a > > libbtrfs to hit the scan code or be a bash script. > > > Thanks for trying to smooth our or wrinkles in this area. It's > > definitely worth working on, I just want to make sure we recreate as > > little infrastructure as possible ;) > > This is an RFC because I am not sure about the "right" direction. > My first goal is more to start a "sane" discussion, than provide a > solution. > > But I have to point out that "btrfs device scan" usually is started > by udev, so no possibility to show [see] an error. More, btrfs dev scan is > started on a device "alone", from which is impossible to check > dev.uuid conflicts... [except if you accept to extend the analysis > to all devices] [*] Agreed with the way errors can be reported from udev hooks, the mount is IMO best time to report incomplete filesystems (aka "failed to read system error" in dmesg). Extending device scan will not help here AFAICS. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
