public inbox for
help / color / mirror / Atom feed
Subject: LVM2 ./WHATS_NEW lib/device/dev-cache.c
Date: Wed, 11 Apr 2012 09:12:00 -0000	[thread overview]
Message-ID: <> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	2012-04-11 09:12:03

Modified files:
	.              : WHATS_NEW 
	lib/device     : dev-cache.c 

Log message:
	Change message severity to log_very_verbose for missing dev info in udev db.
	Libudev does not provide transactions when querying udev database - once we
	get the list of block devices (devices/obtain_device_list_from_udev=1) and
	we iterate over the list to get more detailed information about device node
	and symlink names used etc., the device could be removed just in between we
	get the list and put a query for more info. In this case, libudev returns
	NULL value as the device does not exist anymore.
	Recently, we've added a warning message to reveal such situations. However,
	this could be misleading if the device is not related to the LVM action
	we're just processing - the non-related block device could be removed in
	parallel and this is not an error but a possible and normal operation.
	(N.B. This "missing info" should not happen when devices are related to
	the LVM action we're just processing since all such processing should be
	synchronized with udev and the udev db must always be in consistent state
	after the sync point. But we can't filter this situation out from others,
	non-related devices, so we have to lower the message verbosity here for a
	general solution.)


--- LVM2/WHATS_NEW	2012/04/11 01:23:29	1.2377
+++ LVM2/WHATS_NEW	2012/04/11 09:12:02	1.2378
@@ -1,5 +1,6 @@
 Version 2.02.96 - 
+  Change message severity to log_very_verbose for missing dev info in udev db.
   Fix problems when specifying PVs during RAID down-converts.
   Fix ability to handle failures in mirrored log (regression intro 2.02.89).
   Fix unlocking volume group in vgreduce in error path.
--- LVM2/lib/device/dev-cache.c	2012/03/06 02:39:25	1.74
+++ LVM2/lib/device/dev-cache.c	2012/04/11 09:12:03	1.75
@@ -497,7 +497,7 @@
 	struct udev_enumerate *udev_enum = NULL;
 	struct udev_list_entry *device_entry, *symlink_entry;
-	const char *node_name, *symlink_name;
+	const char *entry_name, *node_name, *symlink_name;
 	struct udev_device *device;
 	int r = 1;
@@ -508,20 +508,34 @@
 		goto bad;
+	/*
+	 * Report any missing information as "log_very_verbose" only, do not
+	 * report it as a "warning" or "error" - the record could be removed
+	 * by the time we ask for more info (node name, symlink name...).
+	 * Whatever removes *any* block device in the system (even unrelated
+	 * to our operation), we would have a warning/error on output then.
+	 * That could be misleading. If there's really any problem with missing
+	 * information from udev db, we can still have a look at the verbose log.
+	 */
 	udev_list_entry_foreach(device_entry, udev_enumerate_get_list_entry(udev_enum)) {
-		if (!(device = udev_device_new_from_syspath(udev, udev_list_entry_get_name(device_entry)))) {
-			log_warn("WARNING: udev failed to return a device entry.");
+		entry_name = udev_list_entry_get_name(device_entry);
+		if (!(device = udev_device_new_from_syspath(udev, entry_name))) {
+			log_very_verbose("udev failed to return a device for entry %s.",
+					 entry_name);
 		if (!(node_name = udev_device_get_devnode(device)))
-			log_warn("WARNING: udev failed to return a device node.");
+			log_very_verbose("udev failed to return a device node for entry %s.",
+					 entry_name);
 			r &= _insert(node_name, 0, 0);
 		udev_list_entry_foreach(symlink_entry, udev_device_get_devlinks_list_entry(device)) {
 			if (!(symlink_name = udev_list_entry_get_name(symlink_entry)))
-				log_warn("WARNING: udev failed to return a symlink name.");
+				log_very_verbose("udev failed to return a symlink name for entry %s.",
+						 entry_name);
 				r &= _insert(symlink_name, 0, 0);

             reply	other threads:[~2012-04-11  9:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11  9:12 prajnoha [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-12-21 13:21 zkabelac
2011-12-21 13:17 zkabelac
2011-12-21 13:14 zkabelac
2011-01-17 15:16 zkabelac
2010-05-24 22:53 agk
2005-03-21 14:51 agk

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:

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

  git send-email \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).