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

    Out of Space - Ubuntu Linux 14.04

    Scheduled Pinned Locked Moved IT Discussion
    ubuntu 14.04linuxubuntu
    28 Posts 2 Posters 6.4k Views
    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.
    • handsofqwertyH
      handsofqwerty @scottalanmiller
      last edited by

      @scottalanmiller said:

      Once you have pvcreated, use vgextend to add the new block device to your existing VG.

      Look up the details with vgs

      This is what I got.

      root@plex-server:~# pvcreate /dev/sdb
        Physical volume "/dev/sdb" successfully created
        
      root@plex-server:~# vgs
        VG             #PV #LV #SN Attr   VSize  VFree
        plex-server-vg   1   2   0 wz--n- 19.76g 20.00m
      
      1 Reply Last reply Reply Quote 0
      • handsofqwertyH
        handsofqwerty
        last edited by

        So basically, now what?

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

          I think.....

          vgextend plex-server-vg /dev/sdb
          
          handsofqwertyH 2 Replies Last reply Reply Quote 0
          • handsofqwertyH
            handsofqwerty @scottalanmiller
            last edited by

            @scottalanmiller said:

            I think.....

            vgextend plex-server-vg /dev/sdb
            

            Do I need to reboot?

            1 Reply Last reply Reply Quote 0
            • handsofqwertyH
              handsofqwerty @scottalanmiller
              last edited by

              @scottalanmiller said:

              I think.....

              vgextend plex-server-vg /dev/sdb
              
              root@plex-server:~# vgextend plex-server-vg /dev/sdb
                Volume group "plex-server-vg" successfully extended
              
              1 Reply Last reply Reply Quote 0
              • handsofqwertyH
                handsofqwerty
                last edited by

                I was able to tab complete the plex-server-vg after typing vgextend, so I'm pretty sure that's right.

                1 Reply Last reply Reply Quote 0
                • handsofqwertyH
                  handsofqwerty
                  last edited by

                  This is what I have currently...

                  root@plex-server:~# vgs
                    VG             #PV #LV #SN Attr   VSize  VFree
                    plex-server-vg   2   2   0 wz--n- 44.75g 25.02g
                  root@plex-server:~# df -h
                  Filesystem                           Size  Used Avail Use% Mounted on
                  /dev/mapper/plex--server--vg-root     18G   17G  332K 100% /
                  none                                 4.0K     0  4.0K   0% /sys/fs/cgroup
                  udev                                 2.0G  4.0K  2.0G   1% /dev
                  tmpfs                                396M  712K  395M   1% /run
                  none                                 5.0M     0  5.0M   0% /run/lock
                  none                                 2.0G  4.0K  2.0G   1% /run/shm
                  none                                 100M     0  100M   0% /run/user
                  /dev/sda1                            236M   55M  169M  25% /boot
                  overflow                             1.0M   16K 1008K   2% /tmp
                  
                  1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller
                    last edited by

                    So you can see that you now have 25GB free.

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

                      Now you need to lvextend to 100%free

                      I'm on a plane. You will need to Google the syntax.

                      1 Reply Last reply Reply Quote 0
                      • handsofqwertyH
                        handsofqwerty
                        last edited by

                        Ok, I was able to figure it out. Here is the final results:

                        What I used to get info:

                        root@plex-server:/dev# lvs
                          LV     VG             Attr      LSize  Pool Origin Data%  Move Log Copy%  Convert
                          root   plex-server-vg -wi-ao--- 17.74g
                          swap_1 plex-server-vg -wi-ao---  2.00g
                        
                        root@plex-server:/dev# vgs
                          VG             #PV #LV #SN Attr   VSize  VFree
                          plex-server-vg   2   2   0 wz--n- 44.75g 25.02g
                        

                        The command I ran to extend the logical volume and the file system together and the results:

                        root@plex-server:/dev# lvextend -r plex-server-vg/root /dev/sdb
                          Extending logical volume root to 42.74 GiB
                          Logical volume root successfully resized
                        resize2fs 1.42.9 (4-Feb-2014)
                        Filesystem at /dev/mapper/plex--server--vg-root is mounted on /; on-line resizing required
                        old_desc_blocks = 2, new_desc_blocks = 3
                        The filesystem on /dev/mapper/plex--server--vg-root is now 11203584 blocks long.
                        
                        root@plex-server:/dev# df -h
                        Filesystem                           Size  Used Avail Use% Mounted on
                        /dev/mapper/plex--server--vg-root     42G   17G   24G  42% /
                        none                                 4.0K     0  4.0K   0% /sys/fs/cgroup
                        udev                                 2.0G  4.0K  2.0G   1% /dev
                        tmpfs                                396M  716K  395M   1% /run
                        none                                 5.0M     0  5.0M   0% /run/lock
                        none                                 2.0G  4.0K  2.0G   1% /run/shm
                        none                                 100M     0  100M   0% /run/user
                        /dev/sda1                            236M   55M  169M  25% /boot
                        overflow                             1.0M   16K 1008K   2% /tmp
                        

                        Thanks so much for your help and guidance @scottalanmiller ! I learned a lot today!

                        1 Reply Last reply Reply Quote 1
                        • handsofqwertyH
                          handsofqwerty
                          last edited by

                          Now, @scottalanmiller, one more question...the new virtual HDD is thin provisioned, so if I needed to expand it further, I can do it easily. Would I have to run lvextend again if I expand that drive in VMware? I assume so but are just curious. Thanks!

                          scottalanmillerS 1 Reply Last reply Reply Quote 1
                          • scottalanmillerS
                            scottalanmiller @handsofqwerty
                            last edited by

                            @handsofqwerty said:

                            Now, @scottalanmiller, one more question...the new virtual HDD is thin provisioned, so if I needed to expand it further, I can do it easily. Would I have to run lvextend again if I expand that drive in VMware? I assume so but are just curious. Thanks!

                            Yes, expanding or growing underlying block storage will not make volume managers or file systems on top grow too. The system has no way to know how you want the new storage to be used, so you would not want this. What if you wanted to add a new filesystem, for example, you would take the same action but would be pretty surprised if you found that that was automatically added to an already existing filesystem.

                            In a case like yours, it feels like the layers of expansion are obvious and you would "just want that." BUt if you were doing other tasks with the storage you would be like "oh, yeah, it can't make that judgement call for me."

                            handsofqwertyH 1 Reply Last reply Reply Quote 1
                            • handsofqwertyH
                              handsofqwerty @scottalanmiller
                              last edited by

                              @scottalanmiller said:

                              @handsofqwerty said:

                              Now, @scottalanmiller, one more question...the new virtual HDD is thin provisioned, so if I needed to expand it further, I can do it easily. Would I have to run lvextend again if I expand that drive in VMware? I assume so but are just curious. Thanks!

                              Yes, expanding or growing underlying block storage will not make volume managers or file systems on top grow too. The system has no way to know how you want the new storage to be used, so you would not want this. What if you wanted to add a new filesystem, for example, you would take the same action but would be pretty surprised if you found that that was automatically added to an already existing filesystem.

                              In a case like yours, it feels like the layers of expansion are obvious and you would "just want that." BUt if you were doing other tasks with the storage you would be like "oh, yeah, it can't make that judgement call for me."

                              I totally understand. It's easy to think about use cases only from one perspective, so I know what you mean. I figured that was the case but wanted to double check. So I should be able to, in theory, issue the same command, right?

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

                                Yup, you just do the same process again to expand in the future.

                                handsofqwertyH 1 Reply Last reply Reply Quote 0
                                • handsofqwertyH
                                  handsofqwerty @scottalanmiller
                                  last edited by

                                  @scottalanmiller said:

                                  Yup, you just do the same process again to expand in the future.

                                  Sweet, thanks!

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