similar to: using an lvm for kvm vm

'--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

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

> PDC20265: IDE controller at PCI slot 0000:00:11.0 > PCI: Found IRQ 10 for device 0000:00:11.0 > PDC20265: chipset revision 2 > PDC20265: 100% native mode on irq 10 > PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary > PCI Mode. > ide2: BM-DMA at 0x8000-0x8007, BIOS settings: hde:DMA, hdf:pio > ide3: BM-DMA at 0x8008-0x800f, BIOS settings: hdg:pio,

Hi, Imagine you have a program that contains information on an entity called a Player. There can be lots of Players, say a thousand of them. Players have 20 or so attributes, two of them are an X and Y position. The Players'' attributes are updated many times per second. Now imagine you need to create a web app that shows a 2D overhead display of the all the Players. A grid should be

After some extra reading about LVM snapshots & Gluster, I think I can conclude it may be a bad idea to use it on big storage bricks. I understood that the LVM maximum metadata, used to store the snapshots data, is about 16GB. So if I have a brick with a volume arount 10TB (for example), daily snapshots, files changing ~100GB : the LVM snapshot is useless. LVM's snapshots doesn't

I'm trying to create a 500GB lv volume on a 500GB physical volume, but can't: [root at francois-pc ~]# pvscan PV /dev/sdd VG freenas lvm2 [500.00 GB / 500.00 GB free] PV /dev/sdc VG thecus lvm2 [1010.00 GB / 910.00 GB free] PV /dev/mapper/ddf1_RAIDp2 VG VolGroup00 lvm2 [931.25 GB / 0 free] Total: 3 [2.38 TB] / in use: 3 [2.38 TB]

Hi, As someone new to puppet I''m trying to work out the best way to manage different filesystems and logical volumes on different servers. Specifically I would like to be able to define on a series of nodes different LVM logical volumes to create and mount. I''m trying to do this at the moment with a define of the following type: # Manage a partition and create if needed.

I am not sure if it''s a xen bug or lvm bug, or just my bad hardware, but here''s how to reproduce: /dev/vg0/centos1 is lvm block used by a domainU, it''s 8G in size. #lvcreate -L8192M -s -n snap1 vg0 #mount /dev/vg0/snap1 /mnt do some copying files here #umount /mnt #lvremove /dev/vg0/snap1 not removed! it says can''t allocated memory #xm mem-set 0 512 #lvremove

Hi list, I'm building a NFS server on top of CentOS 8. It has 8 x 8 TB HDDs and 2 x 500GB SSDs. The spinning drives are in a RAID-6 array. They are 4K sector size. The SSDs are in RAID-1 array and with a 512bytes sector size. I want to use the SSDs as a cache using dm-cache. So here what I've done so far: /dev/sdb ==> SSD raid1 array /dev/sdd ==> spinning raid6 array I've

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

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 everybody! I'm using LVM and ext3 and am very satisfied with it. But now I have the following problem: I have a filesystem on a LV which is in use - files are created, modified and so on. To do a backup I'd like to create a snapshot of this volume which gets backup'd and then dropped. # lvcreate -s -L 20M -n snapshot /dev/vg/data lvcreate -- WARNING: the snapshot will be

!st install of 5.2; system requires custom partitioning (Scalix mail server). Boot and Swap are hard partitions, rest of drive is LVM. In LVM, three ext3 partitions: /, /home, /var/opt/scalix lvcreate failed for the last (named Scalix_02). It was the last of the three partitions and used up the remainder of the LVM space. Now 'The Installer will now exit..." And all there is is a

Hi I have defined a logical pool and a volume within it # virsh vol-create-as images_lvm myvol 2G Vol myvol created # virsh vol-list images_lvm Name Path ----------------------------------------- myvol /dev/libvirt_images_vg/myvol if I try to create another volume using the previous one as backing-vol, the creation fails with what looks like an incorrect

Just discovered that on CentOS 4.1 when you issue the command: lvcreate -s -n temp -L2G /dev/vgname/lvname to create a snapshot, you get the error message: snapshot: Required device-mapper target(s) not detected in your kernel I've checked and recheck my spelling and tried using the device created under /dev/mapper. I've tried it on both x86_64 and on i386. Works as expected under

I have a DAS w/ 6 750Gb and 6 1Tb discs I am setting up using Linux raid. The controller is a POS so each disc is exported as an R0 single volume. I used a parted and fdisk script to create 1 max size partition labeled as Linux Raid Autodetect and created the first r6 array w/ mdadm. I normally create and mark partitions as raid or lvm so people know what's going on. The first md array is

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

I'm using 'winexe': https://sourceforge.net/projects/winexe/ but this repository, compiled against samba 4.5, and works like a charm: https://sourceforge.net/u/mstowe/winexe/ci/master/tree/ I've tried to recompile them against samba 4.8 (louis repo), and compile flawlessy, but if i try to run them: winexe[10549]: segfault at 138 ip 00007fb165a2f3a4 sp 00007ffdf432a880 error

Me thinks the docs might need a bit of fleshing out ;P http://mongrel.rubyforge.org/docs/mongrel_cluster.html At the very least, what vars can go in its config. Joe -- Posted via http://www.ruby-forum.com/.

I'm trying to install CentOS 2.1 on SATA drive that lives on ICH7R controller. I have the controller setup in BIOS to "compatibility" mode, which means it should look just like regular IDE controller to the OS. In this mode, ide0 and ide1 are PATA controllers, and 4 SATA ports are mapped to ide2 and ide3. If I boot from the 2.1 installation CD, all the drives are detected