ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Solved Ubuntu 18.04 Space Issue

    IT Discussion
    6
    46
    2.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      Curtis @scottalanmiller
      last edited by Curtis

      @scottalanmiller said in Ubuntu 18.04 Space Issue:

      @Curtis Run this...

      lvresize -l +100%FREE /dev/ubuntu-vg/ubuntu-lv

      user@server:~$ sudo lvresize -l +100%FREE /dev/ubuntu-vg/ubuntu-lv
      sudo: unable to resolve host server: Resource temporarily unavailable

      /etc/lvm/archive/.lvm_server_2656_1676534144: write error failed: No space left on device

      😕

      1 Reply Last reply Reply Quote 0
      • C
        Curtis
        last edited by

        Tried as root, and got this:

        /etc/lvm/archive/.lvm_server_2674_604287443: write error failed: No space left on device

        1 Reply Last reply Reply Quote 0
        • M
          marcinozga
          last edited by

          The error tells you exactly why it's failing. Clean up some space, /var/log/ would be a good place to start. Then re-run that command.

          C 1 Reply Last reply Reply Quote 0
          • C
            Curtis @marcinozga
            last edited by

            @marcinozga said in Ubuntu 18.04 Space Issue:

            The error tells you exactly why it's failing. Clean up some space, /var/log/ would be a good place to start. Then re-run that command.

            Would this work?

            find /var/log -type f -delete
            1 Reply Last reply Reply Quote 0
            • DustinB3403D
              DustinB3403
              last edited by

              @Curtis said in Ubuntu 18.04 Space Issue:

              @marcinozga said in Ubuntu 18.04 Space Issue:

              The error tells you exactly why it's failing. Clean up some space, /var/log/ would be a good place to start. Then re-run that command.

              Would this work?

              find /var/log -type f -delete

              I wouldn't do that. Just cd into the directory and remove anything that is zipped.

              1 Reply Last reply Reply Quote 0
              • C
                Curtis
                last edited by

                root@server:/var# lvresize -l +100%FREE /dev/ubuntu-vg/ubuntu-lv
                Size of logical volume ubuntu-vg/ubuntu-lv changed from 4.00 GiB (1024 extents) to <99.00 GiB (25343 extents).
                Logical volume ubuntu-vg/ubuntu-lv successfully resized.

                🙂 Now what?

                DustinB3403D wirestyle22W C 3 Replies Last reply Reply Quote 0
                • DustinB3403D
                  DustinB3403 @Curtis
                  last edited by

                  @Curtis said in Ubuntu 18.04 Space Issue:

                  Now what?

                  df -h

                  C 1 Reply Last reply Reply Quote 0
                  • wirestyle22W
                    wirestyle22 @Curtis
                    last edited by wirestyle22

                    @Curtis As you are doing this man each command so you understand what is occuring

                    Example: man df

                    1 Reply Last reply Reply Quote 0
                    • M
                      marcinozga
                      last edited by

                      Show the output of

                      mount
                      1 Reply Last reply Reply Quote 0
                      • C
                        Curtis @DustinB3403
                        last edited by

                        @DustinB3403

                        I still need to resize the file system I believe?

                        2b89db0a-d884-490e-9c32-edae48a9a4a0-image.png

                        1 Reply Last reply Reply Quote 0
                        • C
                          Curtis @Curtis
                          last edited by Curtis

                          Seems like I should run:

                          resize2fs /dev/ubuntu-vg/ubuntu-lv

                          ?

                          M scottalanmillerS 2 Replies Last reply Reply Quote 0
                          • M
                            marcinozga @Curtis
                            last edited by

                            @Curtis it depends on filesystem. That's why I asked for output of mount command.

                            C 1 Reply Last reply Reply Quote 0
                            • C
                              Curtis @marcinozga
                              last edited by

                              @marcinozga said in Ubuntu 18.04 Space Issue:

                              @Curtis it depends on filesystem. That's why I asked for output of mount command.

                              sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1988900k,nr_inodes=497225,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=403972k,mode=755)
