search for: vdb1

Hi, I reported a bug to anaconda (rhbz 901905), but it might be btfs related. Anaconda does this: 18:49:10,317 INFO program: Running... mkfs.btrfs --data=single --label=fedora /dev/vdb1 /dev/vdc1 /dev/vdd1 /dev/vde1 18:49:10,742 INFO program: 18:49:10,746 INFO program: WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL 18:49:10,746 INFO program: WARNING! - see http://btrfs.wiki.kernel.org before using 18:49:10,748 INFO program: 18:49:10,749 INFO program: SMALL VOLUME: forcing mixed meta...

Hi, I'm trying to set up a redundant DRBD system but I'm running into trouble when I try to define a volume group. The physical backing device for the drbd resource /dev/drbd0 is /dev/vdb1. The problem is that when I do a "pvs" on the command line the physical volume is shown as /dev/vdb1. So I tried the following filter in /etc/lvm/lvm.conf: filter = [ "r|/dev/vdb.*|", "a/.*/" But this doesn't seem to haven any effect at all. The system still se...

On 16/03/2020 13:50, Marcio Demetrio Bacci wrote: > Hi, > > >Is this the machine that you cannot set the permissions on ? > Yes. > > >If so, what is the filesystem ? > Ext4 for SO and Ext4 for shared files, but I have created a pool ZFS > on this last filesystem (/dev/vdb1). > If zfs is involved in any way, you will have problems, zfs uses nfs4acls, you could try adding 'nfs4acl_xattr' to the 'vfs objects' line. Rowland

hi guys,   happy new year!!!  I encountered  a problem when we used virt-df command to display my guest disks useage. the virt-df command from pkg libguestfs-tools-c-1.36.3-6.el7_4.3.x86_64,version is  virt-df --version : virt-df 1.36.3rhel=7,release=6.el7_4.3,libvirt the output in guest with the method referred in http://libguestfs.org/virt-df.1.html#STATVFS NUMBERS is:

...ial -chardev socket,id=charchannel0,path=/tmp/a,server,nowait -device virtserialport,nr=1,chardev=charchannel0,id=channel0,name=org.libguestfs.channel.0 -device virtio-blk-pci,drive=disk1 -drive file=/srv/imgs/centos-7.2.qcow2,if=none,id=disk1 then the console showing: ><rescue> mount /dev/vdb1 /sysroot/ [ 72.552185] SGI XFS with ACLs, security attributes, no debug enabled [ 72.568377] XFS (vdb1): Mounting V4 Filesystem [ 73.379679] XFS (vdb1): Starting recovery (logdev: internal) [ 73.406398] XFS (vdb1): Ending recovery (logdev: internal) ><rescue> statvfs bash: statvfs:...

On 16/03/2020 01:55, Marcio Demetrio Bacci via samba wrote: > Hi, > > I think the error is in converting the POSIx ACl, but I don't know how to > fix this. You posted: My two DC are Samba4 (migrated of the Windows 2008 Server) and my current File Servers are Windows 2008 Server. Yet, you have a Unix domain member: netbios name = SRV-FILESERVER Is this the machine that you

...fference, but this is the disk signature. But what's interesting, this is not grub stage 1. This is a simple parted boot strap code that looks for the active bit in the MBR (the boot flag). When I do this: http://ur1.ca/ndhi3 There's the grub stage1. It's embedded in /boot (vda1) and (vdb1). When dd the 1st sector of vda1 and vdb1 to files, and diff the files, they're identical. So they're both pointing to the same LBA on each disk for stage 2. It really shouldn't matter though, whether this three step jump method is used, or grub stage 1 is written to each MBR gap and f...

...ve as a second storage disk to the KVM. I used the disk's label (/dev/disk/by-label/backups) so that I wouldn't have to worry about the device name changing down the road. When I booted up the KVM and listed the disks, I only saw "/dev/vdb". I was also expecting to see "/dev/vdb1". I ran fdisk on it only to see the partition table wasn't detected. The drive itself is OK - I can mount it successfully on the KVM host. Here's the fdisk output: Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel with di...

Hi, >Is this the machine that you cannot set the permissions on ? Yes. >If so, what is the filesystem ? Ext4 for SO and Ext4 for shared files, but I have created a pool ZFS on this last filesystem (/dev/vdb1). Dispositivo Inicializar In?cio Fim Setores Tamanho Id Tipo /dev/vda1 * 2048 62912511 62910464 30G 83 Linux Disco /dev/vdb: 5 TiB, 5497568624640 bytes, 10737438720 setores Unidades: setor de 1 * 512 = 512 bytes Tamanho de setor (l?gico/f?sico): 512 bytes / 512 bytes Taman...

...Hi, >>> >>>> Is this the machine that you cannot set the permissions on ? >>> Yes. >>> >>>> If so, what is the filesystem ? >>> Ext4 for SO and Ext4 for shared files, but I have created a pool ZFS >>> on this last filesystem (/dev/vdb1). >>> >> If zfs is involved in any way, you will have problems, zfs uses >> nfs4acls, you could try adding 'nfs4acl_xattr' to the 'vfs objects' line. > > this goes in the right direction, but it's zfsacl for ZFS. :) oh, no, hold on, this is about ZFS...

.../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. ... #zerombr #clearpart --none --initlabel part raid.01 --onpart vda1 --noformat part raid.02 --onpart vdb1 --noformat raid /boot --fstype xfs --label boot --level 1 --device md0 --noformat part raid.11 --onpart vda2 --noformat part raid.12 --onpart vdb2 --noformat raid pv.00 --level 1 --device md1 --noformat volgroup v --noformat logvol / --fstype=xfs --name=wurzel --vgname=v --useexisting logvol...

....cgi?id=1113805 [drm] Initialized bochs-drm 1.0.0 20130925 for 0000:00:02.0 on minor 0 virtio-pci 0000:00:05.0: irq 40 for MSI/MSI-X virtio-pci 0000:00:05.0: irq 41 for MSI/MSI-X vda: vda1 vda2 virtio-pci 0000:00:06.0: irq 42 for MSI/MSI-X virtio-pci 0000:00:06.0: irq 43 for MSI/MSI-X vdb: vdb1 tsc: Refined TSC clocksource calibration: 3392.169 MHz md: bind<vdb1> mdadm (350) used greatest stack depth: 12384 bytes left md: bind<vda2> md: raid1 personality registered for level 1 md/raid1:md127: active with 2 out of 2 mirrors created bitmap (1 pages) for device md127 md12...

....cgi?id=1113805 [drm] Initialized bochs-drm 1.0.0 20130925 for 0000:00:02.0 on minor 0 virtio-pci 0000:00:05.0: irq 40 for MSI/MSI-X virtio-pci 0000:00:05.0: irq 41 for MSI/MSI-X vda: vda1 vda2 virtio-pci 0000:00:06.0: irq 42 for MSI/MSI-X virtio-pci 0000:00:06.0: irq 43 for MSI/MSI-X vdb: vdb1 tsc: Refined TSC clocksource calibration: 3392.169 MHz md: bind<vdb1> mdadm (350) used greatest stack depth: 12384 bytes left md: bind<vda2> md: raid1 personality registered for level 1 md/raid1:md127: active with 2 out of 2 mirrors created bitmap (1 pages) for device md127 md12...

...ized bochs-drm 1.0.0 20130925 for 0000:00:02.0 on minor 0 > virtio-pci 0000:00:05.0: irq 40 for MSI/MSI-X > virtio-pci 0000:00:05.0: irq 41 for MSI/MSI-X > vda: vda1 vda2 > virtio-pci 0000:00:06.0: irq 42 for MSI/MSI-X > virtio-pci 0000:00:06.0: irq 43 for MSI/MSI-X > vdb: vdb1 > tsc: Refined TSC clocksource calibration: 3392.169 MHz > md: bind<vdb1> > mdadm (350) used greatest stack depth: 12384 bytes left > md: bind<vda2> > md: raid1 personality registered for level 1 > md/raid1:md127: active with 2 out of 2 mirrors > created bitm...

...uest 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. Nothing to do! So here is where I am stuck. Guest1 is my test system so it only has the / and /var logical volumes, whereas the production guest (guest...

On 08/05/2015 10:23 AM, Chris Murphy wrote: > Nothing about hd0 or hd1 gets baked into the bootloader code. It's an > absolute reference to a physical drive at the moment in time the > command is made. Is that true? If I have a system with two disks, where device.map labels one as hd0 and the other as hd1, and I swap those numbers, the resulting boot sector will differ by one bit.

...nd I get lots of these erors in my log file: Dec 4 08:53:37 mx dovecot: auth: Error: close failed in file object destructor: Dec 4 08:53:37 mx dovecot: auth: Error: IOError: [Errno 9] Bad file descriptor What could cause these error messages? My mailboxes are stored on an ext4 filesystem: /dev/vdb1 on /srv/mail type ext4 (rw,noatime) doveconf -n: # OS: Linux 3.11.2-hardened x86_64 Gentoo Base System release 2.2 ext4 auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags lda_mailb...

...const args[] = { device, NULL }; + + guestfs_push_error_handler (g, NULL, NULL); + ret = guestfs_debug (g, "exists", (char **) args); + guestfs_pop_error_handler (g); + + return ret && ret[0] != 0; +} + /* Resolve block device name to the libguestfs device name, eg. * /dev/xvdb1 => /dev/vdb1; and /dev/mapper/VG-LV => /dev/VG/LV. This * assumes that disks were added in the same order as they appear to @@ -1820,7 +1833,7 @@ resolve_fstab_device (guestfs_h *g, const char *spec, Hash_table *md_map, char *type, *slice, *disk, *part; int r; - if (STRPREFIX (spe...

...directly on these two drives properly. OK I did that and this works. ## At the GRUB boot menu, hit c to get to a shell grub> root (hd0,0) grub> setup (hd0) grub> setup (hd1) That's it. What I did to test is was I zero'd the first 440 bytes of vdb and the the first 512 bytes of vdb1. I confirmed that this disk alone does not boot at all. After running the above commands, either drive boots. NOW, I get to say I've seen stage 1.5 get used because when it did the setup, it said it was embedding /grub/e2fs_stage1_5. In the above case hd0,0 is first disk first partition which...

...ned is virtual disk (eg /dev/vda) to have a LVM partition, which in turn has a logical volume for root? It should be possible create a fresh virtual disk, add it to the VM as /dev/vdb (say), and then inside the CentOS 7 VM, partition the new disk into however many partitions you need (say /dev/vdb1 for /boot, /dev/vdb2 for swap, and /dev/vdb3 for /) and then use dd or use mkfs and rsync, etc. to copy the file systems, go a grub-install on /dev/vdb and then stop the VM and remove the /dev/vda disk from it and restart it. Oh, you might need to make sure the UUID or LABEL used to reference...