search for: vda2

...m trying to resize to a larger LVM partition. I have ntfsresize installed on the server - the windows partition is not encrypted. root at kvm1:~# ntfsresize -v ntfsresize v2011.4.12AR.4 (libntfs-3g) The attempt ends with an error Fatal error: exception Guestfs.Error("ntfsresize_opts: /dev/vda2) I have attached a txt file of the results where I have used export LIBGUESTFS_DEBUG=1 ; export LIBGUESTFS_TRACE=1 I have also tried using virt-resize --expand /dev/sda2 /dev/vgpool/w2008webtemplate /dev/vgpool/wintest2 as well as virt-resize --expand /dev/vda2 /dev/vgpool/w2008webtemplate...

...guestfs: trace: vfs_type "/dev/vda" libguestfs: trace: vfs_type = "" libguestfs: trace: mount_ro "/dev/vda" "/" libguestfs: trace: mount_ro = -1 (error) libguestfs: trace: list_partitions libguestfs: trace: list_partitions = ["/dev/vda1", "/dev/vda2"] libguestfs: trace: vfs_type "/dev/vda1" libguestfs: trace: vfs_type = "ntfs" libguestfs: trace: mount_ro "/dev/vda1" "/" libguestfs: trace: mount_ro = -1 (error) libguestfs: trace: vfs_type "/dev/vda2" libguestfs: trace: vfs_type = "ntfs...

This first factors out all the partition sizing, and then resizes the images created to be 1GB instead of 512MB, to work around a size limitation with btrfs: mkfs_btrfs: /dev/vda2: device /dev/vda2 is too small (must be at least 256 MB)

...imgfile=sheepfs_dir + "/volume/" + vdi_name >>> g.add_drive_opts(imgfile, format="raw", readonly=0) >>> g.launch() >>> root = g.inspect_os() >>> print root [] >>> g.list_filesystems() [('/dev/vda1', 'ntfs'), ('/dev/vda2', 'ntfs')]

...ctive of the host. The filesystem wasn't set on the logical volume until the guest installation occurred. 5. So then I switched over to the guest system and ran df -h to see the existing filesystem [root at guest1 jeffb]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda2 4.5G 2.3G 2.0G 53% / tmpfs 1004M 88K 1004M 1% /dev/shm /dev/vda1 485M 30M 430M 7% /boot /dev/vdb1 2.0G 219M 1.7G 12% /var 6. Then I ran resize2fs /dev/vda2 and got the result that the filesystem is already xx blocks long. Nothi...

...rmatted. 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 pv.00 --fstype="lvmpv" --onpart=vda2 --noformat volgroup v --noformat logvol / --fstype=xfs --name=wurzel --vgname=v --useexisting logvol /home --fstype=ext4 --name=home --vgname=v --noformat ... you see, / will be reformatted, /boot will be reformatted, but /home will not. Now a machine with md raid 1. I tried the following....

...Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x942d1f03 Device Boot Start End Blocks Id System dev/vdal * 2048 1026047 512000 83 Linux dev/vda2 * 1026048 41943039 20458496 8e Linux LVM Hmm, it seems that the boot flag should be removed from /dev/vda2 partition? (How we do that?) > BTW: are you using virt-manager to configure/run your VMs? Or direct virsh > commans or what? It's a hosted VPS service, and I have a virtual c...

...m Partition > 4 22646784 25163775 1.2 GiB 8200 SWAP System Partition > > > # fdisk -l /dev/vda > ... > Disklabel type: gpt > ... > Device Start End Sectors Size Type > /dev/vda1 2048 411647 409600 200M EFI System > /dev/vda2 411648 1435647 1024000 500M Linux filesystem > /dev/vda3 1435648 22646783 21211136 10.1G Linux filesystem > /dev/vda4 22646784 25163775 2516992 1.2G Linux swap > > > # fatlabel /dev/vda1 > labelefi > > # e2label /dev/vda2 > labelboot > > # e2label...

Hi,everyone: As the subject says, why chinese characters are shown as '?' by using ls function? Did anyone encounter the same problem and does resolution exist? Looking forward to your reply. Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL:

...lesystem interactive shell for editing virtual machine filesystems. Type: 'help' for help on commands 'man' to read the manual 'quit' to quit the shell Operating system: Fedora release 16 (Verne) /dev/mapper/vg_f16x64-lv_root mounted on / /dev/vda2 mounted on /boot ><fs> mountpoints /dev/vg_f16x64/lv_root: / /dev/vda2: /boot (or 'mounts' which does the same but only lists the devices). Please send replies to the mailing list. I hopefully deleted any specifics of your environment in this reply. Rich. -- Richard...

