similar to: Resizing ext4 fedora qemu guest

Package: xcp-xapi Version: 1.3.2-14 I've expanded the underlying volume for the SR xe sr-scan doesn't seem to detect the new space I've tried various things: - using pvresize so that LVM detects the bigger partition pvresize /dev/sda6 and the pvscan command now shows the correct space. running "xe sr-scan uuid=$UUID" after this failed to detect the space -

Hi, We have some problems with Xen 4.0.1 and resinzing of lvm volumes. When I resize a lvm volume with "lvresize -L+50G -n /dev/data/windows-data" the Windows Dom U don''t scan the new size of the lvm volume. The only way to see the extend is to halt and create the DomU We have try with sign and unsigned drivers gplpv, with Windows 2008 and Windows 2003 server :

Hi! I am experiencing strange behavior with my new CentOS 6.3 installation (system up to date). I have a big 11 TB EXT4 array mounted on /home/data. The server is a Tyan 2U (TA26-B3992-E) with Dual Opteron 2216, one cpu has 4 Gigs RAM and the other has 8 Gigs (so 12 Gigs total). The server uses 8 x Seagate 2TB SAS hard disks (7200 RPM) and all the disks are grouped together to form 1

I have a fesh install of CentOS release 6.6 on my laptop. I want to use a more secure config with /home crypted. But when this partition is mounted I cannot login anymore on my laptop. Only root can login. This occur at level 5 (graphic login) or 3 (text login). The message is "Cannot enter home directory. Using /." Logged as root I can create a new user (with useradd) and his home

Yeah:) I''d like to work on this. Here are my first observations: - We need to call vdev_op_asize method with additonal ''offset'' argument, - We need to move data to new disk starting from the very begining, so we can''t reuse scrub/resilver code which does tree-walk through the data. Below you can see how I imagine to extend RAIDZ. Here is the legend:

Hi , Trying to attach a disk to existing VM using virsh attach-device - XML <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none' io='native'/> <source file='/var/lib/libvirt/images/guest.qcow2'/> <target dev='vdc' bus='virtio'/> </disk> After

Hi Steven, Read/Write errors are recorded when an active path of the geom_multipath device is pulled while running the i/o on dataset created for the pool. Running I/o on dataset using dd. *Freebsd version :* 9.0 *Patch imported from stable 9 : *r229303, r234916 *zpool status:* * * pool: poola state: ONLINE scan: none requested config:

On Oct 8, 2014, at 10:28 AM, Jelle de Jong <jelledejong at powercraft.nl> wrote: > Hello everyone, > > I been using CF cards for almost more then 7 years now with ext > file-system without any major problems on ALIX boards. > > Last year I took 30 other systems in production with ext4 and the CF > cards been dropping out pretty fast, it may have been a bad batch but

Hi, There is a difference between the help of lvresize and its man page. In the manpage, there is nothing about the -r or --resizefs function. Centos4. [root at serv01 ~]# lvresize Please specify either size or extents (not both) lvresize: Resize a logical volume lvresize [-A|--autobackup y|n] [--alloc AllocationPolicy] [-d|--debug] [-h|--help]

Hello All, the update to Centos6.6 got interrupted on a laptop. I then did this: package-cleanup --cleandupes yum-complete-transaction and remove and reinstall the latest kernel. I now get an error message when booting: /dev/mapper/vg_jvermeulen-lv_home does not exist. I can boot into single user mode and run all commands. in fdisk -l .....lv_home is not listed. How can I re-add this? I do

Dear James, Thank you for being quick to help. Yes, I could see all of them: # vgs # lvs # pvs Regards, Khem On Sat, February 28, 2015 7:37 am, James A. Peltier wrote: > > > ----- Original Message ----- > | Dear All, > | > | I am in desperate need for LVM data rescue for my server. > | I have an VG call vg_hosting consisting of 4 PVs each contained in a > | separate

Side note: In CentOS-6, I noticed a new option in lvresize / lvextend: -r, --resizefs Resize underlying filesystem together with the logical volume using fsadm(8). Nice. Two steps (lvresize and resize2fs) can now be combined into one! Works great. But that has nothing to do with my question, just thought I'd share the discovery. == Anyway, here's

I need to shrink /home(755G) to 150GB and use free space to add to the existing /(50G). #df -kh Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_web-lv_root 50G 7.8G 40G 17% / tmpfs 7.8G 384K 7.8G 1% /dev/shm /dev/sda2 485M 79M 381M 18% /boot /dev/sda1 200M 256K 200M 1% /boot/efi /dev/mapper/vg_web-lv_home755G 6.2G 711G

----- Original Message ----- | Dear All, | | I am in desperate need for LVM data rescue for my server. | I have an VG call vg_hosting consisting of 4 PVs each contained in a | separate hard drive (/dev/sda1, /dev/sdb1, /dev/sdc1, and /dev/sdd1). | And this LV: lv_home was created to use all the space of the 4 PVs. | | Right now, the third hard drive is damaged; and therefore the third PV |

Hi all, i''ve a Problem :) I tried to resize a disk of my data guest from 100 to 400 GB. I did an lvresize /dev/xendata/data-disk -L 400G an it works. I started the Guest and did an df -h to check the size but there are still 100 G :( Can somebody tell me whats wrong? i dont want to lose my data at the Disk! The Machine is Debian Lenny and the guest OS also. King Regards Florian Rahmann

Hello, I did df -h on my CentOS 6.4 machine. $ df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_ysg-lv_root 47G 8.8G 36G 20% / tmpfs 948M 372K 947M 1% /dev/shm /dev/sda1 485M 62M 398M 14% /boot /dev/mapper/vg_ysg-lv_home 4.6G 2.7G 1.7G 63% /home What I don't understand is why

Is there a way for a domU to discover size changes of block devices modified by dom0? To make it clear - if I do in dom0 a lvresize of a logical volume given as physical disk to a domU, is there a way to use the new size of this device within the domU without reboot? Thanks Ralf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Dear All, I am in desperate need for LVM data rescue for my server. I have an VG call vg_hosting consisting of 4 PVs each contained in a separate hard drive (/dev/sda1, /dev/sdb1, /dev/sdc1, and /dev/sdd1). And this LV: lv_home was created to use all the space of the 4 PVs. Right now, the third hard drive is damaged; and therefore the third PV (/dev/sdc1) cannot be accessed anymore. I would like

On Thu, May 28, 2020 19:38, Robert Nichols wrote: > What output do you get from: > > file -s /dev/mapper/vg_voinet01-lv_log > lsblk -f /dev/mapper/vg_voinet01-lv_log > file -s /dev/mapper/vg_voinet01-lv_log /dev/mapper/vg_voinet01-lv_log: symbolic link TO '../DM-5' dm-f lsblk -f /dev/mapper/vg_voinet01-lv_log NAME FSTYPE LABEL UUID

On 9/25/2016 12:56 PM, Robert Nichols wrote: > > What I do is have a separate logical volume for /var/lib/libvirt, > with /var/lib/libvirt/etc bind-mounted to /etc/libvirt. It keeps > all the libvirt stuff together, since the backup requirements > there are quite different from the rest of the system. this! when I create a centos system, I let anaconda setup LVM, but I hugely