similar to: Disc layout advice

'--no-degraded' flag in the first mdadm call inhibits the startup of array unless all expected drives are present. This will prevent starting arrays in degraded state. Second mdadm call (after LVM is scanned) will scan unused yet devices and make an attempt to run all found arrays even they are in degraded state. Two new tests are added. This fixes rhbz1527852. Here is boot-benchmark

I thought I'd test replacing a failed drive in a 4 drive raid 10 array on a CentOS 5.2 box before it goes online and before a drive really fails. I 'mdadm failed, removed', powered off, replaced drive, partitioned with sfdisk -d /dev/sda | sfdisk /dev/sdb, and finally 'mdadm add'ed'. Everything seems fine until I try to create a snapshot lv. (Creating a snapshot lv

Hi Chris, thanks for your answer. It is the first time I decided to encrypt my lvm. I choosed to encrypt the volume group, not every logical volume itself, because in case of doing lvm snapshots in that group they will be encrypted too? And how do I create a new encrypted volume group? Regards Tim Am 6. M?rz 2015 01:58:23 MEZ, schrieb Chris Murphy <lists at colorremedies.com>: >On

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2168506 This small set covers the new /dev/mapper/VG-LV "--key" ID format in the libguestfs LUKS-on-LVM inspection test. Thanks, Laszlo Laszlo Ersek (3): update common submodule LUKS-on-LVM inspection test: rename VGs and LVs LUKS-on-LVM inspection test: test /dev/mapper/VG-LV translation common

Requires this series: https://www.redhat.com/archives/libguestfs/2019-November/msg00036.html

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2168506 This small set covers the new /dev/mapper/VG-LV "--key" ID format in the LUKS-on-LVM virt-inspector test. Thanks, Laszlo Laszlo Ersek (3): update common submodule inspector: rename VGs and LVs in LUKS-on-LVM test inspector: test /dev/mapper/VG-LV translation in LUKS-on-LVM test common

Hi, I'm trying to set up an iscsi 12.5 TB storage for some data backup. Doing so, I had some difficulties to find the right tool, maybe it's also a question of the system settings... The server is a 32Bit CentOS 5.3 with the recent updates. Ths iscsi connection can be establised. fdisk and parted fail to create any information on the device or fail completely. using the lvm tools

Hi there, I am using tar to backup the whole system (specific directorues usr,lib,sbin,etc,var,home,root). On bare metal recovery I install the minimal portion of the syetm and then I throw the tarballs. Any opinions? D. Karapiperis -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all, I had centos 5.9 installed with one of its volumes (non-root) on LVM: ... /dev/vgapps/lvapps /opt/apps ext3 defaults 1 2 ... Then installed centos 6.4 on this servers but without exporting this volume (I wanted to reuse it). After that instead importing it I did: # pvcreate /dev/sddlmac # vgcreate vgapps /dev/sddlmac And then realised that I should have

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

Hello, Maybe someone can help me.... I have a guest XEN image that ran well until today. I use an LVM partition to host the guest and today on Dom0 I added another LVM to be available to this domU. This were all the commands I issued : On hypervisor lvcreate -n lintra02data -L 30G rootvg vi /etc/xen/lintra02 and add volume to file like this : disk = [

Hi all I want to shrink one of my LVM based domU''s, but don''t quite know how to do it. I have searched the Wiki & HOWTO''s, and they all show you how expand / enlarge a LVM based domU, but not shrinking it. So, I stopped (destroyed) the domU, and then resized it as follows: lvresize /dev/data/cpanel1 -L10GB (It was 100GB), but when I a started it up again, I

Add the 'label' optional argument to the mkfs action, so it is possible to set a filesystem label direct when creating it. There may be filesystems not supporting changing the label of existing filesystems but only setting it at creation time, so this new optarg will help. Implement it for the most common filesystems (ext*, fat, ntfs, btrfs, xfs), giving an error for all the others, just

Hi, >> Yes, here's the layout from the vm: >> >> # df -h >> Filesystem Size Used Avail Use% Mounted on >> devtmpfs 7.9G 0 7.9G 0% /dev >> tmpfs 7.9G 0 7.9G 0% /dev/shm >> tmpfs 7.9G 643M 7.3G 9% /run >> tmpfs 7.9G 0 7.9G 0%

This series fixes inspection in the case that fstab contains references to md devices. I've made a few changes since the previous posting, which I've summarised below. [PATCH 1/8] build: Create an MD variant of the dummy Fedora image I've double checked that no timestamp is required in the Makefile. The script will not run a second time to build fedora-md2.img. [PATCH 2/8] build:

I have a system running CentOS 6.3, with a SCSI attached RAID: http://www.raidweb.com/index.php/2012-10-24-12-40-09/janus-ii-scsi/2012-10-24-12-40-59.html For disaster recovery purposes, I want to build up a spare system which could take the place of the server hosting the RAID above. But here's what I see: # fdisk -l /dev/sdc WARNING: GPT (GUID Partition Table) detected on

Trying to setup a volume group with puppet lvm and this:- volume_group { "my_vg": ensure => present, physical_volumes => "/dev/sdb /dev/sdc /dev/sdd", require => [ Physical_volume["/dev/sdb"], Physical_volume["/dev/sdc"], Physical_volume["/dev/sdd"] ] } Fails with this in the debug

On Thu, 2015-06-25 at 11:50 -0400, Robert Heller wrote: > At Thu, 25 Jun 2015 11:03:18 -0400 CentOS mailing list < > centos at centos.org> wrote:HA! You only really need to learn *one* > command: the man command. > The man > provides 'enlightenment' for all other commands: > man vgdisplay > man lvdisplay > man lvcreate > man lvextend > man lvresize

sorry corrections: For this test I created a 40GB lvm volume group with /dev/sdb and /dev/sdc then a 40GB LV then a 60GB VDO vol (for testing purposes) vdostats --verbose /dev/mapper/vdoas | grep -B6 'saving percent' output from just created vdoas [root at localhost ~]# vdostats --verbose /dev/mapper/vdoas | grep -B6 'saving percent' physical blocks : 10483712

Hi all, I would like to use libguestfs to manage the virtual disk images of virtual machines on XenServer, which is a virtualization platform. When I try to do some test of the Java codes contained in the libguestfs package, the following error promped up: Exception in thread "main" java.lang.UnsatisfiedLinkError: no guestfs_jni in java.library.path at