similar to: filesystem type unknow for lvm root fs

hi all! some windows vm's filesystem type is unknown(/dev/sda: unknown), and 'mount' command leads to: 'libguestfs: error: mount: /dev/sda on / (options: ''): mount: you must specify the filesystem type ' if i don't know the type, whether i could mount the device? Thanks! ??

Hello everybody, I been trying to debug a problem for a month now and can use some insights and advice. This is the setup, I got two linux ha storage node providing iscsi disk, the disks is mounted on two linux kvm host and one backup server. The iscsi disk has lvm on it, the logical volume groups are visible on all servers. On the backup server I have the following running: # guestmount

Hi, trying to convert a VMware Linux installation to a XEN VM, I copied the harddisk image. I was expecting problems, but this is what I got: ------------snip # xm create -c vm2 Using config file "/etc/xen/vm/vm2". /dev/hda: No medium found mount: unknown filesystem type ''LVM2_member'' Traceback (most recent call last): File

I have an 8-core SuperMicro Xeon server with CentOS 6.3. The OS is installed on a 120 GB SSD connected by SATA, the machine also contains an Areca SAS controller with 24 drives connected. The motherboard is a SuperMicro X9DA7. When I installed the OS, I used the default options, which creates an LVM volume group to contain / and /home, and keeps /boot and /boot/efi outside the volume group.

Hi This topic is perhaps not for this list, but it I'm running on a CentOS 4.4 and it seems that a lot of people here uses 3Ware and RAID volumes. I did a RAID migration on a 3Ware 9590SE-12, so that an exported disk grew from 700GB to 1400GB. The exported disk is managed by LVM. The problem now is that I don't really know what to do now to let LVM and my locigal volume to make use of

RHEL 4's mkinitrd will fail to recognise that root is on LVM when running on a recent kernel/udev due to changes in naming. This patch detects LVM root for RHEL 4, and uses a dirty hack to frig mkinitrd if required. Fixes RHBZ#580461 --- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 21 +++++++++++++++++++-- 1 files changed, 19 insertions(+), 2 deletions(-) diff --git

Anybody know a way to enlarge a filesystem ext3 without having to unmounted it, when they are still space left in the volume group (when using LVM) ? I will be running large production linux system running Oracle. I can't stop the database everytime I have to enlarge a filesystem. We can do it with all others filesystems (JFS, REISERSFS and XFS) when they are created in a volume group. Why

On Fri, May 31, 2013 at 12:48 AM, Richard W.M. Jones <rjones@redhat.com>wrote: > On Thu, May 30, 2013 at 10:21:42PM +0800, Qiu Yu wrote: > > Hi, > > > > Following code snippet, running as non-root user, will throw up a > > 'Permission denied' RuntimeError. > > > > Could someone kindly guide me the correct way to handle LVM disk as > >

On 06/23/2015 10:54 AM, Marko Vojinovic wrote: > (1) I have no valid usecase for it. I don't remember when was the last > time I needed to resize partitions (probably back when I was trying to > install Windows 95). Disk space is very cheap, and if I really need to > have *that* much data on a single partition, another drive and a few > intelligently placed symlinks are usually

Can someone please explain what the purpose of stride is on ext3? I have been "googling" this for hours and wasn't really able to understand the underlying concepts. How does it fit with LVM, PV create's metablock size, and hardware RAID controller? TIA -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 2015-06-24 13:03, Nicolas C. wrote: > Hello, > > Do you have recommendations on EXT4 and LVM options for a 3TB > file-system for mdbox? > > We currently use the mbox format on a XFS with poor performances since > the update in v2.1 (Debian). What qualifies as "poor performance"? How many users? > > We will switch to EXT4 to have the possibility of

So here goes... First some back story -Centos 5 with latest updates as of yesterday. kernel is 2.6.18-238.19.1.el5 -setup is raid 1 for /boot and lvm over raid6 for everything else - The / partition (lvm "RootVol") had run out of room... (100% full, things where falling appart...) I resized the root volume (from 20GiB to 50GiB). This was done from a fedora 15 livecd,

We had puppet turned off on a host for a few days, and when we turned it back on, we started seeing: (/Stage[setup]/Foo::Filesystems/Filesystem[/dev/data_vg/foo_lv]/ensure) change from absent to present failed: Execution of ''mkfs.ext4 /dev/data_vg/foo_lv'' returned 1: mke2fs 1.41.12 (17-May-2010)#012/dev/data_vg/foo_lv is mounted; will not make a filesystem here! It''s

I have been running some virtual machines on CentOS7 KVM with the VMs living in a folder under a /home directory. Everything I've read says to create LVM volume groups and base storage pools on that. So i followed the instructions at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Deployment_and_Administration_Guide/sect-LVM_based_storage_pools.html

Hi All, I've been chasing down an issue in recent weeks (my own lab, so no prod here) and I'm reaching out in case someone might have some guidance to share. I'm running fairly large VMs (RHOSP underclouds - 8vcpu, 32gb ram, about 200gb single disk as a growable qcow2) on some RHEL7.6 hypervisors (kernel 3.10.0-927.2x.y, libvirt 4.5.0, qemu-kvm-1.5.3) on top of SSD/NVMe drives

On 16/01/2020 10:50, Ralf Prengel wrote: > Hallo, > has anyone a working Centos 8.1 PXE Installation? > > This is my problem > http://realtechtalk.com/Centos_PXEBoot_NetInstall_Failure__Pane_is_dead-2012-articles > All CentOS 8.1.1911 validations were done over PXE (machines reinstalled - physical or VMs). So that article mentions something specific about non distro kernel to

On Tue, 23 Jun 2015 18:42:13 -0700 Gordon Messmer <gordon.messmer at gmail.com> wrote: > > I wondered the same thing, especially in the context of someone who > prefers virtual machines. LV-backed VMs have *dramatically* better > disk performance than file-backed VMs. Ok, you made me curious. Just how dramatic can it be? From where I'm sitting, a read/write to a disk

Hello, I am running libvirt 0.8.3 with a couple VMs using a LVM VG that I had previously setup on my host. I did not use the storage pool functionality of libvirt to create the VG in the first place ('pool-list' is empty). Now I want to be able to take snapshots of the VMs. Having read this previous post [1] on the mailing list, I gather that libvirt does indeed support taking snapshots

On 6/24/2015 1:06 PM, m.roth at 5-cent.us wrote: > Gordon Messmer wrote: >> On 06/23/2015 08:10 PM, Marko Vojinovic wrote: >>> Ok, you made me curious. Just how dramatic can it be? From where I'm >>> sitting, a read/write to a disk takes the amount of time it takes, the >>> hardware has a certain physical speed, regardless of the presence of >>>

Hi, I''m running Xen on a Debian Xeon E3110 using the Debian 2.6.26-2-xen kernel. As filesystem for my lvm domU partitions I choosed xfs. I get the following error in kern.log of domU when booting a domU: blkfront: sda2: write barrier op failed blkfront: sda2: barriers disabled end_request: I/O error, dev sda2, sector 0 end_request: I/O error, dev sda2, sector 0 Filesystem