search for: vda1

...m to be having trouble using guestmount to mount a Fedora 24 disk that is using XFS.  This is the error messings I get when I try: root@cpdev-cn5:/var/lib/libvirt/images/base# guestmount --rw -a ${disk_path}/${disk_name} -m /dev/${target}1 /tmp/fedora-master/ libguestfs: error: mount_options: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so guestmount: '/dev/sda1' could not be mounted. Did you mean one of these?...

...m to be having trouble using guestmount to mount a Fedora 24 disk that is using XFS.  This is the error messings I get when I try: root@cpdev-cn5:/var/lib/libvirt/images/base# guestmount --rw -a ${disk_path}/${disk_name} -m /dev/${target}1 /tmp/fedora-master/ libguestfs: error: mount_options: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so guestmount: '/dev/sda1' could not be mounted. Did you mean one of these?...

...The guest and host are freshly installed Centos 7 (host was fully patched before guest install). Guest is installed on an lvm pool residing on an md raid1 with two SATA 7200 RPM drives with their write caches off. The delay is on mounting /boot, the dmesg on the guest says: [ 23.491857] XFS (vda1): Mounting V4 Filesystem [ 46.668396] XFS (vda1): Ending clean mount [ 46.668404] SELinux: initialized (dev vda1, type xfs), uses xattr Subsequent mounts by hand on a running system last even longer - dmesg records: [ 96.442544] XFS (vda1): Unmounting Filesystem [ 100.086741] XFS (vda1):...

...trouble using guestmount to mount a Fedora 24 disk that is using XFS.  This is the error messings I get when I try: > > root@cpdev-cn5:/var/lib/libvirt/images/base# guestmount --rw -a ${disk_path}/${disk_name} -m /dev/${target}1 /tmp/fedora-master/ > libguestfs: error: mount_options: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, > missing codepage or helper program, or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > guestmount: '/dev/sda1' could not be mounted. Did you mean...

...trouble using guestmount to mount a Fedora 24 disk that is using XFS.  This is the error messings I get when I try: > > root@cpdev-cn5:/var/lib/libvirt/images/base# guestmount --rw -a ${disk_path}/${disk_name} -m /dev/${target}1 /tmp/fedora-master/ > libguestfs: error: mount_options: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, > missing codepage or helper program, or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > guestmount: '/dev/sda1' could not be mounted. Did you mean...

...just an optional blocksize argument, thus mimicking what you can already do with 'mkfs-b'. But this change will allow us in future to encode much of the rest of the /sbin/mkfs command line. Here is how it works from guestfish (with verbose & trace): ><fs> mkfs-opts ext2 /dev/vda1 blocksize:1024 mkfs_opts "ext2" "/dev/vda1" "blocksize:1024"send_to_daemon: 0x2393bc0 g->state = 3, n = 72 proc 210 (part_disk) took 0.18 seconds recv_from_daemon: 0x2393bc0 g->state = 3, size_rtn = 0x7fffd24c565c, buf_rtn = 0x7fffd24c5650 mkfs -t ext2 -b 1024 /d...

Looks working. [root at mail ~]# ls -lh / total 72K -rw------- 1 root root 8.0K Mar 13 09:56 aquota.group -rw------- 1 root root 7.0K Mar 13 09:56 aquota.user .... [root at mail ~]# repquota -a *** Report for user quotas on device /dev/vda1 Block grace time: 7days; Inode grace time: 7days Block limits File limits User used soft hard grace used soft hard grace ---------------------------------------------------------------------- rpcuser -- 12 0 0...

...trouble using guestmount to mount a Fedora 24 disk that is using XFS. This is the error messings I get when I try: > > root@cpdev-cn5:/var/lib/libvirt/images/base# guestmount --rw -a ${disk_path}/${disk_name} -m /dev/${target}1 /tmp/fedora-master/ > libguestfs: error: mount_options: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, > missing codepage or helper program, or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > guestmount: '/dev/sda1' could not be mounted. Did you mean...

...quota #quota = dict:User quota::proxy::quota #quota = fs:User quota:user quota = fs:user } The logs report the following error each time quota is requested: Mar 11 17:56:20 mail.xxxxxxx.xx dovecot[4923]: imap(xxxx): Error: Failed to get quota resource STORAGE: quota-fs: quotactl(Q_GETQUOTA, /dev/vda1) failed: No such file or directory I have no idea of which file or directory is missing. Any advice is welcome. Thanks and best regards, - Eric Grammatico _/) -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20...

