Ubuntu Server 18.04LTS Can't extend default LV?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
3
down vote

favorite












My recent install of Ubuntu Server 18.04 appears to have created an LV mounted on / that is only 4GB. However the volume group is 160GB as expected.



But I get an insufficient disk space message when I try and expand the LV even though the group appears to have free space:



tom@git:~$ sudo pvs
PV VG Fmt Attr PSize PFree
/dev/vda3 ubuntu-vg lvm2 a-- <159.00g <155.00g
tom@git:~$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
ubuntu-vg 1 1 0 wz--n- <159.00g <155.00g
tom@git:~$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
ubuntu-lv ubuntu-vg -wi-ao---- 4.00g

tom@git:~$ sudo lvextend -L +10G /dev/ubuntu-vg/ubuntu-lv
/etc/lvm/archive/.lvm_git_20778_346817101: write error failed: No space left on device


Any ideas here? My root filesystem is at 100%, the new installer obviously doesn't make use of all disk space for the primary LV by default.










share|improve this question

























    up vote
    3
    down vote

    favorite












    My recent install of Ubuntu Server 18.04 appears to have created an LV mounted on / that is only 4GB. However the volume group is 160GB as expected.



    But I get an insufficient disk space message when I try and expand the LV even though the group appears to have free space:



    tom@git:~$ sudo pvs
    PV VG Fmt Attr PSize PFree
    /dev/vda3 ubuntu-vg lvm2 a-- <159.00g <155.00g
    tom@git:~$ sudo vgs
    VG #PV #LV #SN Attr VSize VFree
    ubuntu-vg 1 1 0 wz--n- <159.00g <155.00g
    tom@git:~$ sudo lvs
    LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
    ubuntu-lv ubuntu-vg -wi-ao---- 4.00g

    tom@git:~$ sudo lvextend -L +10G /dev/ubuntu-vg/ubuntu-lv
    /etc/lvm/archive/.lvm_git_20778_346817101: write error failed: No space left on device


    Any ideas here? My root filesystem is at 100%, the new installer obviously doesn't make use of all disk space for the primary LV by default.










    share|improve this question























      up vote
      3
      down vote

      favorite









      up vote
      3
      down vote

      favorite











      My recent install of Ubuntu Server 18.04 appears to have created an LV mounted on / that is only 4GB. However the volume group is 160GB as expected.



      But I get an insufficient disk space message when I try and expand the LV even though the group appears to have free space:



      tom@git:~$ sudo pvs
      PV VG Fmt Attr PSize PFree
      /dev/vda3 ubuntu-vg lvm2 a-- <159.00g <155.00g
      tom@git:~$ sudo vgs
      VG #PV #LV #SN Attr VSize VFree
      ubuntu-vg 1 1 0 wz--n- <159.00g <155.00g
      tom@git:~$ sudo lvs
      LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
      ubuntu-lv ubuntu-vg -wi-ao---- 4.00g

      tom@git:~$ sudo lvextend -L +10G /dev/ubuntu-vg/ubuntu-lv
      /etc/lvm/archive/.lvm_git_20778_346817101: write error failed: No space left on device


      Any ideas here? My root filesystem is at 100%, the new installer obviously doesn't make use of all disk space for the primary LV by default.










      share|improve this question













      My recent install of Ubuntu Server 18.04 appears to have created an LV mounted on / that is only 4GB. However the volume group is 160GB as expected.



      But I get an insufficient disk space message when I try and expand the LV even though the group appears to have free space:



      tom@git:~$ sudo pvs
      PV VG Fmt Attr PSize PFree
      /dev/vda3 ubuntu-vg lvm2 a-- <159.00g <155.00g
      tom@git:~$ sudo vgs
      VG #PV #LV #SN Attr VSize VFree
      ubuntu-vg 1 1 0 wz--n- <159.00g <155.00g
      tom@git:~$ sudo lvs
      LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
      ubuntu-lv ubuntu-vg -wi-ao---- 4.00g

      tom@git:~$ sudo lvextend -L +10G /dev/ubuntu-vg/ubuntu-lv
      /etc/lvm/archive/.lvm_git_20778_346817101: write error failed: No space left on device


      Any ideas here? My root filesystem is at 100%, the new installer obviously doesn't make use of all disk space for the primary LV by default.







      ubuntu lvm extend






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 4 hours ago









      tomstephens89

      626822




      626822




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          3
          down vote



          accepted










          LVM creates metadata backup on every change. It can't back up the data to /etc/lvm/archive as / is full. Either delete some files and try again, or use the -A n switch to not back up this change.



          Reference man lvm (emphasis mine):




          -A|--autobackup n



          Whether or not to metadata should be backed up automatically after a change. You are strongly advised not to disable this! See vgcfgbackup(8).







          share|improve this answer




















          • Thanks, using -A n has let me extend the LV. Life saver thanks!
            – tomstephens89
            4 hours ago










          • Forgot to add that I needed to use the --resizefs option as well.
            – tomstephens89
            4 hours ago










          • Using -r, --resizefs depends on your use-case, of course.
            – Lenniey
            4 hours ago











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "2"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f937324%2fubuntu-server-18-04lts-cant-extend-default-lv%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          3
          down vote



          accepted










          LVM creates metadata backup on every change. It can't back up the data to /etc/lvm/archive as / is full. Either delete some files and try again, or use the -A n switch to not back up this change.



          Reference man lvm (emphasis mine):




          -A|--autobackup n



          Whether or not to metadata should be backed up automatically after a change. You are strongly advised not to disable this! See vgcfgbackup(8).







          share|improve this answer




















          • Thanks, using -A n has let me extend the LV. Life saver thanks!
            – tomstephens89
            4 hours ago










          • Forgot to add that I needed to use the --resizefs option as well.
            – tomstephens89
            4 hours ago










          • Using -r, --resizefs depends on your use-case, of course.
            – Lenniey
            4 hours ago















          up vote
          3
          down vote



          accepted










          LVM creates metadata backup on every change. It can't back up the data to /etc/lvm/archive as / is full. Either delete some files and try again, or use the -A n switch to not back up this change.



          Reference man lvm (emphasis mine):




          -A|--autobackup n



          Whether or not to metadata should be backed up automatically after a change. You are strongly advised not to disable this! See vgcfgbackup(8).







          share|improve this answer




















          • Thanks, using -A n has let me extend the LV. Life saver thanks!
            – tomstephens89
            4 hours ago










          • Forgot to add that I needed to use the --resizefs option as well.
            – tomstephens89
            4 hours ago










          • Using -r, --resizefs depends on your use-case, of course.
            – Lenniey
            4 hours ago













          up vote
          3
          down vote



          accepted







          up vote
          3
          down vote



          accepted






          LVM creates metadata backup on every change. It can't back up the data to /etc/lvm/archive as / is full. Either delete some files and try again, or use the -A n switch to not back up this change.



          Reference man lvm (emphasis mine):




          -A|--autobackup n



          Whether or not to metadata should be backed up automatically after a change. You are strongly advised not to disable this! See vgcfgbackup(8).







          share|improve this answer












          LVM creates metadata backup on every change. It can't back up the data to /etc/lvm/archive as / is full. Either delete some files and try again, or use the -A n switch to not back up this change.



          Reference man lvm (emphasis mine):




          -A|--autobackup n



          Whether or not to metadata should be backed up automatically after a change. You are strongly advised not to disable this! See vgcfgbackup(8).








          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 4 hours ago









          Lenniey

          2,0122719




          2,0122719











          • Thanks, using -A n has let me extend the LV. Life saver thanks!
            – tomstephens89
            4 hours ago










          • Forgot to add that I needed to use the --resizefs option as well.
            – tomstephens89
            4 hours ago










          • Using -r, --resizefs depends on your use-case, of course.
            – Lenniey
            4 hours ago

















          • Thanks, using -A n has let me extend the LV. Life saver thanks!
            – tomstephens89
            4 hours ago










          • Forgot to add that I needed to use the --resizefs option as well.
            – tomstephens89
            4 hours ago










          • Using -r, --resizefs depends on your use-case, of course.
            – Lenniey
            4 hours ago
















          Thanks, using -A n has let me extend the LV. Life saver thanks!
          – tomstephens89
          4 hours ago




          Thanks, using -A n has let me extend the LV. Life saver thanks!
          – tomstephens89
          4 hours ago












          Forgot to add that I needed to use the --resizefs option as well.
          – tomstephens89
          4 hours ago




          Forgot to add that I needed to use the --resizefs option as well.
          – tomstephens89
          4 hours ago












          Using -r, --resizefs depends on your use-case, of course.
          – Lenniey
          4 hours ago





          Using -r, --resizefs depends on your use-case, of course.
          – Lenniey
          4 hours ago


















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f937324%2fubuntu-server-18-04lts-cant-extend-default-lv%23new-answer', 'question_page');

          );

          Post as a guest













































































          Comments

          Popular posts from this blog

          What does second last employer means? [closed]

          List of Gilmore Girls characters

          Confectionery