search for: blkrrpart

From: "Richard W.M. Jones" <rjones at redhat.com> In Linux, close (fd) closes the file descriptor even if it returns an error. --- daemon/file.c | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/daemon/file.c b/daemon/file.c index e0f8794..91746e0 100644 --- a/daemon/file.c +++ b/daemon/file.c @@ -483,7 +483,6 @@ pread_fd (int fd, int count, int64_t

...ze, int64_t offset, return -1; } - /* When you call close on any block device, udev kicks off a rule - * which runs blkid to reexamine the device. We need to wait for - * this rule to finish running since it holds the device open and - * can cause other operations to fail, notably BLKRRPART. 'settle' - * flag is only set on block devices. - * - * XXX We should be smarter about when we do this or should get rid - * of the udev rules since we don't use blkid in cached mode. - */ - if (settle) - udev_settle (); - return r; } @@ -575,7 +563,7 @@ do_pwrite...

This is a possibly better work-around for bug 769304, the bug where blkid runs from udev whenever a device closes, causing the subsequent operation to fail. For background to this change, see: https://rwmj.wordpress.com/2012/01/19/udev-unexpectedness/#content So far we have noticed this problem in two places (although I'm fairly certain it affects many more): - in virt-resize, after

An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20060828/ce9c7bc0/attachment.htm>

...BLKROSET' redefined /usr/include/sys/mount.h:76: warning: this is the location of the previous definition /usr/include/linux/fs.h:146: warning: `BLKROGET' redefined /usr/include/sys/mount.h:77: warning: this is the location of the previous definition /usr/include/linux/fs.h:147: warning: `BLKRRPART' redefined /usr/include/sys/mount.h:78: warning: this is the location of the previous definition /usr/include/linux/fs.h:148: warning: `BLKGETSIZE' redefined /usr/include/sys/mount.h:79: warning: this is the location of the previous definition /usr/include/linux/fs.h:149: warning: `BLKFLS...

I''ve been using lvm under centos to create the backing store for domUs and although the performance seems acceptable it has some shortcomings. The biggest of which is the LVM bug which prevents me from removing an lv (it says it is still mounted and it definitely isnt). I thought this was just a centos bug but it appears to be evident in debian and ubuntu too and I really can''t

...col loses synchronization if you 'upload' before mounting disks - 559963 libguestfs Perl programs do set locale, but still localization doesn't work - 521674 Perl modules are unversioned, but should carry version numbers - 516096 Race condition in test_swapon_label_0: /sbin/blockdev: BLKRRPART: Device or resource busy - 507810 guestfish -i / virt-inspector cannot handle spaces in filenames - 502533 Updated Polish translation of libguestfs - 501894 Some String parameters should be OptString - 501893 String parameters should be checked for != NULL - 501889 write-file does not support...

Hi, I recently installed centos for the first time and I like it! Also, I just started working with lvm. The following warnings are genertated whenever I run one of lvm commands on the external usb disk (MyBook by Western Digital). * What could be the source for those messages? * Should I worry about them (writing into the created LV's seems to work)? * If yes, how to fix them? [root