[00:07] nvm [12:48] PR snapcraft#2445 opened: Add core18 support to dotnet plugin [15:44] with ubuntu core, is there a way to change the partiton labels? im having a problem where I have one installation on a thumbdrive and another installation on the main mmc, and i think its getting confused... === phoenix_firebrd is now known as murthy [21:13] o/ === phoenix_firebrd is now known as murthy [21:14] Hey is anyone else having significant issues with 18.04 LTS snap installs? All of mine are taking up 100% of the space allocated for them, and I cant even list my containers because theres no space avialble. Can anyone give any insights into this? I cant even finish installs of my snaps until this is resolved. [21:21] This is what Im seeing on disk so far: http://paste.ubuntu.com/p/dQ3PZ8vwwc/ and http://paste.ubuntu.com/p/WkznvBsZRR/ The issue is, I cant even execute "docker container list" becuse it says not enough disk space. Total usage on the disk is maybe 10 Gb? On a disk thats well over 1TB in total size. Its a completely fresh Ubuntu 18.04LTS install, the only change is I also installed Ubuntu-Desktop. [21:23] fallenour, I'm no snap expert, but I believe that's totally normal [21:24] snaps are essentially disk images, they are no larger than the files they contain. They get mounted, read-only, and that's why it will always say 100% used. [21:24] I've encountered problems with monitoring on production systems where I would get disk usage alerts on snap installs :) [21:25] MattJ: Well the problem with that is, It installed by default on the system, but it wont even let me finish the snap install. I cant even configure the items snap installed. If I cant configure it, I cant use it, and effectively, its broken. If its unconfigurable, its worthless. [21:25] 100% on your / partition is obviously a problem [21:25] MattJ: Yea thats the same though Ihave. My question is, why doesnt it do to 75% instead, and scale due to isntall size, that way it always has room for changes? [21:26] Because snaps are read-only by design [21:26] fallenour: there are no changes within the snap container [21:26] fallenour: it's a version of software. If you installed a new version, then the new snap gets symlinked to "current" [21:26] MattJ: The other question is, how do I change it so I can configure the services. leftyfb Then how am I supposed to configure Nextcloud for instance to use a database? If I cant complete the isntall, it wont work. [21:26] They just contain the application, any data that the application generates doesn't go into the snap but into your usual system partition [21:27] MattJ: That I get, but even when Ive used snaps previously, tehy at least allowed me to configure the application first. I cant even do that here. [21:27] fallenour: you've mentioned docker, lx(c/d) and nextcloud. Lets start with testing a simple snap. Maybe try installing vlc [21:27] fallenour, because your main disk is full [21:27] fallenour: configuring the application is done outside of the snap container in your root filesystem [21:28] leftyfb: Ok, Im game. ill try it. [21:28] fallenour, can you do a `df -h /`? [21:28] leftyfb: MattJ Im getting connection refused for snap. My disk: http://paste.ubuntu.com/p/HdmdQXXrns/ [21:29] /dev/mapper/ubuntu--vg-ubuntu--lv 4062912 4046528 0 100% / [21:29] you have zero space left on your drie [21:29] drive* [21:29] you are out of disk space, nothing to do with snaps [21:29] fallenour, I asked for with -h [21:30] Sorry about that MattJ http://paste.ubuntu.com/p/NXNH85Qwgn/ leftyfb Thats the thing though, I know I shouldnt be. The server its on has at least 800 GB of dedicated space across multiple drives. Theres no way its full. [21:31] fallenour: you only have 4G in your root partition [21:31] fallenour, that's what you need to fix... the root partition is only 4GB [21:31] I've done installations before where the installer only creates a relatively small root partition (when using LVM) [21:31] You have to grow the partition manually [21:32] MattJ: leftyfb Ok, how do I do that? more specifically safely, the other question is how do I check to see how many disks my server can see. [21:32] MattJ: leftyfb All of the installs were done with LVM [21:32] https://wiki.ubuntu.com/Lvm is a good place to start I guess [21:34] MattJ: leftyfb when did Ubuntu start doing this? this wasnt an issue in 16.04, they would jsut use the full space availble. Im confused as to why this is a thing now [21:34] I don't know, I don't typically use LVM [21:35] MattJ: I normally do, but I only use it so that I can expand drive space later with LVM when I upgrade the harddrives in the future. But like I said before, I never had this issue. THe only thing Ive done differently this time is use 1 Raid 0 instead of 6. [21:37] fallenour: the default install of Ubuntu server should use up the remaining space by default. How did you do the install? [21:37] Btw, raid 0 is begging for data loss. Hope you don't care about the data on it [21:39] leftyfb: I used the built in process through cd install. generic "install with * using LVM" option. As for the data itself, I have replication between the servers on the databases, web app servers are using raid 1 with the data between HA Master-Master with 15 minute backups to cold storage. [21:40] leftyfb: MattJ odd idea, but how do I list all the physical disks that the system can see? I tried df -aTh, anything else I can try to see what it can see? It may not be seeing my drives and using only ram, if thats a thing. [21:40] lsblk [21:41] You might be better off in #ubuntu-server at this point since this isn't a snap issue [21:41] leftyfb: I think we just found the problem http://paste.ubuntu.com/p/nfFdh3SRDh/ [21:41] Yeah, like we said, you only created a 4g partition for root [21:44] leftyfb: So weird. I have no idea why it did this, or why it added all the space to sda3. Is there a fast fix for this? [22:11] fallenour, try #ubuntu-server