Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In my dedicated server I only need 2 partitions but I am not sure why so many were created.
I am using OVH dedicated server so maybe thats why.
This is my "df -h" output
All the partitions name /dev/root aren't real on disk partitions. They look like bind mounts related to the operation of the BIND DNS server (named), which typically runs in a chroot jail for security reasons (in this case the jail is in /var/named/chroot). If you look at these partitions, you can see they have exactly the same usage % as your root filesystem (in fact /dev/root is your root filesystem). These are just pseudo-partitions for the name server (been awhile since I had to run BIND, so I'm not sure why things are set up this way). They are not costing you any space you would otherwise have. Also, you do need /dev/shm as well, but it's an in memory filesystem like /dev itself -- again, it's not costing you anything.
All the partitions name /dev/root aren't real on disk partitions. They look like bind mounts related to the operation of the BIND DNS server (named), which typically runs in a chroot jail for security reasons (in this case the jail is in /var/named/chroot). If you look at these partitions, you can see they have exactly the same usage % as your root filesystem (in fact /dev/root is your root filesystem). These are just pseudo-partitions for the name server (been awhile since I had to run BIND, so I'm not sure why things are set up this way). They are not costing you any space you would otherwise have. Also, you do need /dev/shm as well, but it's an in memory filesystem like /dev itself -- again, it's not costing you anything.
Thank you for explaining everything and thank you.
But my last thing is
how come there is only 1.7TB on /dev/mapper/vg-lv1 when I was doing partitioning on OVH it had 1.9TB.
The filesystem uses a bit of extra space to hold things like inodes and other metadata. There's also some space reserved for root (5% by default IIRC). This probably accounts for the slight discrepancy.
The filesystem uses a bit of extra space to hold things like inodes and other metadata. There's also some space reserved for root (5% by default IIRC). This probably accounts for the slight discrepancy.
The filesystem uses a bit of extra space to hold things like inodes and other metadata. There's also some space reserved for root (5% by default IIRC). This probably accounts for the slight discrepancy.
I see.
Thank you very much BTMiller for the answers. Very helpful.
I was just a bit worried why I only had 1.7TB allocated on a section.
But now I know.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.