[00:44] <WobblyBob> Anyone an idea how to increase storage size on virt-manager using the gui not cli
[00:54] <mybalzitch> did you check the storage manager bit? been a bit since I was in virt-manager
[00:55] <WobblyBob> yeah doesnt give any options to update it
[00:58] <mybalzitch> ahh, it might not be possible. not seeing anything on google about it, it suggests qemu-img or virt-resize
[01:04] <rfm> WobblyBob, do you mean RAM or disk storage?
[01:04] <WobblyBob> disk storage
[01:06] <rfm> WobblyBob, then depends on what kind of disk image you're using.  qcow2 is most common I think where it's "qemu-img resize diskfilename.qcow2 +8G" to grow by 8G
[01:07] <rfm> WobblyBob, if it's an ubuntu cloud image, cloud-init will repartition and grow the fs at the next boot
[18:48] <ahasenack> hi, does anybody have a clue why apt remove ./*.deb ended up installing the deb? I know that removing a local deb filename makes no sense, but I wanted to see what would happen. And this was unexpected to me: https://pastebin.ubuntu.com/p/dkVq7mqvrd/
[18:52] <sdeziel> ahasenack: surprising but maybe "remove" behaves like other subcommands (for example, dist-upgrade accepts packages names to install: https://mobile.twitter.com/JulianKlode/status/1322294691430281218)
[18:53] <ahasenack> I know with install recent versions of apt-get can be used like dpkg, with dep resolving
[18:53] <ahasenack> but remove?
[18:53] <ahasenack> I expected it to either check for a package that was named like the filename,
[18:53] <ahasenack> or perhaps extract the package name from the given deb, and consider that for removal
[18:53] <ahasenack> but I never expected it to install the package
[18:55] <sdeziel> yeah, it guessed the right package name but then did the wrong action, feels like a bug
[18:56] <ahasenack> I'll also try again with apt-get, not just apt
[18:57] <ahasenack> but it was just a surprise that I thought about asking around first :)
[18:57] <mgedmin> do file a bug
[18:58] <mgedmin> did you know that apt-get install can remove packages?  if you say apt-get install pkg-
[18:58] <mgedmin> also I think apt-get remove can install packages if you suffix the name with a +
[18:58] <ahasenack> it sure can, if dependencies warrant it
[18:58] <ahasenack> ah, you mean the -? No, I had no idea
[18:58] <ahasenack> good to know
[18:58] <ahasenack> as I was investigating sudo rules
[18:58] <mgedmin> it's convenient when you want to both install and remove stuff with one command
[18:59] <mgedmin> but it looks like ./foo.deb gets an implicit + or something, which is really unintuitive, and I think unintended
[18:59] <mgedmin> so, I would file a bug (if I weren't a lazy person)
[18:59] <ahasenack> I will, thanks
[18:59] <ahasenack> also want to try other releases, this was bionic
[19:02] <mgedmin> lol https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929242
[19:02] <mgedmin> I didn't see any bugs in debian about apt remove ./file.deb installing the package
[19:03] <mgedmin> don't see any in https://bugs.launchpad.net/ubuntu/+source/apt either
[19:04] <mgedmin> congratulations on your discovery :)
[21:07] <FuZi0N> Anyone else notice high RAM utilization being reported in 'top' and any other monitoring tool but then when you try to find the service which is utilizing most of the memory you can't find it? Perhaps there's a memory leak in Linux Kernel 5.4.0-52-generic on Ubuntu 18.04.1?
[21:08] <sarnold> FuZi0N: try smem, it's fantastic at helping you assign blame
[21:08] <FuZi0N> ok
[21:08] <FuZi0N> trying it now!
[21:13] <sdeziel> FuZi0N: there's also systemd-cgtop that can be useful for some cases
[21:23] <FuZi0N> sarnold how can I make sense of this smem output? https://pastebin.com/TcTZT8Sf
[21:27] <sarnold> FuZi0N: pid 3940 is using 4118948 kb of memory 'uniquely', pid 23897 is using 3636008 kb of memory uniquely, etc
[21:27] <sarnold> that's the amount of memory you could free up if you stopped those processes
[21:36] <FuZi0N> https://pastebin.com/kmQ95n0D
[21:36] <FuZi0N> Based on this it looks like a kernel memory leak issue?
[21:39] <sarnold> FuZi0N: you'd need to keep track of those numbers ovre a long time to tell if there's a kernel memory leak or not
[21:48] <FuZi0N> sdeziel sarnold: what does it mean if smem is saying that I'm only using ~11GB of userspace memory but systemd-cgtop is saying that my plex docker container is using ~17GB memory?
[21:50] <sarnold> FuZi0N: systemd-cgtop is likely multiply-accounting memory that is shared among multiple processes
[21:52] <FuZi0N> So it wouldn't help me identify any issues in my case?
[21:56] <sarnold> probably not, the output you've shown me looks a lot like a single-purpose system; it's not like you can just stop plex and go on your way -- that's the whole reason for the machine to exist as far as I can tell
[21:57] <sarnold> you might be able to pick and choose which plugins you want to load, maybe the memory use of one of them doesn't justify what it does for you