On 30/07/12 12:11, Bryn M. Reeves wrote:
On Mon, 2012-07-30 at 12:09 +0200, Erik P. Olsen wrote:
On 30/07/12 11:51, Bryn M. Reeves wrote:
On Mon, 2012-07-30 at 11:42 +0200, Erik P. Olsen wrote:
On 30/07/12 10:44, Bryn M. Reeves wrote:
What state is the device in following a resume?
(/sys/block/sd*/device/state).
What is that? I don't see anything near this path on my system. You probably
mean a faulty resume, in that case I'll have to wait til it happens again.
No, I meant what state the device is in following a resume.. It should
be "running" prior to the suspend (and at all times during normal
operation).
The above path is a sysfs attribute that indicates the state of the
block device.
E.g. for sda on my system:
$ cat /sys/block/sda/device/state
running
It says running both before and after suspend/resume.
When the problem occurs? You'll also need to adjust the device for the
one that's showing the problem. I used sda as an example as I'm
currently on a single disk machine.
No the problem didn't occur this time. It has happened twice the past ten days
and I was aware of the device address. Mine is sdc.
--
Erik
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