/dev/mapper/ubuntu--vg-ubuntu--lv on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=45,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16445)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/var/lib/snapd/snaps/wekan_518.snap on /snap/wekan/518 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/wekan_523.snap on /snap/wekan/523 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_4917.snap on /snap/core/4917 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_6673.snap on /snap/core/6673 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/wekan_517.snap on /snap/wekan/517 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_6818.snap on /snap/core/6818 type squashfs (ro,nodev,relatime,x-gdu.hide)
/dev/sda2 on /boot type ext4 (rw,relatime,data=ordered)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
tmpfs on /run/snapd/ns type tmpfs (rw,nosuid,noexec,relatime,size=403972k,mode=755)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=403968k,mode=700,uid=1000,gid=1000)
root@wekan:/var# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1988900k,nr_inodes=497225,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=403972k,mode=755)
/dev/mapper/ubuntu--vg-ubuntu--lv on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=45,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16445)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/var/lib/snapd/snaps/wekan_518.snap on /snap/wekan/518 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/wekan_523.snap on /snap/wekan/523 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_4917.snap on /snap/core/4917 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_6673.snap on /snap/core/6673 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/wekan_517.snap on /snap/wekan/517 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_6818.snap on /snap/core/6818 type squashfs (ro,nodev,relatime,x-gdu.hide)
/dev/sda2 on /boot type ext4 (rw,relatime,data=ordered)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
tmpfs on /run/snapd/ns type tmpfs (rw,nosuid,noexec,relatime,size=403972k,mode=755)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=403968k,mode=700,uid=1000,gid=1000)
                              1 Reply Last reply Reply Quote 0
                              • scottalanmillerS
                                scottalanmiller @Curtis
                                last edited by

                                @Curtis said in Ubuntu 18.04 Space Issue:

                                Seems like I should run:

                                resize2fs /dev/ubuntu-vg/ubuntu-lv

                                Yup, run that.

                                1 Reply Last reply Reply Quote 0
                                • M
                                  marcinozga
                                  last edited by

                                  It's ext4, so the above command you provided is correct.

                                  1 Reply Last reply Reply Quote 0
                                  • C
                                    Curtis
                                    last edited by

                                    Ahhhhhhhhhh, thats better 🙂

                                    Filesystem                         Size  Used Avail Use% Mounted on
udev                               1.9G     0  1.9G   0% /dev
tmpfs                              395M  1.1M  394M   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   98G  3.9G   90G   5% /
tmpfs                              2.0G     0  2.0G   0% /dev/shm
tmpfs                              5.0M     0  5.0M   0% /run/lock
tmpfs                              2.0G     0  2.0G   0% /sys/fs/cgroup
/dev/loop2                         152M  152M     0 100% /snap/wekan/518
/dev/loop3                         152M  152M     0 100% /snap/wekan/523
/dev/loop5                          87M   87M     0 100% /snap/core/4917
/dev/loop1                          90M   90M     0 100% /snap/core/6673
/dev/loop0                         152M  152M     0 100% /snap/wekan/517
/dev/loop4                          90M   90M     0 100% /snap/core/6818
/dev/sda2                          976M  155M  755M  18% /boot
tmpfs                              395M     0  395M   0% /run/user/1000
                                    scottalanmillerS 1 Reply Last reply Reply Quote 2
                                    • scottalanmillerS
                                      scottalanmiller @Curtis
                                      last edited by

                                      @Curtis ta da!

                                      1 Reply Last reply Reply Quote 0
                                      • scottalanmillerS
                                        scottalanmiller
                                        last edited by

                                        So what you have is a file system (EXT4) inside of a volume on top of a partition, on top of the physical device. The issue was that the volume was the wrong size, so the filesystem was using all available space "to it", which was 4GB. The partition had a 4GB volume inside of the 100GB partition. So we had to expand that, then expand the FS to fill the new space.

                                        C 1 Reply Last reply Reply Quote 1
                                        • C
                                          Curtis @scottalanmiller
                                          last edited by Curtis

                                          @scottalanmiller said in Ubuntu 18.04 Space Issue:

                                          So what you have is a file system (EXT4) inside of a volume on top of a partition, on top of the physical device. The issue was that the volume was the wrong size, so the filesystem was using all available space "to it", which was 4GB. The partition had a 4GB volume inside of the 100GB partition. So we had to expand that, then expand the FS to fill the new space.

                                          That's pretty confusing. I'll have to read up on it more. Anyone have some recommended readings that might help me wrap my head around this?

                                          JaredBuschJ scottalanmillerS 2 Replies Last reply Reply Quote 0
                                          • JaredBuschJ
                                            JaredBusch @Curtis
                                            last edited by

                                            @Curtis said in Ubuntu 18.04 Space Issue:

                                            @scottalanmiller said in Ubuntu 18.04 Space Issue:

                                            So what you have is a file system (EXT4) inside of a volume on top of a partition, on top of the physical device. The issue was that the volume was the wrong size, so the filesystem was using all available space "to it", which was 4GB. The partition had a 4GB volume inside of the 100GB partition. So we had to expand that, then expand the FS to fill the new space.

                                            That's pretty confusing. I'll have to read up on it more. Anyone have some recommended readings that might help me wrap my head around this?

                                            Not really. It is a simple logical design. Pretty much all systems work this way.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 2 / 3
                                            • First post
                                              Last post