search for: pvscan

Hey Roger, I am seeing this weird behavior when using #linux-next + stable/for-jens-3.8 tree. Basically I can do ''pvscan'' on xvd* disk and quite often I get checksum errors: # pvscan /dev/xvdf PV /dev/xvdf2 VG VolGroup00 lvm2 [18.88 GiB / 0 free] PV /dev/dm-14 VG vg_x86_64-pvhvm lvm2 [4.00 GiB / 68.00 MiB free] PV /dev/dm-12 VG vg_i386-pvhvm lvm2 [4.00 GiB / 68.00 MiB free] PV...

I'm trying to create a 500GB lv volume on a 500GB physical volume, but can't: [root at francois-pc ~]# pvscan PV /dev/sdd VG freenas lvm2 [500.00 GB / 500.00 GB free] PV /dev/sdc VG thecus lvm2 [1010.00 GB / 910.00 GB free] PV /dev/mapper/ddf1_RAIDp2 VG VolGroup00 lvm2 [931.25 GB / 0 free] Total: 3 [2.38 TB] / in use: 3 [2.38 TB] / in no VG: 0 [0...

...I was moving data from an ATARAID (via Promise FastTrack100 Controller) into the LVM device below: 58,1: # cat /proc/lvm/VGs/foo3/LVs/bar name: /dev/foo3/bar size: 476315648 access: 3 status: 1 number: 0 open: 1 allocation: 0 device: 58:01 # /sbin/pvscan pvscan -- reading all physical volumes (this may take a while...) pvscan -- ACTIVE PV "/dev/hdm" of VG "foo1" [76.31 GB / 0 free] pvscan -- ACTIVE PV "/dev/hdn" of VG "foo3" [76.31 GB / 0 free] pvscan -- ACTIVE PV "/dev/hdk" of VG "foo3&q...

Hi, I am trying to recover data from my old system which had LVM. The disk had two partitions - /dev/sda1 (boot, Linux) and /dev/sda2 (Linux LVM). I had taken a backup of both partitions using dd. Now I am booting of CentOS live cd for system restore. I recreated partitions like previous system using fdisk and then used dd to dump all the data onto it. I would like to mount sda2 as LVM, but I

Dear friends: Using Centos 5. I have two physical drives. During install, I made sure to check hdb as well as hda. Both were listed as partitions (which is correct). But my fstab file does not show hdb. How do I make sure that hdb has been formatted and is part of my file system. If hdb is not formatted, how do I format it, please. Sorry for the question. I am a newbie. d[sher at localhost

I did a default install and after installing some other things I realized that a lot of space was allocated to /home as an lvm that is never going to be used. Is it possible to remove the lvm and grow the root (xfs) filesystem without starting over? -- Les Mikesell lesmikesell at gmail.com

...80 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 33 265041 83 Linux /dev/sda2 34 1338 10482412+ 8e Linux LVM /dev/sda3 1339 1860 4192965 82 Linux swap / Solaris [root at nd11176 ~]# pvscan PV /dev/sda2 VG VolGroup00 lvm2 [9.97 GB / 0 free] Total: 1 [9.97 GB] / in use: 1 [9.97 GB] / in no VG: 0 [0 ] [root at nd11176 ~]# vgscan Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 [root at nd11176 ~...

...g CentOS 5.0 ... I try to mount the old HD as /mnt/oldDisk but since it's a LVM, the "mount -t ext3" doesn't work. I'm new to LVM ... could someone help me on this. Also, there is a problem I found. Both HD have the same VG called /dev/VolGroup00 ... server:[root]/dev> pvscan PV /dev/hdb2 VG VolGroup00 lvm2 [76.22 GB / 0 free] PV /dev/hda2 VG VolGroup00 lvm2 [76.22 GB / 0 free] Total: 2 [152.44 GB] / in use: 2 [152.44 GB] / in no VG: 0 [0 ] where the /dev/hdb2 is the old one with bad sector ... and it's unmounted. The /dev/hda2 is the root fi...

...error /dev/dm-13: read failed after 0 of 4096 at 0: Input/output error /dev/dm-14: read failed after 0 of 4096 at 61203218432: Input/output error /dev/dm-14: read failed after 0 of 4096 at 0: Input/output error Volume group "VGe1" successfully created [root at frodo pilpel10]# pvscan /dev/dm-11: read failed after 0 of 4096 at 5242814464: Input/output error /dev/dm-11: read failed after 0 of 4096 at 0: Input/output error /dev/dm-12: read failed after 0 of 4096 at 54460416: Input/output error /dev/dm-12: read failed after 0 of 4096 at 0: Input/output error /dev/dm-...

...=1581810). If we don't start lvmetad earlier, the device nodes are not created. Therefore move the whole initialization step into appliance/init. Two further changes had to be made: Now we are using lvmetad all the time, using vgchange is incorrect. With lvmetad activated early we must use ‘pvscan --cache --activate ay’ to scan all disks for PVs and activate any VGs on them (although the documentation is complex, confusing and contradictory so I'm not completely sure about this). The ‘lvm_system_dir’ local variable in ‘daemon/lvm-filter.c’ previously contained the path of the directory...