On Fri, May 5, 2017 at 12:52 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 5/5/2017 1:42 ??, Nikolaos Milas wrote: > > Hmm, it seems that the boot flag should be removed from /dev/vda2 >> partition? >> > > Actually, I tried this and left the boot flag only to /dev/vda1. I > rebooted and I am still getting the same error. :-( > > I was hoping we were close to a solution... > > > Nick > _______________________________________________ > Cent...

...bguestfs filesystem interactive shell for editing virtual machine filesystems. Type: 'help' for help on commands 'man' to read the manual 'quit' to quit the shell ><fs> add /dev/dm-40 ><fs> run ><fs> inspect_os ><fs> pvs /dev/vda2 unknown device ><fs> lvs /dev/vg_kojit/lv_root /dev/vg_kojit/lv_swap ><fs> mount /dev/vg_kojit/lv_root / libguestfs: error: mount: mount_stub: /dev/vg_kojit/lv_root: No such file or directory ><fs> ><fs> The actual information about VM's block devices can be...

...ab match the actual UUID > as reported by blkid? And remove/etc/lvm/cache/.cache if it exists Thank you Marcelo for replying, The directory /etc/lvm/cache/ is empty. And, yes, the UUID matches: # blkid /dev/vda1: UUID="297e2939-d6f5-431a-9813-9848368ee306" TYPE="xfs" /dev/vda2: UUID="OR1eUA-1hhb-PCff-qybQ-rLt4-JuTN-EcWX61" TYPE="LVM2_member" /dev/sr0: UUID="2017-03-16-21-15-06-00" LABEL="ISOIMAGE" TYPE="iso9660" PTTYPE="PMBR" /dev/mapper/centos-root: UUID="fcee6215-e97a-4a4f-9473-5115f8559683" TYPE=&...

...uot; >/home/vmail/brain-force.ch/tobster/.dovecot.test $ cat /home/vmail/brain-force.ch/tobster/.dovecot.test test $ echo "test1" >/home/vmail/brain-force.ch/tobster/.dovecot.test $ cat /home/vmail/brain-force.ch/tobster/.dovecot.test test1 Mounts show that the FS should be rw /dev/vda2 / ext4 rw,relatime,data=ordered 0 0 I restarted dovecot several time already. As well I restarted the physical host on which the dovecot vms reside. Filesystems are not full and are not running out of inodes. Does anyone have an idea why dovecot suddenly behaves like that? Thanks a lot for any...

...648 22646783 10.1 GiB 8300 ROOT System Partition 4 22646784 25163775 1.2 GiB 8200 SWAP System Partition # fdisk -l /dev/vda ... Disklabel type: gpt ... Device Start End Sectors Size Type /dev/vda1 2048 411647 409600 200M EFI System /dev/vda2 411648 1435647 1024000 500M Linux filesystem /dev/vda3 1435648 22646783 21211136 10.1G Linux filesystem /dev/vda4 22646784 25163775 2516992 1.2G Linux swap # fatlabel /dev/vda1 labelefi # e2label /dev/vda2 labelboot # e2label /dev/vda3 labelroot # swaplabel /dev/vda4 LABEL: labe...

...#include <string.h> #include <libintl.h> #include <error.h> +#include <errno.h> #include <assert.h> #include "c-ctype.h" @@ -37,31 +38,27 @@ #include "options.h" /** - * Make a LUKS map name from the partition name, - * eg. C<"/dev/vda2" =E<gt> "luksvda2"> + * Make a cryptsetup map name from the partition name, + * eg. C<"/dev/vda2" =E<gt> "cryptvda2"> */ -static void -make_mapname (const char *device, char *mapname, size_t len) +static char * +make_mapname (const char *dev...

On 5/5/2017 5:11 ??, Barry Brimer wrote: > Are the correct volumes referenced in your /etc/default/grub file? Thanks Barry for your feedback. Here is the output: http://iweb.noa.gr/files/centos7/scratchvm-data-20170505-01.png What can you tell from that? Cheers, Nick

On Sat, Apr 14, 2012 at 12:20:00AM +0100, Dale Amon wrote: > I might add that virt-rescue now gets much further > than I have ever seen before... it shows a line > [ 245.032513] vda: vda1 vda2 > > before hanging forever. So it at least has gotten > to the point of recognizing the partitions on the > virtual disk I want to access. This hang is also characteristic of the ADFS problem. I don't think anything is going to change until someone fixes this kernel bug. Rich....

Hi, Sorry for the long delay. It prints exactly the same: [ 3.792033] virtqueue elements = 128, max_segments = 126 (1 queues) [ 3.802191] vda: vda1 vda2 < vda5 > A little bit more about my setup (if it helps): It's a qemu-system-x86_64 kvm instance with 16 cores and 10G of RAM. I can reproduce the bug every time with mkfs.btrfs on a 10GB LVM volume (right after the reboot). I have almost no knowledge of vring / virtio. Is it correct th...

Hi, Sorry for the long delay. It prints exactly the same: [ 3.792033] virtqueue elements = 128, max_segments = 126 (1 queues) [ 3.802191] vda: vda1 vda2 < vda5 > A little bit more about my setup (if it helps): It's a qemu-system-x86_64 kvm instance with 16 cores and 10G of RAM. I can reproduce the bug every time with mkfs.btrfs on a 10GB LVM volume (right after the reboot). I have almost no knowledge of vring / virtio. Is it correct th...