similar to: Resizing lvm fails with fedora20

On 11.01.2015 02:57, Alex Regan wrote: > Hi, > I'm trying to resize a 15GB LVM root partition on a fedora20 server with > a fedora20 guest and I'm having a problem. Is this supported on fedora20? > > I recall having a similar problem (maybe even exact same problem) all > the way back in fedora16 or fedora17, but hoped/thought it would be > fixed by now? > > #

When the daemon starts up it creates a fresh (empty) LVM configuration and starts up lvmetad (which depends on the LVM configuration). However this appears to cause problems: Some types of PV seem to require lvmetad and don't work without it (https://bugzilla.redhat.com/show_bug.cgi?id=1581810). If we don't start lvmetad earlier, the device nodes are not created. Therefore move the

Hi, this series improves the way LVM is used in the appliance: in particular, now lvmetad can eventually run at all, and with the correct configuration. Also improve the listing strategies. Changes in v2: - dropped patch #5, will be sent separately - move lvmetad statup in own function (patch #2) Thanks, Pino Toscano (4): daemon: lvm-filter: set also global_filter daemon: lvm-filter:

On Wednesday, 18 July 2018 15:37:24 CEST Richard W.M. Jones wrote: > The old vgscan API literally ran vgscan. When we switched to using > lvmetad (in commit dd162d2cd56a2ecf4bcd40a7f463940eaac875b8) this > stopped working because lvmetad now ignores plain vgscan commands > without the --cache option. > > We documented that vgscan would rescan PVs, VGs and LVs, but without >

Hello, A windows XP machine 'X' (the only one left in the LAN) sees all fedora14/samba3 shares on f14 machine 'A' but cannot see fedora20/samba4 shares on machines 'B' or 'C'. 'X' can ping all of the others by name, and all of the others 'A', 'B' and 'C' CAN see ALL of the other shares INCLUDING on the XP machine 'X'.

Hi, this series improves the way LVM is used in the appliance: in particular, now lvmetad can eventually run at all, and with the correct configuration. Also improve the listing strategies. Thanks, Pino Toscano (5): daemon: lvm-filter: set also global_filter daemon: lvm-filter: start lvmetad better daemon: lvm: improve filter for LVs with activationskip flag set daemon: lvm: list

This patch reworks how we start up LVM and lvmetad. It fixes the problem we had converting a guest which had a peculiar LVM configuration: https://bugzilla.redhat.com/show_bug.cgi?id=1581810#c14 However please note I have NOT yet tested it fully. Rich.

Marc, et al, Thanks for your reply. Sorry, I didn't mean to be confusing. Summary of problem: 1) XP sees samba shares on fedora14/samba3 machine, but not on fedora20/samba4 machines. 2) all fedora machines see all shares including on XP machine. 3) clicking on f20 machine from XP tries to log in rather than showing the shares. Login is not successful. 4) all machines can ping each

Hi, We are trying to do P2V conversion with virt-p2v. we have conversion server (virt-p2v) and physical server (virt-p2v) server configured as per below documentation. http://libguestfs.org/virt-p2v.1.html#kernel-command-line-configuration After "Start Conversion" from GUI interface, we are conversion fails with "/run/lvm/lvmetad.socket: connect failed: No such file or

Thanks a lot for your awesome support Richard. "test connection" worked after we configured the necessary IP details but the "Conversion" ends with status as 1 with the below error message: (PFA of the complete logs stored on conversion server under "/tmp/virt-v2v-***" directory) /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to

On 06/03/15 20:30, Al Schapira wrote: > Marc, et al, > > Thanks for your reply. Sorry, I didn't mean to be confusing. > > Summary of problem: > 1) XP sees samba shares on fedora14/samba3 machine, but not on > fedora20/samba4 machines. > 2) all fedora machines see all shares including on XP machine. > 3) clicking on f20 machine from XP tries to log in rather

Hi, isn't it possible, that your new Samba4 server uses higher SMB protocol, than the old MS windows XP machine can understand/handle? Not sure about this, but might be worth checking? cheers :] -- *Karel Lang* *Unix/Linux Administration* lang at afd.cz | +420 731 13 40 40 AUFEER DESIGN, s.r.o. | www.aufeerdesign.cz On 03/06/2015 02:42 AM, Al Schapira wrote: > Hello, > > A

Hello Al, Am 06.03.2015 um 02:42 schrieb Al Schapira: > A windows XP machine 'X' (the only one left in the LAN) sees all > fedora14/samba3 shares on f14 machine 'A' but cannot see fedora20/samba4 > shares on machines 'B' or 'C'. > > 'X' can ping all of the others by name, and all of the others 'A', 'B' > and 'C'

On Fri, 2015-03-06 at 21:59 +0000, Rowland Penny wrote: > try adding 'map to guest = Bad User' to smb.conf > > Rowland > IT WORKED!!! THANK YOU. Now the XP machine can see both the f14 and f20 shares. (It was not even necessary to restart nmbd or smbd on the f20 machines.) Now, if I'm not asking for too much, can you please explain why this worked. :-) Many thanks

On Sat, Oct 31, 2015 at 06:11:05PM +0000, Richard W.M. Jones wrote: > > On Sat, Oct 31, 2015 at 10:14:32PM +0530, Tejas Gadaria wrote: > > Hi, > > > > We are trying to do P2V conversion with virt-p2v. > > > > we have conversion server (virt-p2v) and physical server (virt-p2v) server > > configured as per below documentation. > > > >

Hello, The last weekend, the VM with CentOS 7 (kernel-3.10.0-327.28.2.el7.x86_64) was running with 2.5GB of used memory, but without users connected, and heavy services running. Three minutes after reboot, the o.s. is running with 114MB used. ?Why the 62% of memory is used if the o.s. does not have an intensive load? top sorted by memory: top - 12:55:34 up 8 days, 21:41, 1 user, load

Hi Jason, On 14/08/15 16:45, Jason Warr wrote: > On Fri, 2015-08-14 at 16:31 +0100, Michael H wrote: >> Hi Thomas, >> >> >>> Could anybody point me in the right direction for setting the kernel >>> parameter, max_stack_depth, to 10240 for database tuning? >>> >>> I have currently set it by running 'ulimit -s 10240' but this does not

On Tue, Jul 26, 2016 at 05:41:28PM +0200, Pino Toscano wrote: > The appliance has no LVM system ID set, which means that lvm commands > will ignore VGs with a system ID set to anything. Since we want to work > with them, pass --foreign at least when listing them to see them. > > See also lvmsystemid(7). This is sort of a hack, if I'm understanding correctly. Can we not

Currently lvmetad is started in init, and thus using the system (= appliance) configuration of lvm. Later on, in the daemon, a local copy of the lvm configuration is setup, and set it for use using the LVM_SYSTEM_DIR environment variable: this means only the programmes executed by the daemon will use the local lvm configuration, and not lvmetad. Thus manually start lvmetad from the daemon, right

On 26.02.2014 17:59, Stephan Sachse wrote: >> # chown -R foo:foo /var/lib/libvirt/filesystems/mycontainer > > you must "shift" the uids for the container 0 -> 666, 1 -> 667, 2 -> > 668. there is a tool for this: uidmapshift I prepared two containers, the first I used chown, in the second uidmapshift, here is the results. ./uidmapshift -r