I posted this to the Fedora-list, but thought I might get some additional information here as well. I have a HD that refuses to mount with a 'bad magic number in super-block'. I'm running FedoraCore 6 x86_64. [root at moe ~]# fdisk -l /dev/hdc Disk /dev/hdc: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes

...#39;/> <target dev='sda' bus='scsi'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> guests were Windows 8/2012, now after de-defining guests those disks are still unavailable to host's lvm, pvscan doesn't see. Is there a way to fix it? bw. P

...ostname has changed. I see that I couldn't previously find it with systemctl because it is a "static" service, neither enabled nor disabled. What is "static" really intended to mean here? The other static services seem to be boot-time related for the most part, eg anaconda, pvscan.... Man for hostnamectl (also new to me) indicates some potential uses for the hostnamed-maintained names, yet I see nothing obvious making use of that info. Can you give me an example? Thanks for the clues.....Nick Geovanis >Date: Sun, 27 Dec 2015 18:14:55 -0700 >From: Brandon Vincent &lt...

...right away if there are still buffers being freed from > underneath the journal, without oopsing my machine all the time. I tested the patch, but it didn't seem to help. Basically, I was running a kernel compile, and copying files into a different ext3 filesystem (both on LVs), and running pvscan (i.e. invalidate_buffers) repeatedly. At one point, I got several free buffers reported in cleanup_transaction. After that (this is the first time it happened) my kernel compile deadlocked and the kernel is stuck on: ext3_create journal_start start_this_handle log_wait_for_space log_do_checkpoin...

/dev/md3 is a raid5 array consisting of 4*500Gb disks pvs and pvscan both display good info: % pvscan | grep /dev/md3 PV /dev/md3 VG RaidDisk lvm2 [1.36 TB / 0 free] % pvs /dev/md3 PV VG Fmt Attr PSize PFree /dev/md3 RaidDisk lvm2 a- 1.36T 0 But pvdisplay... % pvdisplay /dev/md3 --- Physical volume --- PV Nam...

Hello, I have a physical volume with no volume group. # /sbin/pvscan -n WARNING: only considering physical volumes in no volume group PV /dev/sdg2 lvm2 [148.95 GB] Total: 1 [148.95 GB] / in use: 0 [0 ] / in no VG: 1 [148.95 GB] Can I just create a volume group -- for example: # vgcreate my_volume_group /dev/sdg2 and then activate it: # vgchange -a...

...ovirt_init)" if [ $? -eq 1 ]; then info "storage_init or ovirt_init arguments not found" - return 0 + else + info "Found storage_init: $storage_init" fi fi -info "Found storage_init: $storage_init" + +# Check for HostVG +lvm pvscan >/dev/null 2>&1 + +for hostvg in $(lvm pvs --noheadings -o vg_name,pv_name 2>/dev/null | awk '/^ HostVG/{print $2}'); do + storage_init="$hostvg,$storage_init" + info "Found HostVG on $hostvg" +done + # storage_init is passed in a specific format #...

...>, which it's supposed to according to Red Hat guides on LVM. On a CentOS 5.9 server, with an almost identical set up, the VG showed up under /dev/ correctly, so I'm wondering if the VG folder is stored elsewhere in CentOS 6? I have tried the obvious solutions, such as a reboot, vgscan, pvscan, and even partprobe. I have even tried running 'find' in search of the VG name, which returned no results. Any help is much appreciated. :) Regards, Kyle Thorne | VentraIP Australia *Level 3 Technical Administrator* -- *The contents of this email are strictly private and confidential u...

...ut without > activating them. > > I have introduced a new API (lvm_scan) which scans or rescans PVs, VGs > and LVs. It has an optional activate parameter allowing activation of > any new LVs that are found. > > With lvmetad this nicely maps to the single command: > > pvscan --cache [--activate ay] > --- lvm_scan seems basically vgscan + activate -- wouldn't be better to just add the "activate" optarg to vgscan? After all, if vgscan is deprecated, and users should migrate to lvm_scan, they can just add a new optarg. -- Pino Toscano

...ge.py index 5f7f0e3..047bcd1 100644 --- a/scripts/storage.py +++ b/scripts/storage.py @@ -90,13 +90,19 @@ class Storage: vg = subprocess.Popen(vg_cmd, shell=True, stdout=PIPE, stderr=STDOUT) vg_output = vg.stdout.read() for vg in vg_output: - pvs = system("pvscan -o pv_name,vg_uuid --noheadings | grep \"%s\" | egrep -v -q \"%s%s[0-9]+|%s \"") % (vg, dev, part_delim, dev) - if pvs > 0: + pvs_cmd = "pvs -o pv_name,vg_uuid --noheadings | grep \"%s\" | egrep -v -q \"%s%s[0-9]+|%s \"&quot...