[slacker]

/etc/fstab cannot work unless you shrink /home first, create a new md3 array, and then finally mount /usr/local on it.

Symlink is much quicker in this case.

[RichardWnl]

Ok so what would you suggest in this situation:











As you can see the root folder is get filled up, especially /usr/local/ where cPanel seems to store some of it's data.

Some data needs to be moved before / is full... so symlink or /etc/fstab ?

[slacker]

I assume the 1.7TB partition is mounted on /home.
That's OVH default.

Simply change /etc/fstab in order to mount /dev/sda2 where you know the data will be stored. There's no need to symlink really...

[RichardWnl]

Yes that would be possible by creating a symlink also known as a symbolic link. Which is kinda what a shortcut does in Windows.

[freshwire]

I assume that /dev/root is just some alias to /dev/sda1. I should have known this sorry.

Yes it is a fresh install of OS via manager.

You can also take a look at this guide to resize partitions (while keeping data intact):
http://www.howtoforge.com/linux_resi..._partitions_p2

[JamesP]

Thanks for the help guys, if I reinstall it through manager I need to do a fresh OS install right? Here's the results also:

______________
root [~]# fdisk -l

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 2550 20478976+ 83 Linux
/dev/sda2 2550 243136 1932506112 83 Linux
/dev/sda3 243136 243201 523264 82 Linux swap / Solaris

_____________________________

Thanks again.

[freshwire]

after I've installed my server

If you've only just installed it then you can initiate the re-install procedure in the OVH manager. It should allow you to specify the partitions desired.

However. It is strange that the devices would be named /dev/root and /dev/sda2. This suggests to me they are not the same physical disk. If so, where is sda1?

Try to run:

$ fdisk -l

and paste here the results.

[JamesP]

Hi,

Thanks for the response, sorry if I'm explaining it badly:

Here's the results:
___________
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 20317448 20317448 0 100% /
/dev/root 20317448 20317448 0 100% /
none 12364428 108 12364320 1% /dev
/dev/sda2 1917281412 5823040 1814833068 1% /home
tmpfs 12364428 0 12364428 0% /dev/shm
/dev/loop0 495844 19802 450442 5% /tmp
/dev/loop0 495844 19802 450442 5% /var/tmp
/dev/root 20317448 20317448 0 100% /var/named/chroot/var/run/dbus

[Razakel]

I'm not sure I understand how you've got your partitions set up now. Do you mean you've got a 20GB partition mounted at /root and 1.7TB free space (because that doesn't make any sense), or 20GB mounted at / and 1.7TB free space?

/dev/sda2 will probably be mounted somewhere else, probably /home. In that case, you can just delete the 1.7TB partition and extend the 20GB one.

Can you run df and post the results?

[JamesP]

Hi,

I see that after I've installed my server my /root has only 20GB of space, and the other 1.7TB has been allocated to /dev/sda2.

My question is, to access this 1.7TB onto root, is there a way I can bridge them somehow so that space is accessible to root? Or do I have to do a fresh OS install and partition the whole disk space to /root and not make a /dev/sda2?

Thanks,

James.

Any help appreciated!