similar to: Re: Problem on slow keystroke response - guest on Xen box

--- Javier Barroso <javibarroso@gmail.com> wrote: > On Wed, Dec 3, 2008 at 7:55 AM, Stephen Liu <satimis@yahoo.com> > wrote: > > > > > Hi Javier, > > > > > > Further to my late posting; > > > > > > After installing udev on next boot the guest was completely cut off > > from outside world. It can''t be

Hi, I''m using puppet 2.7.3 on RHEL/CentOS and I have an issue which is now a big blocking issue within my environment. What I''m trying to accomplish wit puppet is a create a mountpoint, mount a filesystem on it and install an application on that filesystems are set proper user/ group and permissions on it, but it fails big time. The issues I currently run into are about 3

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.

On Fri, May 8, 2009 at 10:14 AM, Javier Barroso <javibarroso@gmail.com> wrote: > Hello, > > I have a etch xen server with a virtual machine with 2 network > interfaces configured. Every interface has a different mac, and inside > the host has a different ip. > > However I can see with tcpdump and arpwatch (I discover this because > arpwatch told me), about the two ips

I have a series of unmounted lv's that are used in xen vm's of various flavors in a lab environment. I made a script that I use to backup all of them prior to doing anything I may need to undo and all I execute is: dd if=/dev/vgname/lvname of=/dir/name.img Are there any additional parameters I should use? I haven't tried to restore this into an lv, but I did swap the 'phy'

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

On Fri, May 06, 2016 at 06:19:35PM +0000, Wes James wrote: > 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

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

Hi. I'm currently trying to configure a kickstart script to do auto installs. We split up the partitions so that we have control on the mount security like setting no execute on the tmp portions etc . I keep hitting the same error : "Could not stat /dev/VolGroup00/LogVol_root --- No Such file or directory The device apparently does not exist; did you specify is correctly " Even

I have a kickstart file with the following partitioning directives: part /boot --fstype ext3 --onpart=sda1 part pv.100000 --onpart=sda2 --noformat volgroup vol0 pv.100000 --noformat logvol / --vgname=vol0 --name=lvol1 --useexisting --fstype=ext4 logvol /tmp --vgname=vol0 --name=lvol2 --useexisting --fstype=ext4 logvol swap --vgname=vol0 --name=lvol3 --useexisting logvol /data --vgname=vol0

On May 06, 2016, at 12:37 PM, John R Pierce <pierce at hogranch.com> wrote: On 5/6/2016 11:28 AM, John R Pierce wrote: On 5/6/2016 11:19 AM, Wes James wrote: sudo resize2fs /dev/lvname/root I get: resize2fs: Bad magic number in super-block while trying to open /dev/lvname/root Couldn't find valid filesystem superblock. what file system type is this /dev/lvname/root ?

> > From: Scott Robbins <scottro11 at gmail.com> > Date: May 06, 2016 12:32:55 PM > To: CentOS mailing list <centos at centos.org> > Subject: Re: [CentOS] resize lvm > > On Fri, May 06, 2016 at 06:19:35PM +0000, Wes James wrote: > > 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

Hello Gentlemen, I would like to ask a question about an issue I have with the Centos 6.3 installation. I have installed a Centos 6.3 on a server we used before with 5.4 on Friday. I have created a KS file to let me connect to the server via VNC and have all repos and packages preconfigured. I only needed to partition the hard drive using VNC. During the partition process I selected which

hi, The problem: for kvm/qemu disks are /dev/vdx devices when using the virtio driver. For vmware, drives are /dev/sdx devices. For hp servers, /dev/ccisss/whatever (sorry, no proliant with an array controller handy to check it). in order to just have one kickstart script to maintain I am trying to use the %pre section but getting a bit stuck. This is what I have: %pre if [ -b /dev/sda ] then

Hi, I am struggling with kickstart. What I want to achieve is a reinstall, but some data partitions should survive the install, i.e. they should not be formatted. With a single disk this works, here is the relevant part from the kickstart file (I shortened the name of the volume group) ... zerombr clearpart --none --initlabel part /boot --fstype="xfs" --label=boot --onpart=vda1 part

Hello Group, I am building a company application based on Centos 5.7 OS. The application was working earlier and creating right partitions both for hardware as well as VM. But since we introduced Centos 5.7 OS and start building application with 5.7 anaconda the hardware partitions are duplicate of VM partitions *while creating hardware partition my code looks like.* cat >

On 5/6/2016 11:19 AM, Wes James wrote: > sudo resize2fs /dev/lvname/root > > > I get: > > > > resize2fs: Bad magic number in super-block while trying to open > /dev/lvname/root > Couldn't find valid filesystem superblock. what file system type is this /dev/lvname/root ? -- john r pierce, recycling bits in santa cruz

On May 06, 2016, at 12:29 PM, John R Pierce <pierce at hogranch.com> wrote: On 5/6/2016 11:19 AM, Wes James wrote: sudo resize2fs /dev/lvname/root I get: resize2fs: Bad magic number in super-block while trying to open /dev/lvname/root Couldn't find valid filesystem superblock. what file system type is this /dev/lvname/root ? I tried to find the type from blkid /dev/sda4

Dear All, I'm trying to create a kickstart installer. I specified an option --byes-per-inode to 'logvol' command, but I got a message "No such option: --bytes-per-inode" during installation. Does anybody know a solution? The following is the lines for disk partitioning definition specified in my kickstart file. ------------------------- ## ## Disk partitioning information

Hello, I am new to Centos and this mailing list. I have an application (IntelliJ IDEA) which uses the ctrl+alt+f# key combinations to provide shortcuts. The keystrokes are bind to the ttys virtual consoles. Is there anyway to rebind the keystrokes to the application? I tried the following solution (xorg.conf edit) but my PC freezes during boot process. I had to rollback the xorg.conf changes