How to make system file partitions larger without reinstalling Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election Results Why I closed the “Why is Kali so hard” questionMove / to a new partitionHow to use DD to clone a partition off a disk image?Disk problems prevent me from booting, or set the disk to read-only. How do I fix the disk?Manually cloning a Live USB Arch distro to a VMware virtual diskHow to mount sdb directly or using LVM partitions on sda?Expanding root partition CentOS 6 With using fdiskXen domU not resizing diskHow to extend logical & extended partition with fdiskExtend partition using LVMOptimal LVM Setup to Keep Adding Space to Single Mountpoint

Estimate capacitor parameters

How are presidential pardons supposed to be used?

If I can make up priors, why can't I make up posteriors?

Writing Thesis: Copying from published papers

Passing functions in C++

Is there folklore associating late breastfeeding with low intelligence and/or gullibility?

Why does this iterative way of solving of equation work?

I'm thinking of a number

What's the point in a preamp?

Why is there no army of Iron-Mans in the MCU?

What was the last x86 CPU that did not have the x87 floating-point unit built in?

Estimated State payment too big --> money back; + 2018 Tax Reform

Is there a documented rationale why the House Ways and Means chairman can demand tax info?

Autumning in love

Limit for e and 1/e

Working around an AWS network ACL rule limit

Is above average number of years spent on PhD considered a red flag in future academia or industry positions?

Biased dice probability question

Can the prologue be the backstory of your main character?

Simulating Exploding Dice

What do you call a plan that's an alternative plan in case your initial plan fails?

Active filter with series inductor and resistor - do these exist?

Stop battery usage [Ubuntu 18]

What do you call the holes in a flute?



How to make system file partitions larger without reinstalling



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionMove / to a new partitionHow to use DD to clone a partition off a disk image?Disk problems prevent me from booting, or set the disk to read-only. How do I fix the disk?Manually cloning a Live USB Arch distro to a VMware virtual diskHow to mount sdb directly or using LVM partitions on sda?Expanding root partition CentOS 6 With using fdiskXen domU not resizing diskHow to extend logical & extended partition with fdiskExtend partition using LVMOptimal LVM Setup to Keep Adding Space to Single Mountpoint



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2















I'm using SteamOS. SteamOS I believe is Debian based.



I wiped the laptop and got it installed nicely. When I started moving my music over I got this message: Error while copying to "Music". - There is not enough space on the destination. Try to remove files to make space.



I assume, I need to make some sort of partition larger but I haven't been able to figure out how to do that?



As requested:



desktop@steamos:~$ sudo fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x116c49cc

Device Boot Start End Blocks Id System
/dev/sda1 1 1953525167 976762583+ ee GPT
Partition 1 does not start on physical sector boundary.
desktop@steamos:~$ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 9.3G 8.8G 27M 100% /
udev 10M 0 10M 0% /dev
tmpfs 739M 360K 739M 1% /run
/dev/disk/by-uuid/12742cc0-e489-472e-aa10-974d078d98e0 9.3G 8.8G 27M 100% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.4G 25M 3.4G 1% /run/shm
/dev/sda5 889G 119M 843G 1% /boot
/dev/sda1 487M 128K 486M 1% /boot/efi
/dev/sda3 9.3G 1.5G 7.4G 17% /boot/recovery
desktop@steamos:~$









share|improve this question



















  • 1





    It's definitely possible to resize partitions. In order to get relevant advice, edit your question and add the result of the command sudo fdisk -l and df -h (both entered at the terminal).

    – garethTheRed
    Oct 5 '14 at 6:31


















2















I'm using SteamOS. SteamOS I believe is Debian based.



I wiped the laptop and got it installed nicely. When I started moving my music over I got this message: Error while copying to "Music". - There is not enough space on the destination. Try to remove files to make space.



I assume, I need to make some sort of partition larger but I haven't been able to figure out how to do that?



As requested:



desktop@steamos:~$ sudo fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x116c49cc

Device Boot Start End Blocks Id System
/dev/sda1 1 1953525167 976762583+ ee GPT
Partition 1 does not start on physical sector boundary.
desktop@steamos:~$ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 9.3G 8.8G 27M 100% /
udev 10M 0 10M 0% /dev
tmpfs 739M 360K 739M 1% /run
/dev/disk/by-uuid/12742cc0-e489-472e-aa10-974d078d98e0 9.3G 8.8G 27M 100% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.4G 25M 3.4G 1% /run/shm
/dev/sda5 889G 119M 843G 1% /boot
/dev/sda1 487M 128K 486M 1% /boot/efi
/dev/sda3 9.3G 1.5G 7.4G 17% /boot/recovery
desktop@steamos:~$









