SCSI device not created upon a CF card plug in

[Andriy Gapon]

on 23/07/2009 18:33 Peter C. Lai said the following:
> GEOM should pick up the state change, but the bug may continue to exist
> because the CF reader is tagged as a storage device with invalid media
> when umass attaches to it on startup; there wasn't a really good way to
> actually enumerate the slice table upon insertion because the device
> does not send a disconnect/reconnect to the bus when you insert the
> card. At the time, the workaround was to tickle the device by attempting
> a mount against the whole disk, then the slice table will be enumerated.

It definitely doesn't do disconnect/reconnect, the question is does it send other
kind of notification on media insertion/change?

> Example, CF card reader on boot will be picked up as /dev/da4
> You insert card, no state change can be detected because the device
> doesn't get reset on the bus.
> mount /dev/da0 /mnt <-- will fail for obvious reasons, but now slices
> are enumerated
> mount /dev/da0s1f /mnt/mycfcard <-- ok

$ true > /dev/da0
looks cleaner and is safer way to trigger the re-tasting.
Still, this is a sub-case of polling.

-- 
Andriy Gapon