To Symlink or not to Symlink?

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











up vote
1
down vote

favorite












Prefacing this by saying I'm pretty new to Linux/Computers.



I'm working on doing a yum update on an outdated RHEL (7.2) system. I'm currently not able to install anything new or change the disk partition scheme, but it was sent to my team with only 2g of /var space, while /home has 50g, and root, for some reason, has 641g. I know it's not ideal, but nothing I can do about it at this time.



While trying to yum update, the var cache fills up. I've tried yum clear all , but there just isn't enough space in the folder to complete this update. I know you can use LVS to resize partitions, but was told this can be potentially dangerous and not always consistent. I also know I can do a symlink from the /var to /home or maybe root, but this feels like a band-aid and I want to make this solution long-term.



Is there a better way to handle this situation? And what is the best way to implement this symlink safely, if I have to use it?







share|improve this question

























    up vote
    1
    down vote

    favorite












    Prefacing this by saying I'm pretty new to Linux/Computers.



    I'm working on doing a yum update on an outdated RHEL (7.2) system. I'm currently not able to install anything new or change the disk partition scheme, but it was sent to my team with only 2g of /var space, while /home has 50g, and root, for some reason, has 641g. I know it's not ideal, but nothing I can do about it at this time.



    While trying to yum update, the var cache fills up. I've tried yum clear all , but there just isn't enough space in the folder to complete this update. I know you can use LVS to resize partitions, but was told this can be potentially dangerous and not always consistent. I also know I can do a symlink from the /var to /home or maybe root, but this feels like a band-aid and I want to make this solution long-term.



    Is there a better way to handle this situation? And what is the best way to implement this symlink safely, if I have to use it?







    share|improve this question























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      Prefacing this by saying I'm pretty new to Linux/Computers.



      I'm working on doing a yum update on an outdated RHEL (7.2) system. I'm currently not able to install anything new or change the disk partition scheme, but it was sent to my team with only 2g of /var space, while /home has 50g, and root, for some reason, has 641g. I know it's not ideal, but nothing I can do about it at this time.



      While trying to yum update, the var cache fills up. I've tried yum clear all , but there just isn't enough space in the folder to complete this update. I know you can use LVS to resize partitions, but was told this can be potentially dangerous and not always consistent. I also know I can do a symlink from the /var to /home or maybe root, but this feels like a band-aid and I want to make this solution long-term.



      Is there a better way to handle this situation? And what is the best way to implement this symlink safely, if I have to use it?







      share|improve this question













      Prefacing this by saying I'm pretty new to Linux/Computers.



      I'm working on doing a yum update on an outdated RHEL (7.2) system. I'm currently not able to install anything new or change the disk partition scheme, but it was sent to my team with only 2g of /var space, while /home has 50g, and root, for some reason, has 641g. I know it's not ideal, but nothing I can do about it at this time.



      While trying to yum update, the var cache fills up. I've tried yum clear all , but there just isn't enough space in the folder to complete this update. I know you can use LVS to resize partitions, but was told this can be potentially dangerous and not always consistent. I also know I can do a symlink from the /var to /home or maybe root, but this feels like a band-aid and I want to make this solution long-term.



      Is there a better way to handle this situation? And what is the best way to implement this symlink safely, if I have to use it?









      share|improve this question












      share|improve this question




      share|improve this question








      edited Jun 27 at 14:56
























      asked Jun 27 at 14:09









      Stimulai

      113




      113




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          A symlink does the job for a workaround but for a permanent solution you should resize your partitions. Resizing / via LVM should be done via the RHEL rescue console and before you resize anything make sure you have a current backup.



          I resized many LVM volumes over time and never had a problem but you never know.



          If you have far enough space on / you can also move the whole /var to the root logical volume, delete the /var logical volume and add the 2GB to the root logical volume.



          To link the yum cache as a temporary workaround do something like:



          mkdir /tmpvar
          mv /var/cache/yum /tmpvar
          ln -s /tmpvar/yum /var/cache/yum


          To get a more detailed view on the resize process please add the output of lvs, pvs and fdisk -l






          share|improve this answer























          • I ended up going with the symlink and it worked just fine. I know it's a temporary solution, but I don't currently have the authorization to resize the partitions. Thank you for the help!!
            – Stimulai
            Jun 27 at 16:32










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          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: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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%2funix.stackexchange.com%2fquestions%2f452230%2fto-symlink-or-not-to-symlink%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
          1
          down vote













          A symlink does the job for a workaround but for a permanent solution you should resize your partitions. Resizing / via LVM should be done via the RHEL rescue console and before you resize anything make sure you have a current backup.



          I resized many LVM volumes over time and never had a problem but you never know.



          If you have far enough space on / you can also move the whole /var to the root logical volume, delete the /var logical volume and add the 2GB to the root logical volume.



          To link the yum cache as a temporary workaround do something like:



          mkdir /tmpvar
          mv /var/cache/yum /tmpvar
          ln -s /tmpvar/yum /var/cache/yum


          To get a more detailed view on the resize process please add the output of lvs, pvs and fdisk -l






          share|improve this answer























          • I ended up going with the symlink and it worked just fine. I know it's a temporary solution, but I don't currently have the authorization to resize the partitions. Thank you for the help!!
            – Stimulai
            Jun 27 at 16:32














          up vote
          1
          down vote













          A symlink does the job for a workaround but for a permanent solution you should resize your partitions. Resizing / via LVM should be done via the RHEL rescue console and before you resize anything make sure you have a current backup.



          I resized many LVM volumes over time and never had a problem but you never know.



          If you have far enough space on / you can also move the whole /var to the root logical volume, delete the /var logical volume and add the 2GB to the root logical volume.



          To link the yum cache as a temporary workaround do something like:



          mkdir /tmpvar
          mv /var/cache/yum /tmpvar
          ln -s /tmpvar/yum /var/cache/yum


          To get a more detailed view on the resize process please add the output of lvs, pvs and fdisk -l






          share|improve this answer























          • I ended up going with the symlink and it worked just fine. I know it's a temporary solution, but I don't currently have the authorization to resize the partitions. Thank you for the help!!
            – Stimulai
            Jun 27 at 16:32












          up vote
          1
          down vote










          up vote
          1
          down vote









          A symlink does the job for a workaround but for a permanent solution you should resize your partitions. Resizing / via LVM should be done via the RHEL rescue console and before you resize anything make sure you have a current backup.



          I resized many LVM volumes over time and never had a problem but you never know.



          If you have far enough space on / you can also move the whole /var to the root logical volume, delete the /var logical volume and add the 2GB to the root logical volume.



          To link the yum cache as a temporary workaround do something like:



          mkdir /tmpvar
          mv /var/cache/yum /tmpvar
          ln -s /tmpvar/yum /var/cache/yum


          To get a more detailed view on the resize process please add the output of lvs, pvs and fdisk -l






          share|improve this answer















          A symlink does the job for a workaround but for a permanent solution you should resize your partitions. Resizing / via LVM should be done via the RHEL rescue console and before you resize anything make sure you have a current backup.



          I resized many LVM volumes over time and never had a problem but you never know.



          If you have far enough space on / you can also move the whole /var to the root logical volume, delete the /var logical volume and add the 2GB to the root logical volume.



          To link the yum cache as a temporary workaround do something like:



          mkdir /tmpvar
          mv /var/cache/yum /tmpvar
          ln -s /tmpvar/yum /var/cache/yum


          To get a more detailed view on the resize process please add the output of lvs, pvs and fdisk -l







          share|improve this answer















          share|improve this answer



          share|improve this answer








          edited Jun 27 at 15:37


























          answered Jun 27 at 14:32









          T-One

          336




          336











          • I ended up going with the symlink and it worked just fine. I know it's a temporary solution, but I don't currently have the authorization to resize the partitions. Thank you for the help!!
            – Stimulai
            Jun 27 at 16:32
















          • I ended up going with the symlink and it worked just fine. I know it's a temporary solution, but I don't currently have the authorization to resize the partitions. Thank you for the help!!
            – Stimulai
            Jun 27 at 16:32















          I ended up going with the symlink and it worked just fine. I know it's a temporary solution, but I don't currently have the authorization to resize the partitions. Thank you for the help!!
          – Stimulai
          Jun 27 at 16:32




          I ended up going with the symlink and it worked just fine. I know it's a temporary solution, but I don't currently have the authorization to resize the partitions. Thank you for the help!!
          – Stimulai
          Jun 27 at 16:32












           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f452230%2fto-symlink-or-not-to-symlink%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?