share|improve this question



















  • 1





    It's definitely possible to resize partitions. In order to get relevant advice, edit your question and add the result of the command sudo fdisk -l and df -h (both entered at the terminal).

    – garethTheRed
    Oct 5 '14 at 6:31














2












2








2








I'm using SteamOS. SteamOS I believe is Debian based.



I wiped the laptop and got it installed nicely. When I started moving my music over I got this message: Error while copying to "Music". - There is not enough space on the destination. Try to remove files to make space.



I assume, I need to make some sort of partition larger but I haven't been able to figure out how to do that?



As requested:



desktop@steamos:~$ sudo fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x116c49cc

Device Boot Start End Blocks Id System
/dev/sda1 1 1953525167 976762583+ ee GPT
Partition 1 does not start on physical sector boundary.
desktop@steamos:~$ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 9.3G 8.8G 27M 100% /
udev 10M 0 10M 0% /dev
tmpfs 739M 360K 739M 1% /run
/dev/disk/by-uuid/12742cc0-e489-472e-aa10-974d078d98e0 9.3G 8.8G 27M 100% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.4G 25M 3.4G 1% /run/shm
/dev/sda5 889G 119M 843G 1% /boot
/dev/sda1 487M 128K 486M 1% /boot/efi
/dev/sda3 9.3G 1.5G 7.4G 17% /boot/recovery
desktop@steamos:~$









share|improve this question
















I'm using SteamOS. SteamOS I believe is Debian based.



I wiped the laptop and got it installed nicely. When I started moving my music over I got this message: Error while copying to "Music". - There is not enough space on the destination. Try to remove files to make space.



I assume, I need to make some sort of partition larger but I haven't been able to figure out how to do that?



As requested:



desktop@steamos:~$ sudo fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x116c49cc

Device Boot Start End Blocks Id System
/dev/sda1 1 1953525167 976762583+ ee GPT
Partition 1 does not start on physical sector boundary.
desktop@steamos:~$ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 9.3G 8.8G 27M 100% /
udev 10M 0 10M 0% /dev
tmpfs 739M 360K 739M 1% /run
/dev/disk/by-uuid/12742cc0-e489-472e-aa10-974d078d98e0 9.3G 8.8G 27M 100% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.4G 25M 3.4G 1% /run/shm
/dev/sda5 889G 119M 843G 1% /boot
/dev/sda1 487M 128K 486M 1% /boot/efi
/dev/sda3 9.3G 1.5G 7.4G 17% /boot/recovery
desktop@steamos:~$






debian files partition disk-usage






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 17 hours ago









Rui F Ribeiro

42.1k1483142




42.1k1483142










asked Oct 5 '14 at 5:57









BrawnyBrawny

1114




1114







  • 1





    It's definitely possible to resize partitions. In order to get relevant advice, edit your question and add the result of the command sudo fdisk -l and df -h (both entered at the terminal).

    – garethTheRed
    Oct 5 '14 at 6:31













  • 1





    It's definitely possible to resize partitions. In order to get relevant advice, edit your question and add the result of the command sudo fdisk -l and df -h (both entered at the terminal).

    – garethTheRed
    Oct 5 '14 at 6:31








1




1





It's definitely possible to resize partitions. In order to get relevant advice, edit your question and add the result of the command sudo fdisk -l and df -h (both entered at the terminal).

– garethTheRed
Oct 5 '14 at 6:31






It's definitely possible to resize partitions. In order to get relevant advice, edit your question and add the result of the command sudo fdisk -l and df -h (both entered at the terminal).

– garethTheRed
Oct 5 '14 at 6:31











2 Answers
2






active

oldest

votes


















1














The Standard of Practice is to enter into a Linux recovery environment. Any distribution Live-CD will enable you to access your computer in a manner appropriate to resize your hard drive partitions.



Resizing partitions is based on the ability to work on your drive without having the drive actually mounted.



$> fdisk -l


Invoking the command above will list your devices, i.e. (/dev/sda1/)



