From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Date: Mon, 30 Mar 2009 14:43:13 +0000 Subject: Question about debugging the source of uevents Message-Id: <49D0DA81.1020804@gmail.com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="------------enigE03B16E403BCAF5A131AFF12" List-Id: To: linux-hotplug@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE03B16E403BCAF5A131AFF12 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I have a spare hard disk I don't touch the most of the time. Due to a strange reason, a change uevent is triggered some random time of the day (like 4 or more times) and then, of course, udev apply the rules, being one of them a rule which runs vol_id which then wakes up my spinned-down hard disk (debugged with echoing a 1 to /proc/sys/vm/block_dump and udevadm monitor). Well, what i want to know is if it's possible to know why the kernel is triggering the uevent in the first place. Grepping the documentation of the kernel I don't see anything about it. I know I can just comment the watch line in /lib/udev/rules.d/60-persistent-storage.rules but I wanted to know more. I'm using Archlinux which currently uses kernel 2.6.28.8 and udev 140. Thanks in advance. --------------enigE03B16E403BCAF5A131AFF12 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknQ2oEACgkQRScp7ATOSDxkEgCfR+DZyQGZPCP/yrSeFmCu6Cfn BJ8AoMJhqIzexuQBvSThaf+InpqcVrV1 =Zul+ -----END PGP SIGNATURE----- --------------enigE03B16E403BCAF5A131AFF12--