From: Tom <tomgparchaur@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Question about debugging the source of uevents
Date: Mon, 30 Mar 2009 16:08:58 +0000 [thread overview]
Message-ID: <49D0EE9A.3040108@gmail.com> (raw)
In-Reply-To: <49D0DA81.1020804@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
Jim Paris escribió:
> Kay Sievers wrote:
>> On Mon, Mar 30, 2009 at 17:27, Tom <tomgparchaur@gmail.com> wrote:
>>>> Are you running smartd?
>>> Yes, but I have smartd configured to ignore the hard disk if it's in
>>> standby. In syslog I have:
>>> smartd[7004]: Device: /dev/sda, is in STANDBY mode, suspending checks
>>>
>>> And thanks for answering so fast (and wasting your time too).
>> But I guess it open the device node writable, so it might trigger a
>> change event.
>
> FWIW, on my system with smartmontools 5.38,
>
> smartctl -a /dev/sda => open("/dev/sda", O_RDWR|O_NONBLOCK)
> smartctl -d ata -a /dev/sda => open("/dev/sda", O_RDONLY|O_NONBLOCK)
>
> It behaves the same in both cases. Tom, you might try adding "-d ata"
> to /etc/smartd.conf to see if it works around your problem.
>
Thanks Jim! That's even better. Now I don't have to use the nowatch udev
rule. With '-d ata' parameter the uvent isn't triggered (and I straced
it too).
> -jim
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-03-30 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 14:43 Question about debugging the source of uevents Tom
2009-03-30 14:59 ` Kay Sievers
2009-03-30 15:27 ` Tom
2009-03-30 15:33 ` Kay Sievers
2009-03-30 15:34 ` Tom
2009-03-30 15:35 ` Kay Sievers
2009-03-30 15:54 ` Jim Paris
2009-03-30 16:08 ` Tom [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=49D0EE9A.3040108@gmail.com \
--to=tomgparchaur@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).