List your mounted drives (persistent drive mountings are stored in /etc/fstab:



$> mount


The umount command will unmount your drive, invoke as follows:



$> umount /dev/sda$


The administration utilities Parted or Gparted will resize your partitions. Be careful not to chop too much data off your partition! Understand how much you can really get away with based on how much is stored on your other partition. There are risks.



Use the search feature on your web browser to find specific instructions for how to resize a partition with GParted:



Please answer garethTheRed's comment to receive more specific answers.




garethTheRed: $> df -h




^ This will list how much space is used on your partitions.



GParted manual






share|improve this answer























  • I think we're on the right track. But when I went to unmount the partition that's using all the space I was faced with this : desktop@steamos:~$ sudo umount /dev/sda5 umount: /boot: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))

    – Brawny
    Oct 5 '14 at 15:07












  • You need to boot into a live Linux distribution, like the Ubuntu install CD. When you are not using the device, you will be able to unmount and resize the partition.

    – Tyler Maginnis
    Oct 5 '14 at 17:25











  • Plenty of filesystem/partition combinations allow a storage volume to grow live. This isn't “the standard of practice”, it's how you make do when you have an inferior operating system or setup (as is the case here, with PC-style partitions).

    – Gilles
    Oct 5 '14 at 20:09












  • I assumed we were talking about ext$ variants. This is the Standard of Practice for non-dynamic filesystems or whatever witchcraft you are talking about there, Gilles.

    – Tyler Maginnis
    Oct 5 '14 at 20:14


















1














You have a 1TiB hard drive with only 10GiB or so used. While it would be possible to expand this 10GiB partition up to a TiB or any size in between, an alternative solution is to add another separate partition for your home directories.



For example, add a new partition (/dev/sda6) and move the contents of your /home directory to it (this will need to be done as root). Then modify your /etc/fstab so that this new partition is automatically mounted at /home every boot.



The process will go something like this (all carried out as root):



# fdisk /dev/sda
n
6
[Enter]
+500G


Next add a filesystem (format it):



# mkfs.ext4 /dev/sda6


Mount it:



# mount /dev/sda6 /mnt


Move the files over:



# mv /home/* /mnt


and unmount:



# umount /mnt


Modify /etc/fstab by adding a line similar to:



UUID=12345678-1234-1234-1234-1234567890ab /home ext4 defaults 1 2


where the UUID is found by:



# blkid /dev/sda6


Running mount -a will mount all mounts defined in /etc/fstab therefore you can test it with:



# mount -a


at which point you should be able to see all the relevant directories within /home.






