search for: lvdisplay

Hi All I'm trying to setup my LVM thin pool to support discards so that the pool can reclaim space even if the underlying device doesn't support trim. It is my understanding that all thin pools should support trim even if the underlying device doesn't. (please correct me if I'm wrong here) I have one centos server that does support trim and everything is working correctly but any

...; wrote: > My guess? The passthrough is causing the error when the command passes > through to the actual device, which doesn't support Trim. > > I don't know how it actually works, but you can try to poke it with this > stick: copy a large file to this LV. Check the LV with lvdisplay. Delete > the file. Fstrim. Lvdisplay. Now compare the two lvdisplay results. > > It should show the PEs used are less after fstrim. > > > Chris Murphy > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos...

...eporting system. Wanted to a) get confirmation, if possible before bugging it and b) warn other souls that may be adventurous too! Summary: failings in LVM and kernel(?) seem to make a "freeze" possible. 1) Lvchange --permission=r seems to not take effect until re-boot even though lvdisplay says it has taken effect; 2) Prior to reboot, mount will mount a read-only LV and give no warning that it is read-only and will mount it r/w. The opposite also occurs: if the LV was ro and it is changed to r/w, mount still acts as if read-only is in effect. 3) If these steps are...

...I have used the following to mount an image and now I need to know the proper way to reverse the process. qemu-nbd -c /dev/nbd0 <qcow2 image using lvm> vgscan --cache (had to use --cache to get the qemu-nbd volume to be recognized, lvmetad is running) vgchange -ay lvdisplay mount <selected qemu-nbd related 'LV Path' found from lvdisplay above> <mount point> I have done the following: umount <mount point> lvchange -an <all qemu-nbd related 'LV Path's found from lvdisplay above> vgchange -an <qemu-n...

My guess? The passthrough is causing the error when the command passes through to the actual device, which doesn't support Trim. I don't know how it actually works, but you can try to poke it with this stick: copy a large file to this LV. Check the LV with lvdisplay. Delete the file. Fstrim. Lvdisplay. Now compare the two lvdisplay results. It should show the PEs used are less after fstrim. Chris Murphy

Greetings - I had a logical volume that was running out of space on a virtual machine. I successfully expanded the LV using lvextend, and lvdisplay shows that it has been expanded. Then I went to expand the filesystem to fill the new space (# resize2fs -p /dev/vde1) and I get the results that the filesystem is already xx blocks long, nothing to do. If I do a # df -h, I can see that the filesystem has not been extended. I could kick the...

Hi all, one of my lv has become completely unaccessible. Every read access results in a buffer io error: Buffer I/O error on dev dm-13, logical block 0, async page read this goes for every block in the lv. A ddrescue failed on every single block. $ lvdisplay --- Logical volume --- LV Path /dev/vg0/lv-vm-tviewer LV Name lv-vm-tviewer VG Name vg0 LV UUID XdgHFs-RHVZ-9BAH-1ZSK-yiBX-qqf0-273CtT LV Write Access read/write LV Creation host, time host1, 2016-02-06 14:58:19 +0100...

...n complaints I encounter when I discuss >> its merits are 'security' and 'transparency'. <snip> > HA! You only really need to learn *one* command: the man command. The > man provides 'enlightenment' for all other commands: > > man vgdisplay > man lvdisplay > man lvcreate > man lvextend > man lvresize > man lvreduce > man lvremove > man e2fsck > man resize2fs <snip> You missed one: man man. mark

Hi I had installed Xen-3.0.4 in Scientific linux 4 (kernel version 2.6.16.33) by following the instructions given in following link project-xen.web.cern.ch/project-xen/xen/howto_slcXen.html I ve created the guest Domain with fedora image of size 2.2GB , disk space as 10GB and the domain started successfully . when i logged into the xm console and checked the disk space its showing only 2.2GB ..

On 6/25/2015 8:50 AM, Robert Heller wrote: > man vgdisplay > man lvdisplay > man lvcreate > man lvextend > man lvresize > man lvreduce > man lvremove > man e2fsck > man resize2fs man xfs_growfs -- john r pierce, recycling bits in santa cruz

...index 7abfb3b..45b5d8c 100755 --- a/scripts/ovirt-config-password +++ b/scripts/ovirt-config-password @@ -8,6 +8,13 @@ trap '__st=$?; stop_log; exit $__st' 0 trap 'exit $?' 1 2 13 15 +warn() { printf '%s\n' "$*" >&2; } + +if [[ ! "Config" =~ $(lvdisplay -C | awk '{ print $1 }') ]]; then + warn "Local storage must be configured prior to setting the administrator password." + exit 99 +fi + # Usage: set_sasl_password USER # Prompt(twice) for a password for the specified USER. # If they match, set that user's system pass...

I converted a system disk from a virtualbox VM and added to the config on a qemu VM. All seems well until I try to mount it. The virtual machine shows data for the disk image using commands like: pvs lvs lvdisplay xena-1 but there is no /dev/xena-1/root to be mounted. I also cannot seem to figure out whether the lvm related modules are available for the virtual machine kernel. Has anyone else tried playing this game? -------------- next part -------------- A non-text attachment was scrubbed... Name: sig...

Hi Guys, I'm fairly new to Linux and I'm trying to un install a hard drive from my Centos 5.1 box running KDE. When I built the PC, I installed two 500 gig maxtors in the tower, then I installed Centos. Now I've decided that I want to remove the slave drive and use it as an external backup drive - I am mounting it into one of those external drive cases with a built in fan. When I

...ly created [root at kasse ~]# lvcreate -L 200M testgroup -n testLV Logical volume "testLV" created At this point, I have /dev/testgroup/testLV, which I can stick a fs on, mount, store files on, unmount, remount and recover the files from. Just as I'd expect. [root at kasse ~]# lvdisplay --- Logical volume --- LV Name /dev/testgroup/testLV VG Name testgroup LV UUID 3KjDiZ-gTAD-sC9E-sOSA-772o-41Yk-ZKK7cx LV Write Access read/write LV Status available # open 0 LV Size...

...ine). I have: intel e5-1620, 64 GB uDDR @1333Mgz, Dom0 on SSD OCZ Vertex4(@SATA3 port). Second SSD OCZ Agility 3 (@SATA3 port) with LVM 2 only for DomU. Kernel (3.4.7) + Xen unstable(rev 25705, Aug 02 14:44:53 2012 +0100) self compiled (according to Manual of Teo En Ming) DimU: Windows XP sp 2 # lvdisplay File descriptor 8 (pipe:[16062]) leaked on lvdisplay invocation. Parent PID 4821: bash --- Logical volume --- LV Name /dev/SSDagility/win_xp VG Name SSDagility LV UUID IsYry9-rirf-G7oW-WSVC-fUOI-0VV1-TnQcIA LV Write Access read/write L...

