The scenario that you've described is exactly what I have in mind as
well. The lack of this feature, which worked fine in 2.6.21, is
holding us back on updating the kernel in our LiveUSB distribution. I
think that this is a feature that would be more and more needed as
portable storage devices start growing in capacity and speed and start
getting smaller in physical size.

Please advise us on how to accomplish this. Kernel boot option; patch;
anything! We'll take anything.

Thanks
Raymano G.

On 11/15/07, Mark Lord <lkml@rtr.ca> wrote:
quoted text
> Raymano Garibaldi wrote:
> > Hi,
> >
> > Is there a way/patch that would revert the USB mass storage
> > suspend/resume behavior to the way things worked on and prior to
> > kernel 2.6.21?
> >
> > The problem is mounting a usb drive, suspending while mounted,
> > detaching the usb drive during suspend, reattaching usb drive during
> > suspend before resume, and resuming.
> >
> > In this case the mount is lost and the drive has to be remounted after
> > resume. If the device remains attached while the computer is
> > suspended, USB_PERSIST works as expected and the device remains
> > mounted when the computer resumes. Kernel 2.6.21-x would leave the
> > mount point intact whether the device was left attached or was
> > detached and reattached while the computer was suspend.
> >
> > We need this functionality particularly in read-only live USB distros.
> > In this case the USB device is read-only and can not change while the
> > computer is suspended even if it gets detached and is reattached
> > before resume.
> ..
>
> Some kind of boot flag would cure this one nicely.
>
> I have the same issue here:  boot/run notebook from USB stick,
> eventually suspend the notebook and unplug the stick so it can
> be packed into the case for travel.
>
> Unpack at the other end, replug the stick, and resume from suspend.
> This should be doable, perhaps with a boot parameter override or something.
>
> ???
>
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/