All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux PM <linux-pm@osdl.org>
Subject: Re: [RFC][PATCH] swsusp: warn about USB devices in documentation
Date: Mon, 20 Feb 2006 11:36:24 +0100	[thread overview]
Message-ID: <200602201136.24893.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0602192243020.29356-100000@netrider.rowland.org>

Hi,

On Monday 20 February 2006 04:50, Alan Stern wrote:
> On Sun, 19 Feb 2006, Rafael J. Wysocki wrote:
> > The appended patch contains a warning about the possiblity to lose data
> > if any filesystems on USB devices are mounted before suspend.
> > 
> > The A:-Q: part is from my correspondence with Alan Stern (thanks Alan).
> 
> > --- linux-2.6.16-rc3-mm1.orig/Documentation/power/swsusp.txt
> > +++ linux-2.6.16-rc3-mm1/Documentation/power/swsusp.txt
> > @@ -17,6 +17,11 @@ Some warnings, first.
> >   * but it will probably only crash.
> >   *
> >   * (*) suspend/resume support is needed to make it safe.
> > + *
> > + * If you have any filesystems on USB devices mounted before suspend,
> > + * they won't be mounted after resume and you may lose data, as though
> > + * you have unplugged the USB devices with mounted filesystems on them
> > + * (see the FAQ below for details).
> 
> This isn't quite right.  The filesystems _will_ still be mounted, but 
> inaccessible (as though you have unplugged the USB devices with mounted 
> filesystems on them).
> 
> Furthermore, this may or may not happen depending on your hardware and the
> type of suspend.  So the "you _may_ lose data" part is good... but the
> "they _won't_ be mounted" part is bad.  On some types of machines (I've
> heard that Apple laptops work well) the process is very reliable; so long 
> as the battery doesn't discharge entirely -- and provided you don't 
> actually unplug the device while the machine is asleep -- you can resume 
> safely with filesystems intact.
> 
> Can you update the patch to fix this paragraph?

Sure, I will.

[I should have waited a bit longer before I posted it to Andrew.]

Greetings,
Rafael

      parent reply	other threads:[~2006-02-20 10:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 22:06 [RFC][PATCH] swsusp: warn about USB devices in documentation Rafael J. Wysocki
2006-02-19 22:13 ` Pavel Machek
2006-02-20  3:50 ` Alan Stern
2006-02-20 10:34   ` Pavel Machek
2006-02-20 13:23     ` Rafael J. Wysocki
2006-02-20 15:34     ` Alan Stern
2006-02-20 16:37       ` Pavel Machek
2006-02-20 16:41         ` Alan Stern
2006-02-20 16:43           ` Pavel Machek
2006-02-20 18:23           ` Patrick Mochel
2006-02-20 19:45             ` Alan Stern
2006-02-20 20:13               ` Patrick Mochel
2006-02-20 20:30                 ` Alan Stern
2006-02-20 20:41                   ` Pavel Machek
2006-02-20 10:36   ` Rafael J. Wysocki [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200602201136.24893.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-pm@osdl.org \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.