search for: lv_log

On Thu, May 28, 2020 19:38, Robert Nichols wrote: > What output do you get from: > > file -s /dev/mapper/vg_voinet01-lv_log > lsblk -f /dev/mapper/vg_voinet01-lv_log > file -s /dev/mapper/vg_voinet01-lv_log /dev/mapper/vg_voinet01-lv_log: symbolic link TO '../DM-5' dm-f lsblk -f /dev/mapper/vg_voinet01-lv_log NAME FSTYPE LABEL UUID MOUNTPOINT vg_voinet01-lv_log (dm-5) The clon...

...ean, 47/120016 files, 80115/512000 blocks /dev/mapper/vg_voinet01-lv_home: clean, 7429/204800 files, 90039/819200 blocks /dev/mapper/vg_voinet01-LogVol04: clean, 770219/20480000 files, 34881086/8102000 blocks fsck.ext4: Bad magic number in super-block while trying to open /dev/mapper/vg_voinet01-lv_log /dev/mapper/vg_voinet01-lv_log The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternat...

Hi > On Thu, May 28, 2020 19:38, Robert Nichols wrote: > >> What output do you get from: >> >> file -s /dev/mapper/vg_voinet01-lv_log >> lsblk -f /dev/mapper/vg_voinet01-lv_log >> > > file -s /dev/mapper/vg_voinet01-lv_log > /dev/mapper/vg_voinet01-lv_log: symbolic link TO '../DM-5' > dm-f > > lsblk -f /dev/mapper/vg_voinet01-lv_log > NAME FSTYPE LABEL UUID MOUNTP...

...om inside that allocated to the virtual instance? Is it even considered advisable to use lvs with virtual guests? To give an example, if I were to configure an smtp server on bare metal I might use the following disk layout: vg_bare 500Gb / lv_root 8Gb /boot lv_boot 1Gb /tmp lv_tmp 8Gb /var/log lv_log 8Gb /var/spool/mail lv_mail 16Gb In a kvm setup, if I wish to do this, would I first create an lv just to host the virtual image and then assign lv s from the space allocated to that image file? vg_bare 500Gb / lv_root 8Gb /boot lv_boot 1Gb /tmp lv_tmp 8Gb /var/log lv_log 8G /var/lib/libvirt/i...

...el: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_inet02-lv_guest01: 129GB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End Size File system Flags 1 0.00B 129GB 129GB ext4 Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_inet02-lv_log: 1049MB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End Size File system Flags 1 0.00B 1049MB 1049MB ext4 Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_inet02-lv_tmp: 8389MB Sector size (logical/physical): 512B/512B Partition Tab...

...Id System However, in that event I cannot see the new disk: /dev/mapper/vg_inet01b-lv_root / ext4 defaults 1 1 UUID=218fd81f-6811-4965-b8d5-b0098a569598 /boot ext4 defaults 1 2 /dev/mapper/vg_inet01b-lv_tmp /tmp ext4 defaults 1 2 /dev/mapper/vg_inet01b-lv_log /var/log ext4 defaults 1 2 /dev/mapper/vg_inet01b-lv_spool /var/spool ext4 defaults 1 2 /dev/mapper/vg_inet01b-lv_swap swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid...

...faults 1 1 UUID=a9a7cc59-bd0c-4362-9ab6-f721e25df2f8 /boot ext4 defaults 1 2 /dev/mapper/vg_vhost04-lv_home /home ext4 defaults 1 2 /dev/mapper/vg_vhost04-lv_tmp /tmp ext4 defaults 1 2 /dev/mapper/vg_vhost04-lv_log /var/log ext4 defaults 1 2 /dev/mapper/vg_vhost04-lv_spool /var/spool ext4 defaults 1 2 /dev/mapper/vg_vhost04-lv_swap swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devp...

Yes, really. I've got hundreds of the damn things here at home, and I want to go through them and get rid of them all. But... to do that I want to read them. I have both a 5.25" and a 3.5" drive, both are plugged in, but in the BIOS, all I see is the 3.5". Fine, I figure I'll take care of those. Nope. I see /dev/fd0 once I've booted up, but neither konqueror nor