Tag Info

New answers tagged

0

Various products offer storage tiering for various types of storage in the same platform, everything from FAST VP on EMC VNX SAN to tiering in systems like ZFS and Storage Spaces. If you're looking for something to bridge storage at multiple sites, or mix cloud and local/LAN storage, then it sounds like you might be served by a cloud storage gateway. ...


0

Yes, you need to use virsh blockresize to notify the guest of the change. The syntax should be something like: virsh blockresize INSTANCE_NAME --path /dev/vg/guest --size NEWSIZEG


0

I found the right parameter "reserved_for_root{ 0 }" 50000 10000 50000 ext4 \ $defaultignore{ } $lvmok{ } \ method{ lvm } format{ } \ lv_name{ root } \ use_filesystem{ } reserved_for_root{ 0 } filesystem{ ext4 } mountpoint{ / }


0

Eddy's fuser -vam /dev/hdb1 example was essentially correct, but it lacked some completeness. In my case, I ran into a similar problem while recovering files from someone off the last drive of a raid1 array where the partition holding the data was in LVM. In this case, I had started photorec to examine the drive, seen that there was a volume group, and ...


0

No way, probably your mount doesn't have the needed capability to use this tricky loopback mount. If you are mounting something so, the mount command first calls a losetup, and finally mounts this losetup device. It is normally /dev/loop0 (or bigger). With the losetup command you can mount a file, or a part of a file as if it were a normal partition. It is ...


1

If I read your question correctly you have a Linux hypervisor (a Xen dom0) with Linux LVM volumes which are used as virtual disks for your Xen guests (domU). And you want to access the data in that LVM directly from the hypervisor, bypassing the Xen guest. I don't use Xen anymore but I imagine the process is similar to what I do with KVM guests: Shut the ...


2

If you are unable to unmount or lvremove a logical volume, verify that there are no processes holding the LV Locate the major/minor numbers for the logical volume you’re trying to remove eg:vol0 # dmsetup info -c | grep vol0 Take note of the 5th column, which indicates if a volume is “open,” and the 2nd and 3rd columns, which are the major and minor IDs, ...



Top 50 recent answers are included