On Wed, June 24, 2015 16:11, Chuck Campbell wrote: > > Is there an easy to follow "howto" for normal LVM administration > tasks. I get tired of googling every-time I have to do something > I don't remember how to do regarding LVM, so I usually just > don't bother with it at all. > > I believe it has some benefit for my use cases, but I've been >

...using metadata type lvm2 Found volume group "VolGroup00" using metadata type lvm2 pvs --units=h PV VG Fmt Attr PSize PFree /dev/sda2 VolGroup00 lvm2 a- 9.88G 0 /dev/sda3 VolGroup00 lvm2 a- 90.00G 0 /dev/sdb1 VolGroup01 lvm2 a- 19.97G 19.97G lvdisplay --- Logical volume --- LV Name /dev/VolGroup00/LogVol00 VG Name VolGroup00 LV UUID cEWsVM-8M8w-0gWY-FFoh-bGLT-sf0M-sbosUD LV Write Access read/write LV Status available # open 1 LV Size 9...

...D Phenom system running 64-bit CentOS 5.4. Our original plan was to use LVM snapshots so that we wouldn't need a maintenance window. This worked fine in test, but we decided to bring down the Xen guests after all. After shutting down the systems we backed up the LVMs. To show the backing LV: lvdisplay /dev/rootvg/xm_c32_001 >From this, we grabbed the "Current LE" field and LV Size. We used LV Size to create a temporary mount point. We used the "Current LE" parameter to create an identically sized LV on the replacement server . On the failing server: dd if=/dev/rootvg/xm_...

Hi everyone. This isn't specifically a CentOS question, since it could apply for any distro but I hope someone can answer it anyway. I took the following steps but was puzzled by the outcome of the test at the end: 1. Create a RAID1 array called md3 with two 750GB drives 2. Create a RAID1 array called md9 with two 500GB drives 3. Initialise md3 then md9 as physical volumes (pvcreate) 4.

...the system settings... The server is a 32Bit CentOS 5.3 with the recent updates. Ths iscsi connection can be establised. fdisk and parted fail to create any information on the device or fail completely. using the lvm tools (pvcreate, vgcreate, lvcreate), I could finaly create a logical volume: lvdisplay /dev/VolGroup02/lvol0 --- Logical volume --- LV Name /dev/VolGroup02/lvol0 VG Name VolGroup02 LV UUID h7T6tD-JZw2-UEdb-q1ml-BDqp-9E0u-mAop6x LV Write Access read/write LV Status available # open 0 LV Si...