Linux Partitions
Hi everyone.
What happens if a linux partition is filled up? What kind of partitions can we resize after the installation without loss of data? How can we do it? Thanks in Advance. |
You may want to look at the Gparted Live-CD.
Although I have considered resizing Linux partitions I have not done so. I avoid resizing if I can. I have resized both FAT32 and NTFS partitions with commercial software. |
Depending on the distro your automatic partitioning may end up making the /home partition very large. This is where you will keep your data and the one most likely to fill up.
Assuming you are reasonably comfortable with manual partitioning I would suggest this: Have a look at what the installer is recommending. Tinker with the partition sizes so that the total comes to about 40MB. Leave the rest of the disc unpartitioned for now. After installation create another partition and mount it as /data or whatever you like. Give yourself full permissions to it. Now, use the /home/yourname directory to save stuff you want to backup regularly. Linux will store all the configuration info here. Use the /data directory to store things like MP3s, Photos etc which don't change and you either don't backup or only need to backup occasionally. As a guide, this is what has worked very well for me for a long time: Code:
Disk /dev/sda: 163.9 GB, 163928604672 bytes On this disc I made /var large instead of creating a /data partition. This disc is "dedicated" to Debian Linux Unstable. Code:
Disk /dev/sdb: 163.9 GB, 163928604672 bytes sdb1 is a 20GB Windows 2000 partition (rarely used). sdb3 is a "/data" partition sdb4 is another large partition where I keep Virtual Machine files sdb 5 is where a Debian Testing OS lives. I have this as an emergency use OS in case sda1 won't boot. Essentially the message is: "There are no RULES, only recommendations". The neat thing is that, as there is no drive letter nonsense, you can mount other partitions in a way that they appear as normal directories and don't get in your way while working. |
Hi,
Quote:
The '/var' directory is another potential problem area. If your system logs aren't rotated then you could fill space rapidly. If you use the system with one partition for '/' then you could eventually have problems if the system has a lot of activity. This would depend on the amount of space allocated to the '/'. That is why most servers are setup with separate partitions for many of the system directories. Sure, with the large disk storage available today the problems do not show up for the average user. But it can happen if you don't plan properly. Quote:
As for the actual partition resizing question, this would depend on how you originally setup the system. If you didn't allocate enough space for a particular system use directory then you have several alternatives. You could backup the system first then re-allocate the space to allow the expansion by using qparted (faq) or even Parted Magic to resize. If you setup the system with a scheme to allow expansion then the re-allocation would be to backup the system first then just delete the partition(s) using fdisk or cfdisk. You would then create the new partitions with the same fdisk or cfdisk. Of course you would have to make the file systems again with this method. The restore to the partitions would be straight forward with the new space. Another way would to just add another hard disk to the system, that is if you have the channels available. If you do it this way then you would scheme the partitions to your needs then either symlink or mount the partitions to the directory structure. You would restore the data to the new partition(s) directory tree. |
All times are GMT -5. The time now is 02:30 PM. |