similar to: [PATCH node] cciss autoinstall fix

One instance of a variable being passed instead of a string and another instance of a tweak in a regular expression that doesn't work on F13. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-storage | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/ovirt-config-storage b/scripts/ovirt-config-storage index 34e84e5..4f3f174

Cleanup the translations of /dev/sdX to /dev/mapper and vice-versa. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-storage | 59 +++++++++++++++++++++++++---------------- scripts/ovirt-functions | 22 +++++++++++++++ 2 files changed, 58 insertions(+), 23 deletions(-) diff --git a/scripts/ovirt-config-storage b/scripts/ovirt-config-storage index

Cleanup the translations of /dev/sdX to /dev/mapper and vice-versa. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-storage | 24 +++++++++++++++--------- scripts/ovirt-functions | 22 ++++++++++++++++++++++ 2 files changed, 37 insertions(+), 9 deletions(-) diff --git a/scripts/ovirt-config-storage b/scripts/ovirt-config-storage index aea73f8..cf73aa4

Quote everywhere that we reference wwid in o-c-storage, o-c-boot and ovirt-functions. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 6 +- scripts/ovirt-config-storage | 178 +++++++++++++++++++++--------------------- scripts/ovirt-functions | 38 +++++----- 3 files changed, 111 insertions(+), 111 deletions(-) diff --git

Putting these out for feedback and comments. These will eventually support the new newt/python based ui for installation/configuration storage.py functions will be moved under a class for better data portability before final version --- scripts/ovirtfunctions.py | 672 +++++++++++++++++++++++++++++++++++++++++++++ scripts/storage.py | 451 ++++++++++++++++++++++++++++++ 2 files

Signed-off-by: Joey Boggs <jboggs at redhat.com> --- scripts/ovirt-config-logging | 11 +++++++++++ scripts/ovirt-early | 6 +++++- 2 files changed, 16 insertions(+), 1 deletions(-) diff --git a/scripts/ovirt-config-logging b/scripts/ovirt-config-logging index 233df67..e296ac4 100755 --- a/scripts/ovirt-config-logging +++ b/scripts/ovirt-config-logging @@ -174,6 +174,13 @@

Is this a suitable place to post this question? I'm using Samba and CUPS to provide printer servcies within my Win95/Win98/Linux LAN It works great except for my one printer that isn't supported under Linux I just can't seem to get Samba set up to provide printer drivers to the windows machines - I've been using the windows drivers sent with the printers I followed the

This set of patches introduces support for multipath devices for storage. Comments and suggestions are appreciated. Mike

This patch sets dax device 'DAXDEV_SYNC' flag if all the target devices of device mapper support synchrononous DAX. If device mapper consists of both synchronous and asynchronous dax devices, we don't set 'DAXDEV_SYNC' flag. 'dm_table_supports_dax' is refactored to pass 'iterate_devices_fn' as argument so that the callers can pass the appropriate functions.

Hi Mike, Thanks for the review Please find my reply inline. > > dm_table_supports_dax() is called multiple times (from > dm_table_set_restrictions and dm_table_determine_type). It is strange > to have a getter have a side-effect of being a setter too. Overloading > like this could get you in trouble in the future. > > Are you certain this is what you want? I agree with

This patch introduces the concept of an "Advanced Storage Configuration", specifically for automated installs (although it could be hooked into manual install), while preserving the original style of specifying LVs. It accomplishes the following: * Add an optional AppVG * Offer new optional LVs - Data2,Swap2 - as part of the new AppVG * Allows the specification of multiple disks, per VG

On Tue, May 21, 2019 at 6:43 AM Pankaj Gupta <pagupta at redhat.com> wrote: > > This patch sets dax device 'DAXDEV_SYNC' flag if all the target > devices of device mapper support synchrononous DAX. If device > mapper consists of both synchronous and asynchronous dax devices, > we don't set 'DAXDEV_SYNC' flag. > > Signed-off-by: Pankaj Gupta

On Mon, Jun 10 2019 at 5:07am -0400, Pankaj Gupta <pagupta at redhat.com> wrote: > This patch sets dax device 'DAXDEV_SYNC' flag if all the target > devices of device mapper support synchrononous DAX. If device > mapper consists of both synchronous and asynchronous dax devices, > we don't set 'DAXDEV_SYNC' flag. > > Signed-off-by: Pankaj Gupta

dm-* devices are references to existing /dev/sd* and /dev/mapper/<wwid>. We should not depend on them and only present /dev/sd* and /dev/mapper/<wwid> to the user. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-storage | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/scripts/ovirt-config-storage

This patch sets dax device 'DAXDEV_SYNC' flag if all the target devices of device mapper support synchrononous DAX. If device mapper consists of both synchronous and asynchronous dax devices, we don't set 'DAXDEV_SYNC' flag. Signed-off-by: Pankaj Gupta <pagupta at redhat.com> --- drivers/md/dm-table.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git

This patch sets dax device 'DAXDEV_SYNC' flag if all the target devices of device mapper support synchrononous DAX. If device mapper consists of both synchronous and asynchronous dax devices, we don't set 'DAXDEV_SYNC' flag. Signed-off-by: Pankaj Gupta <pagupta at redhat.com> --- drivers/md/dm-table.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git

This patch sets dax device 'DAXDEV_SYNC' flag if all the target devices of device mapper support synchrononous DAX. If device mapper consists of both synchronous and asynchronous dax devices, we don't set 'DAXDEV_SYNC' flag. Signed-off-by: Pankaj Gupta <pagupta at redhat.com> --- drivers/md/dm-table.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git

Previous implementation had staticly defined partitions to remove. This would break in the case of split Root and HostVG devices. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 11 +-------- scripts/ovirt-config-uninstall | 49 ++++++++++++++++++++++++--------------- scripts/ovirt-functions | 27 ++++++++++++++++++++++ 3 files changed, 58

Previous implementation had staticly defined partitions to remove. This would break in the case of split Root and HostVG devices. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 11 +-------- scripts/ovirt-config-uninstall | 48 ++++++++++++++++++++++++--------------- scripts/ovirt-functions | 33 +++++++++++++++++++++++++++ 3 files

Hi. I am trying to boot Xen 2.0.5 on an HP DL380 G3. It won''t. The box has an "HP Smart Array 5i" that when running normal Linux is handled by the CCISS driver. I suspect that this is what is not supported in the stock Xen kernel. Am I correct that I need to build a kernel from source ? According to http://lists.xensource.com/archives/html/xen-devel/2004-11/msg00709.html there