Re: USB memory stick hotswap problems

From: Mike (mspam_at_www.ideaway.net)
Date: 09/25/04

  • Next message: Forrest Aldrich: "CVSUP "refuse" file on FreeBSD-5-Beta"
    To: freebsd-current@freebsd.org
    Date: Sat, 25 Sep 2004 15:50:30 -0500
    
    

    Although I fully understand your reasoning, there is still a major
    problem here that really should be resolved. I don't claim that I
    have a solution - but I think I have an example that really requires
    for this to be solved in some way other than "you must unmount the
    USB device before unplugging".
    If you have a USB key, sure, you can have the requirement that it
    must be unounted before being unplugged. But what about devices like
    a digital camera for example? Most of these have an automatic
    inactivity shutdown - I plug it in, I mount the umass device, I copy
    out some files to my home directory and am browsing through the
    pictures - while I do this, the camera decides that it's been inactive
    for over 60 seconds and that it should save on battery power, so it
    turns off. dmesg shows that usb device went away, but the mount point
    (naturally) remains. Now trying to unmout it says the device is busy,
    which is clearly false; forcing the camera back on causes for the
    next device to be allocated (if the first was da0, now it's da1), and
    (incidentally) using umount -f causes an instant reboot in -BETA4 for
    me. clearly all of these are bad, and in all cases I must either live
    with a randomly mounted non-existent device or reboot to remove it.
    (if there is some way of dealing with this situation currently that I
    am just not aware of, please do enlighten me)
    Mike

    On Sat, 25 Sep 2004, Doug White wrote:

    > On Sat, 25 Sep 2004, Ivan Voras wrote:
    >
    >> What is the expected behavour when umounting USB drives which have
    >> already been unplugged? :)
    >
    > panic.
    >
    > You must unmount volumes before removing them from the system. Otherwise
    > there is unflushed dirty data that will get lost, causing data corruption
    > on the volume. You will get a panic since the system doesn't know what to
    > do with the data and wants to avoid causing any further damage.
    >
    > --
    > Doug White | FreeBSD: The Power to Serve
    > dwhite@gumbysoft.com | www.FreeBSD.org
    > _______________________________________________
    > freebsd-current@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-current
    > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: Forrest Aldrich: "CVSUP "refuse" file on FreeBSD-5-Beta"

    Relevant Pages

    • Re: Unable to connect DShot II camera
      ... |> I've just bought the Oregon Scientific DShot II digital camera. ... | the camera as a generic USB device. ... | It could, as you say, be usbdevfs, if gphoto2 uses that. ...
      (Debian-User)
    • Re: Problems reading files off digital cam after mounting via USB
      ... This is the USB Device File System. ... camera, or set up Redhat's automounter to mount the camera. ... > telling me its not a bash command. ...
      (comp.os.linux.hardware)
    • usb port and driver
      ... The same exact ... I dont think ... >I get an error ststing that the USB device was not ... >I have tried cd's that came with the HP camera. ...
      (microsoft.public.windowsxp.device_driver.dev)
    • Re: Camera not found connected to USB
      ... there wasn't an "Imaging Devices" ... >Plugging in a USB device to a different USB channel, ... >list for your camera, ... >found Right click and choose Uninstall. ...
      (microsoft.public.windowsxp.general)