similar to: about lvm filesystem...........

Hi Folks, Anybody have any recent experience building a small cluster that combines GlusterFS and Xen (with bonus points for a Debian environment)? We''re getting ready to shift from a 2-node Xen/Pacemaker/DRBD environment to a 4-node environment - and I''d really like to be able to create/migrate/failover/delete VMs transparently across all 4 nodes. Seems like Gluster might

Hi, I''ve been building up a new HA system, running Xen on DRBD devices. Configuration this applies to: Debian Lenny xen-linux-system-2.6.26-2-xen-686 package |**|drbd8-modules-2.6.26-2-686 drbd8-modules-2.6.26-2-xen-686 As I''ve been building the system, I ran into an interesting problem, with two symptoms: 1. running VMs would come back up after a reboot, but would hang on

Hi Folks, I find myself trying to expand a 2-node high-availability cluster from to a 4-node cluster. I'm running Xen virtualization, and currently using DRBD to mirror data, and pacemaker to failover cleanly. The thing is, I'm trying to add 2 nodes to the cluster, and DRBD doesn't scale. Also, as a function of rackspace limits, and the hardware at hand, I can't separate

Greetings - I had a logical volume that was running out of space on a virtual machine. I successfully expanded the LV using lvextend, and lvdisplay shows that it has been expanded. Then I went to expand the filesystem to fill the new space (# resize2fs -p /dev/vde1) and I get the results that the filesystem is already xx blocks long, nothing to do. If I do a # df -h, I can see that the

Hi list. I''m running Xen 4.0.1 on Debian. I''m trying to live resize a block device : - I have a arbitrary block device in my dom0 (/dev/mapper/vm-vol42). - I start a PV domain with that device as a disk (disk = [''phy:/dev/mapper/vm-vol42,xvda,w'']). - I resize vm-vol42 in the dom0 (adding size only) - the dom0 sees the device''s new size. -

I''ve installed debian lenny amd64, it is frozen now. I''ve install kernel for xen support but it doesn''t start. It says "you need to load kernel first" but I''ve installed all the packages concerning xen, also packages related to the kernel. Perhaps lenny doesn''t support xen anymore? Any solution?

Hi Folks, I''ve been getting just a little fed up with the state of Xen on Debian Lenny - there are a couple of known bugs that lead to periodic kernel panics - but fixes haven''t made it into the Lenny distribution. I''m sort of waiting to see how things shake out with Debian Squeeze, when it becomes stable, but... I''ve been noticing that Suse (both the

Hi guys, I''ve seen this post regarding "lvm resize" and this contains all the information I need to resize a disk inside domU : http://lists.xensource.com/archives/html/xen-users/2006-11/msg00019.html >From this post: "With this I can extend the LVs in the Dom0, and either shutdown the DomU and resize2fs from Dom0 or even (tested on test VMs and low-use

I found a thread that has almost the exact same symptoms as me, but didn't seem to come to a resolution: https://listman.redhat.com/archives/ext3-users/2004-December/msg00018.html I have an LVM(2) array that I've just lvextend'd and want to resize2fs, but I can't get through the e2fsck. I get these errors when fsck-ing: Group 3125's inode table at 102400545 conflicts with

I have a laptop that I put centos 7 on and I started out with a 30gig partition.? I resized the other part of the disk to allow more space for centos.? I then created an unformated partition in the available space,? ran pvcreate /dev/sda4 vgextend lvname /dev/sda4 lvextend -L 184.46G /dev/lvname/root but when I run: sudo resize2fs /dev/lvname/root I get: resize2fs: Bad magic

Hello everybody, I''m playing with Xen and trying to extend DomU disk space. My Configuration: Dom0: all Xen machine are HVM. They''re installed on LVM. I''ve one VG (XEN) on Dom0 and created a LV (here, xps.101.disk) per DomU. disk configuration in xen conf is as follow: disk = [ ''phy:/dev/XEN/xps.%d.disk,ioemu:hda,w'' % (vmid)

Hey all, I''m trying to figure out how to re-size physical partitions in the Dom U. I''ve read up what I can find on line and finally decided to have Logical Volumes in the Dom 0 and pass them as physical volumes for use in the Dom U. Here''s an example of what I''m doing. To start in the Dom 0 I created the LV''s with lvcreate -n guest_boot -L 100M

I'm running CentOS 5.2 x x86_64. I did an lvextend of a logical volume, and proceeded to run one of the ext2 utilities (e.g. ext2online, ext2resize) and found to my surprise that it wasn't on there. So I started googling around, and as far as I can see, though I'm not sure, they're supposed to be a part of the e2fsprogs package. Well, it's installed on the system, at least

Hi. I'm attempting to setup a box here to be a file-server for all my data. I'm attempting to resize an ext3 partition to demonstrate this capability to myself before fully committing to this system as the primary data storage. I'm having some problems resizing an ext3 filesystem after I've resized the underlying logical volume. Following the ext3 resize, fsck spits out lots

Hello, I am using Xen 4.0.1 and Xen 3.2.1 dom0 with Debian Lenny and Squeeze dom0s. I have a bunch of virtual machines running , all using LVM as backend storage. Mostly, an LVM logical volume is mapped to a partition in the VM (eg: xvda1) I have tried to hot resize the filesystem in the VM without umounting it but it just do not work... Here is what I did: - lvextend on the dom0, -

Hi all! I've got a VM at work running C6 on HyperV (no, its not my fault, that's what the company uses. I'd rather gag myself than own one of th ose things.) I ran out of disk space in the VM, so the admin enlarged the virtual disk. but now I realize I don't know how to enlarge the partition and its filesystem. I'll be googling, but in case I miss it, it'd be great if

I'm trying to extend a logical volume and I'm doing as follow: 1- Run `fdisk -l` command and this is the output: Disk /dev/sda: 85.9 GB, 85899345920 bytes 255 heads, 63 sectors/track, 10443 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier:

I came across an old post comment yesterday (from http://echenh.blogspot.com/2010/04/how-to-extend-lvm-on-vmware-guest-os.html ) discussing the "hack" of LVM on Linux VM guests and whether it's better not to use it to simplify disk management. I've re-posted the comment below, does it sound reasonable? Is it better to not use LVM on Linux VM guests? --Russell

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

On Wed, June 24, 2015 16:11, Chuck Campbell wrote: > > Is there an easy to follow "howto" for normal LVM administration > tasks. I get tired of googling every-time I have to do something > I don't remember how to do regarding LVM, so I usually just > don't bother with it at all. > > I believe it has some benefit for my use cases, but I've been >