Hi all : there is a problem on libguestfs-1.29.40 after command :make check libguestfs: error: mkfs_btrfs: /dev/vda1: device /dev/vda1 is too small (must be at least 256 MB) FAIL: test_btrfs_image_0 3/515 test_btrfstune_enable_skinny_metadata_extent_refs_0 libguestfs: error: btrfstune_enable_skinny_metadata_extent_refs: /dev/vda1: btrfstune: invalid option -- 'x' usage: btrfstune [options] device -S...

...ebooting one node... and VM dmesg looks like: [ 483.862664] blk_update_request: I/O error, dev vda, sector 23125016 [ 483.898034] blk_update_request: I/O error, dev vda, sector 2161832 [ 483.901103] blk_update_request: I/O error, dev vda, sector 2161832 [ 483.904045] Aborting journal on device vda1-8. [ 483.906959] blk_update_request: I/O error, dev vda, sector 2099200 [ 483.908306] blk_update_request: I/O error, dev vda, sector 2099200 [ 483.909585] Buffer I/O error on dev vda1, logical block 262144, lost sync page write [ 483.911121] blk_update_request: I/O error, dev vda, sector 2048 [...

...stfish -N fs:ext3:1G Welcome to guestfish, the libguestfs filesystem interactive shell for editing virtual machine filesystems. Type: 'help' for a list of commands 'man' to read the manual 'quit' to quit the shell ><fs> vfs-type /dev/vda1 ext3 ><fs> blockdev-getsize64 /dev/vda1 1073741312 ><fs> resize2fs-size /dev/vda1 100M ><fs> blockdev-getsize64 /dev/vda1 # container size same 1073741312 ><fs> mount-ro /dev/vda1 / # but filesystem is smaller ><fs> df-h...

FYI I set up replica 3 (no arbiter this time), did the same thing - rebooted one node during lots of file IO on VM and IO stopped. As I mentioned either here or in another thread, this behavior is caused by high default of network.ping-timeout. My main problem used to be that setting it to low values like 3s or even 2s did not prevent the FS to be mounted as read-only in the past (at least with

...ferent steps in choot environment in respect of the indication inside the image you sent. Specifically Verify if your boot partition is already mounted under /mnt/sysimage/boot in your current environment If it is mounted on another mount point in your live env go and umount it and run mount /dev/vda1 /mnt/sysimage/boot then chroot /mnt/sysimage when you are in chrooted environment, probably you don't have special files for vda and vda1 because they are dinamically created; verify with ls -l /dev/vda* If this is the case, go and create them mknod -m 660 /dev/vda b 253 0 mknod -m 660 /de...

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:

...> >> [root at mail ~]# ls -lh / >> total 72K >> -rw------- 1 root root 8.0K Mar 13 09:56 aquota.group >> -rw------- 1 root root 7.0K Mar 13 09:56 aquota.user >> .... >> >> [root at mail ~]# repquota -a >> *** Report for user quotas on device /dev/vda1 >> Block grace time: 7days; Inode grace time: 7days >> Block limits File limits >> User used soft hard grace used soft hard grace >> ---------------------------------------------------------------------- >> rpcuser -- 12 0 0 3 0 0 >> ntp -- 12 0 0 3 0 0 >>...

...ubvolume by name, mountinfo shows the name of the subvolume. When mounting a subvolume using subvolid it does not. Seems like a problem when trying to determine what is mounted. -o subvol=<name> # cat /proc/self/mountinfo | grep vda 43 34 0:29 /home /home rw,relatime shared:29 - btrfs /dev/vda1 rw,seclabel,space_cache 44 34 0:29 /boot /boot rw,relatime shared:30 - btrfs /dev/vda1 rw,seclabel,space_cache -o subvolid=<number> #cat /proc/self/mountinfo 43 34 0:29 / /home rw,relatime shared:29 - btrfs /dev/vda1 rw,seclabel,space_cache 44 34 0:29 / /boot rw,relatime shared:30 - btrfs...

...;> g=guestfs.GuestFS() >>> 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')]

...t; total 72K >>>> -rw------- 1 root root 8.0K Mar 13 09:56 aquota.group >>>> -rw------- 1 root root 7.0K Mar 13 09:56 aquota.user >>>> .... >>>> >>>> [root at mail ~]# repquota -a >>>> *** Report for user quotas on device /dev/vda1 >>>> Block grace time: 7days; Inode grace time: 7days >>>> Block limits File limits >>>> User used soft hard grace used soft hard grace >>>> ---------------------------------------------------------------------- >>>> rpcuser -- 12 0 0 3 0...

...uot;/dev/vda"] libguestfs: 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...