On Mon, Jul 30, 2012 at 11:01:53AM +0100, Bryn M. Reeves wrote:
> On Mon, 2012-07-30 at 06:48 -0300, Fernando Cassia wrote:
> > On Mon, Jul 30, 2012 at 6:32 AM, Bryn M. Reeves wrote:
> > > Do you see that happen a lot?
> >
> > Do you mean the error, or the sharing of scripts?
>
> The error: it's
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/bloc
On Mon, 2012-07-30 at 05:55 -0700, ny6...@gmail.com wrote:
> On Mon, Jul 30, 2012 at 09:44:24AM +0100, Bryn M. Reeves wrote:
> > On Sun, 2012-07-29 at 20:13 -0700, ny6...@gmail.com wrote:
> > > That's not a disk problem. That's the disk failing to remount itself
> > > properly after the suspend. Th
On Mon, Jul 30, 2012 at 06:20:53PM +0800, Ed Greshko wrote:
> On 07/30/2012 06:16 PM, Bryn M. Reeves wrote:
> > In this case a suggestion that for whatever reason the kernel hasn't
> > properly dealt with the removal of the device that had been assigned to
> > sdd (it presumably existed at some poi
On Mon, Jul 30, 2012 at 09:44:24AM +0100, Bryn M. Reeves wrote:
> On Sun, 2012-07-29 at 20:13 -0700, ny6...@gmail.com wrote:
> > That's not a disk problem. That's the disk failing to remount itself
> > properly after the suspend. This is very common. In fact, I wrote a script
> > (in Gentoo) to unm
On 07/30/2012 06:51 PM, Bryn M. Reeves wrote:
> Not at all but posts should be relevant to the thread and explain
> anything that other readers might need to know (like the fact that you
> don't have any problems, are running commands on a different type of
> device that's also removable etc.).
Wh
On 07/30/2012 06:35 PM, Ed Greshko wrote:
> Well... Since it is your day job. And I am sure you are willing to impart
> your wisdom on folks
>
> If a drive is not plugged into a port, then what does "running" mean?
Hummm. Now I find this "strange".
I had done a "Net" install on
On Mon, 2012-07-30 at 18:35 +0800, Ed Greshko wrote:
> On 07/30/2012 06:29 PM, Bryn M. Reeves wrote:
> > Do you have a card reader device?
>
> Yes And that is sde.
I would guess it's a multi-card reader device and those additional SCSI
device nodes correspond to empty slots within the reader
On 07/30/2012 06:29 PM, Bryn M. Reeves wrote:
> On Mon, 2012-07-30 at 18:20 +0800, Ed Greshko wrote:
>> On 07/30/2012 06:16 PM, Bryn M. Reeves wrote:
>>> In this case a suggestion that for whatever reason the kernel hasn't
>>> properly dealt with the removal of the device that had been assigned to
On Mon, 2012-07-30 at 18:20 +0800, Ed Greshko wrote:
> On 07/30/2012 06:16 PM, Bryn M. Reeves wrote:
> > In this case a suggestion that for whatever reason the kernel hasn't
> > properly dealt with the removal of the device that had been assigned to
> > sdd (it presumably existed at some point for
On 07/30/2012 06:16 PM, Bryn M. Reeves wrote:
> In this case a suggestion that for whatever reason the kernel hasn't
> properly dealt with the removal of the device that had been assigned to
> sdd (it presumably existed at some point for the sysfs path to have been
> created).
Fresh install, 2 day
On Mon, 2012-07-30 at 18:04 +0800, Ed Greshko wrote:
> On 07/30/2012 05:59 PM, Bryn M. Reeves wrote:
> > On Mon, 2012-07-30 at 17:47 +0800, Ed Greshko wrote:
> >> On 07/30/2012 04:44 PM, Bryn M. Reeves wrote:
> >>> What state is the device in following a resume?
> >>> (/sys/block/sd*/device/state).
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).
> >
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
On 07/30/2012 05:59 PM, Bryn M. Reeves wrote:
> On Mon, 2012-07-30 at 17:47 +0800, Ed Greshko wrote:
>> On 07/30/2012 04:44 PM, Bryn M. Reeves wrote:
>>> What state is the device in following a resume?
>>> (/sys/block/sd*/device/state).
>> I am not so sure that is a "good" indication of anything.
On Mon, 2012-07-30 at 06:48 -0300, Fernando Cassia wrote:
> On Mon, Jul 30, 2012 at 6:32 AM, Bryn M. Reeves wrote:
> > Do you see that happen a lot?
>
> Do you mean the error, or the sharing of scripts?
The error: it's an abnormal condition so if you are seeing that,
especially if it is happenin
On Mon, 2012-07-30 at 17:47 +0800, Ed Greshko wrote:
> On 07/30/2012 04:44 PM, Bryn M. Reeves wrote:
> > What state is the device in following a resume?
> > (/sys/block/sd*/device/state).
>
> I am not so sure that is a "good" indication of anything. I have 2 drives on
> my system /dev/sda and /d
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 tha
On Mon, Jul 30, 2012 at 6:32 AM, Bryn M. Reeves wrote:
> Do you see that happen a lot?
Do you mean the error, or the sharing of scripts?
In any case, thanks in advance for helping the community. ;-P
FC
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription opt
On 07/30/2012 04:44 PM, Bryn M. Reeves wrote:
> What state is the device in following a resume?
> (/sys/block/sd*/device/state).
I am not so sure that is a "good" indication of anything. I have 2 drives on
my system /dev/sda and /dev/sdb.
[egreshko@meimei block]$ cat /sys/block/sdd/device/state
On 30/07/12 10:44, Bryn M. Reeves wrote:
On Sun, 2012-07-29 at 20:13 -0700, ny6...@gmail.com wrote:
That's not a disk problem. That's the disk failing to remount itself
properly after the suspend. This is very common. In fact, I wrote a script
(in Gentoo) to unmount external drives before a susp
On Mon, 2012-07-30 at 06:29 -0300, Fernando Cassia wrote:
> On Mon, Jul 30, 2012 at 12:13 AM, wrote:
> > This is very common. In fact, I wrote a script
> > (in Gentoo) to unmount external drives before a suspend operation, so that
> > the numbering of disks in /dev don't become littered with 'zom
On Mon, Jul 30, 2012 at 12:13 AM, wrote:
> This is very common. In fact, I wrote a script
> (in Gentoo) to unmount external drives before a suspend operation, so that
> the numbering of disks in /dev don't become littered with 'zombie' drives.
It would be great if you could share it...
FC
--
u
On Sun, 2012-07-29 at 20:13 -0700, ny6...@gmail.com wrote:
> That's not a disk problem. That's the disk failing to remount itself
> properly after the suspend. This is very common. In fact, I wrote a script
> (in Gentoo) to unmount external drives before a suspend operation, so that
> the numbering
On Sun, Jul 29, 2012 at 09:59:56AM +0200, Erik P. Olsen wrote:
> I have an external 1 TB harddisk e-sata attached used for backups.
> The problem is that I have few times lost connection to it. I have
> taken up the habit of suspending (to RAM) when I leave the machine
> for a while and the proble
I have an external 1 TB harddisk e-sata attached used for backups. The problem
is that I have few times lost connection to it. I have taken up the habit of
suspending (to RAM) when I leave the machine for a while and the problem seems
to happen when I reactivate the system though not every time
26 matches
Mail list logo