share|improve this answer























    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',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    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%2f159371%2fhow-to-make-system-file-partitions-larger-without-reinstalling%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    The Standard of Practice is to enter into a Linux recovery environment. Any distribution Live-CD will enable you to access your computer in a manner appropriate to resize your hard drive partitions.



    Resizing partitions is based on the ability to work on your drive without having the drive actually mounted.



    $> fdisk -l


    Invoking the command above will list your devices, i.e. (/dev/sda1/)



    List your mounted drives (persistent drive mountings are stored in /etc/fstab:



    $> mount


    The umount command will unmount your drive, invoke as follows:



    $> umount /dev/sda$


    The administration utilities Parted or Gparted will resize your partitions. Be careful not to chop too much data off your partition! Understand how much you can really get away with based on how much is stored on your other partition. There are risks.



    Use the search feature on your web browser to find specific instructions for how to resize a partition with GParted:



    Please answer garethTheRed's comment to receive more specific answers.




    garethTheRed: $> df -h




    ^ This will list how much space is used on your partitions.



    GParted manual






    share|improve this answer























    • I think we're on the right track. But when I went to unmount the partition that's using all the space I was faced with this : desktop@steamos:~$ sudo umount /dev/sda5 umount: /boot: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))

      – Brawny
      Oct 5 '14 at 15:07












    • You need to boot into a live Linux distribution, like the Ubuntu install CD. When you are not using the device, you will be able to unmount and resize the partition.

      – Tyler Maginnis
      Oct 5 '14 at 17:25











    • Plenty of filesystem/partition combinations allow a storage volume to grow live. This isn't “the standard of practice”, it's how you make do when you have an inferior operating system or setup (as is the case here, with PC-style partitions).

      – Gilles
      Oct 5 '14 at 20:09












    • I assumed we were talking about ext$ variants. This is the Standard of Practice for non-dynamic filesystems or whatever witchcraft you are talking about there, Gilles.

      – Tyler Maginnis
      Oct 5 '14 at 20:14















    1














    The Standard of Practice is to enter into a Linux recovery environment. Any distribution Live-CD will enable you to access your computer in a manner appropriate to resize your hard drive partitions.



    Resizing partitions is based on the ability to work on your drive without having the drive actually mounted.



    $> fdisk -l


    Invoking the command above will list your devices, i.e. (/dev/sda1/)



    List your mounted drives (persistent drive mountings are stored in /etc/fstab:



    $> mount


    The umount command will unmount your drive, invoke as follows:



    $> umount /dev/sda$


    The administration utilities Parted or Gparted will resize your partitions. Be careful not to chop too much data off your partition! Understand how much you can really get away with based on how much is stored on your other partition. There are risks.



    Use the search feature on your web browser to find specific instructions for how to resize a partition with GParted:



    Please answer garethTheRed's comment to receive more specific answers.




    garethTheRed: $> df -h




    ^ This will list how much space is used on your partitions.



    GParted manual






    share|improve this answer























    • I think we're on the right track. But when I went to unmount the partition that's using all the space I was faced with this : desktop@steamos:~$ sudo umount /dev/sda5 umount: /boot: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))

      – Brawny
      Oct 5 '14 at 15:07












    • You need to boot into a live Linux distribution, like the Ubuntu install CD. When you are not using the device, you will be able to unmount and resize the partition.

      – Tyler Maginnis
      Oct 5 '14 at 17:25











    • Plenty of filesystem/partition combinations allow a storage volume to grow live. This isn't “the standard of practice”, it's how you make do when you have an inferior operating system or setup (as is the case here, with PC-style partitions).

      – Gilles
      Oct 5 '14 at 20:09












    • I assumed we were talking about ext$ variants. This is the Standard of Practice for non-dynamic filesystems or whatever witchcraft you are talking about there, Gilles.

      – Tyler Maginnis
      Oct 5 '14 at 20:14













    1












    1








    1







    The Standard of Practice is to enter into a Linux recovery environment. Any distribution Live-CD will enable you to access your computer in a manner appropriate to resize your hard drive partitions.



    Resizing partitions is based on the ability to work on your drive without having the drive actually mounted.



    $> fdisk -l


    Invoking the command above will list your devices, i.e. (/dev/sda1/)



    List your mounted drives (persistent drive mountings are stored in /etc/fstab:



    $> mount


    The umount command will unmount your drive, invoke as follows:



    $> umount /dev/sda$


    The administration utilities Parted or Gparted will resize your partitions. Be careful not to chop too much data off your partition! Understand how much you can really get away with based on how much is stored on your other partition. There are risks.



    Use the search feature on your web browser to find specific instructions for how to resize a partition with GParted:



    Please answer garethTheRed's comment to receive more specific answers.




    garethTheRed: $> df -h




    ^ This will list how much space is used on your partitions.



    GParted manual






    share|improve this answer













    The Standard of Practice is to enter into a Linux recovery environment. Any distribution Live-CD will enable you to access your computer in a manner appropriate to resize your hard drive partitions.



    Resizing partitions is based on the ability to work on your drive without having the drive actually mounted.



    $> fdisk -l


    Invoking the command above will list your devices, i.e. (/dev/sda1/)



    List your mounted drives (persistent drive mountings are stored in /etc/fstab:



    $> mount


    The umount command will unmount your drive, invoke as follows:



    $> umount /dev/sda$


    The administration utilities Parted or Gparted will resize your partitions. Be careful not to chop too much data off your partition! Understand how much you can really get away with based on how much is stored on your other partition. There are risks.



    Use the search feature on your web browser to find specific instructions for how to resize a partition with GParted:



    Please answer garethTheRed's comment to receive more specific answers.




    garethTheRed: $> df -h




    ^ This will list how much space is used on your partitions.



    GParted manual







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Oct 5 '14 at 6:44









    Tyler MaginnisTyler Maginnis

    1,039711




    1,039711












    • I think we're on the right track. But when I went to unmount the partition that's using all the space I was faced with this : desktop@steamos:~$ sudo umount /dev/sda5 umount: /boot: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))

      – Brawny
      Oct 5 '14 at 15:07












    • You need to boot into a live Linux distribution, like the Ubuntu install CD. When you are not using the device, you will be able to unmount and resize the partition.

      – Tyler Maginnis
      Oct 5 '14 at 17:25











    • Plenty of filesystem/partition combinations allow a storage volume to grow live. This isn't “the standard of practice”, it's how you make do when you have an inferior operating system or setup (as is the case here, with PC-style partitions).

      – Gilles
      Oct 5 '14 at 20:09












    • I assumed we were talking about ext$ variants. This is the Standard of Practice for non-dynamic filesystems or whatever witchcraft you are talking about there, Gilles.

      – Tyler Maginnis
      Oct 5 '14 at 20:14

















    • I think we're on the right track. But when I went to unmount the partition that's using all the space I was faced with this : desktop@steamos:~$ sudo umount /dev/sda5 umount: /boot: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))

      – Brawny
      Oct 5 '14 at 15:07












    • You need to boot into a live Linux distribution, like the Ubuntu install CD. When you are not using the device, you will be able to unmount and resize the partition.

      – Tyler Maginnis
      Oct 5 '14 at 17:25











    • Plenty of filesystem/partition combinations allow a storage volume to grow live. This isn't “the standard of practice”, it's how you make do when you have an inferior operating system or setup (as is the case here, with PC-style partitions).

      – Gilles
      Oct 5 '14 at 20:09












    • I assumed we were talking about ext$ variants. This is the Standard of Practice for non-dynamic filesystems or whatever witchcraft you are talking about there, Gilles.

      – Tyler Maginnis
      Oct 5 '14 at 20:14
















    I think we're on the right track. But when I went to unmount the partition that's using all the space I was faced with this : desktop@steamos:~$ sudo umount /dev/sda5 umount: /boot: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))

    – Brawny
    Oct 5 '14 at 15:07






    I think we're on the right track. But when I went to unmount the partition that's using all the space I was faced with this : desktop@steamos:~$ sudo umount /dev/sda5 umount: /boot: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))

    – Brawny
    Oct 5 '14 at 15:07














    You need to boot into a live Linux distribution, like the Ubuntu install CD. When you are not using the device, you will be able to unmount and resize the partition.

    – Tyler Maginnis
    Oct 5 '14 at 17:25





    You need to boot into a live Linux distribution, like the Ubuntu install CD. When you are not using the device, you will be able to unmount and resize the partition.

    – Tyler Maginnis
    Oct 5 '14 at 17:25













    Plenty of filesystem/partition combinations allow a storage volume to grow live. This isn't “the standard of practice”, it's how you make do when you have an inferior operating system or setup (as is the case here, with PC-style partitions).

    – Gilles
    Oct 5 '14 at 20:09






    Plenty of filesystem/partition combinations allow a storage volume to grow live. This isn't “the standard of practice”, it's how you make do when you have an inferior operating system or setup (as is the case here, with PC-style partitions).

    – Gilles
    Oct 5 '14 at 20:09














    I assumed we were talking about ext$ variants. This is the Standard of Practice for non-dynamic filesystems or whatever witchcraft you are talking about there, Gilles.

    – Tyler Maginnis
    Oct 5 '14 at 20:14





    I assumed we were talking about ext$ variants. This is the Standard of Practice for non-dynamic filesystems or whatever witchcraft you are talking about there, Gilles.

    – Tyler Maginnis
    Oct 5 '14 at 20:14













    1














    You have a 1TiB hard drive with only 10GiB or so used. While it would be possible to expand this 10GiB partition up to a TiB or any size in between, an alternative solution is to add another separate partition for your home directories.



    For example, add a new partition (/dev/sda6) and move the contents of your /home directory to it (this will need to be done as root). Then modify your /etc/fstab so that this new partition is automatically mounted at /home every boot.



    The process will go something like this (all carried out as root):



    # fdisk /dev/sda
    n
    6
    [Enter]
    +500G


    Next add a filesystem (format it):



    # mkfs.ext4 /dev/sda6


    Mount it:



    # mount /dev/sda6 /mnt


    Move the files over:



    # mv /home/* /mnt


    and unmount:



    # umount /mnt


    Modify /etc/fstab by adding a line similar to:



    UUID=12345678-1234-1234-1234-1234567890ab /home ext4 defaults 1 2


    where the UUID is found by:



    # blkid /dev/sda6


    Running mount -a will mount all mounts defined in /etc/fstab therefore you can test it with:



    # mount -a


    at which point you should be able to see all the relevant directories within /home.






    share|improve this answer



























      1














      You have a 1TiB hard drive with only 10GiB or so used. While it would be possible to expand this 10GiB partition up to a TiB or any size in between, an alternative solution is to add another separate partition for your home directories.



      For example, add a new partition (/dev/sda6) and move the contents of your /home directory to it (this will need to be done as root). Then modify your /etc/fstab so that this new partition is automatically mounted at /home every boot.



      The process will go something like this (all carried out as root):



      # fdisk /dev/sda
      n
      6
      [Enter]
      +500G


      Next add a filesystem (format it):



      # mkfs.ext4 /dev/sda6


      Mount it:



      # mount /dev/sda6 /mnt


      Move the files over:



      # mv /home/* /mnt


      and unmount:



      # umount /mnt


      Modify /etc/fstab by adding a line similar to:



      UUID=12345678-1234-1234-1234-1234567890ab /home ext4 defaults 1 2


      where the UUID is found by:



      # blkid /dev/sda6


      Running mount -a will mount all mounts defined in /etc/fstab therefore you can test it with:



      # mount -a


      at which point you should be able to see all the relevant directories within /home.






      share|improve this answer

























        1












        1








        1







        You have a 1TiB hard drive with only 10GiB or so used. While it would be possible to expand this 10GiB partition up to a TiB or any size in between, an alternative solution is to add another separate partition for your home directories.



        For example, add a new partition (/dev/sda6) and move the contents of your /home directory to it (this will need to be done as root). Then modify your /etc/fstab so that this new partition is automatically mounted at /home every boot.



        The process will go something like this (all carried out as root):



        # fdisk /dev/sda
        n
        6
        [Enter]
        +500G


        Next add a filesystem (format it):



        # mkfs.ext4 /dev/sda6


        Mount it:



        # mount /dev/sda6 /mnt


        Move the files over:



        # mv /home/* /mnt


        and unmount:



        # umount /mnt


        Modify /etc/fstab by adding a line similar to:



        UUID=12345678-1234-1234-1234-1234567890ab /home ext4 defaults 1 2


        where the UUID is found by:



        # blkid /dev/sda6


        Running mount -a will mount all mounts defined in /etc/fstab therefore you can test it with:



        # mount -a


        at which point you should be able to see all the relevant directories within /home.






        share|improve this answer













        You have a 1TiB hard drive with only 10GiB or so used. While it would be possible to expand this 10GiB partition up to a TiB or any size in between, an alternative solution is to add another separate partition for your home directories.



        For example, add a new partition (/dev/sda6) and move the contents of your /home directory to it (this will need to be done as root). Then modify your /etc/fstab so that this new partition is automatically mounted at /home every boot.



        The process will go something like this (all carried out as root):



        # fdisk /dev/sda
        n
        6
        [Enter]
        +500G


        Next add a filesystem (format it):



        # mkfs.ext4 /dev/sda6


        Mount it:



        # mount /dev/sda6 /mnt


        Move the files over:



        # mv /home/* /mnt


        and unmount:



        # umount /mnt


        Modify /etc/fstab by adding a line similar to:



        UUID=12345678-1234-1234-1234-1234567890ab /home ext4 defaults 1 2


        where the UUID is found by:



        # blkid /dev/sda6


        Running mount -a will mount all mounts defined in /etc/fstab therefore you can test it with:



        # mount -a


        at which point you should be able to see all the relevant directories within /home.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Oct 5 '14 at 19:29









        garethTheRedgarethTheRed

        24.9k36482




        24.9k36482



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f159371%2fhow-to-make-system-file-partitions-larger-without-reinstalling%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            -debian, disk-usage, files, partition

            Popular posts from this blog

            Frič See also Navigation menuinternal link

            Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant

            fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown “element blank” The 2019 Stack Overflow Developer Survey Results Are In“tar: unrecognized option --warning” during 'apt-get install'How to fix Fontconfig errorHow do I figure out which font file is chosen for a system generic font alias?Why are some apt-get-installed fonts being ignored by fc-list, xfontsel, etc?Reload settings in /etc/fonts/conf.dTaking 30 seconds longer to boot after upgrade from jessie to stretchHow to match multiple font names with a single <match> element?Adding a custom font to fontconfigRemoving fonts from fontconfig <match> resultsBroken fonts after upgrading Firefox ESR to latest Firefox