How to partition a pair of 3Tb disks under proxmox?

Question

Debian

You need to split the disks of Hetzner's EX4S to make a software RAID1.
There are a number of options for sitting:

• www.wepoca.net/node/41
  
• ras.pl.ua/proxmox_raid1_howto/
  
• www.doless.ru/ustanavlivaem-proxmox-na-server-v-dc...
  
• admway.bystrov.net/2012/04/hetznerde.html
  

Questions:
* why not put on /boot ext4;
* what determines the size of the /boot partition;
* why Debian doesn't recommend a separate /boot partition if RAID1 is planned;
* what are the minuses / pluses of the options of the above authors;
* why mirror swap;
* why partition the folders of the root partition;
Well, your partitioning option will be great, especially if you
comment, of course, on the logic of your partitioning.

Answer 1

About "swap does not need mirroring" - believe me, nonsense. If a disk with a swap partition on which there was data at that moment crashes on the fly on an overloaded server, then everything can happen, up to a kernel panic.
On /boot do not put ext4 historically (before grub was not able to ext4). Well, yes - he really is not needed there. There are no technical problems for this.
> does not recommend a separate /boot partition if RAID1 is planned;
All of a sudden you may find yourself with a bootloader that doesn't know how to build raid1. Again - in fact, there are no technical obstacles in stable debian for this.
> what determines the size of the /boot partition;
The amount of slag that you will add there. For “they installed a new kernel, checked it, removed the old one” 256 MB is more than enough. In general, one core in /boot eats ~ 30-40 megabytes.
> what for to carry on sections of a folder of a root section;
It is not necessary if you do not understand what it is for.
It makes sense to take out the docroot of web servers, for example, what to mount with noatime. It makes sense to mount /bin /usr/bin, /etc and so on in RO, so that a kiddis script that accidentally gets there does not break anything.
All in all, it's a no-brainer.
In fact, the main use case is so that the place on / does not end. Therefore, if you do not understand FS tuning and mount parameters, then it makes sense to separate only those partitions that you do not control writing to (/var/lib/vz, for example), so that the place in the root does not suddenly run out on the fly ( which is not fatal, but unpleasant).

Answer 2

why not put on /boot ext4;
I don’t know how it is now, but a couple of years ago, to run Grub from ext4, you had to jump with a tambourine.
what determines the size of the /boot partition;
the size of the files on it. a lot there is not necessary
why to mirror swap;
Here you work like this on the server, it swaps cheerfully, and then the disk with the swap flies out. what will happen to the server and the data in the swap?
why partition the folders of the root partition;
so that the overflow of one section would not affect the others.

Answer 3

- for / boot ext4 is not needed, as well as ext3. Journaling is redundant. There will be enough ext2.
- I don’t know about others, I realized for myself that 256 is enough. Well, I don't think it explains anything.
- swap does not need to be mirrored. Moreover, using RAID for swap is redundant. Two partitions are made so that the total is RAM * 2. The kernel itself will destroy the optimal way to use it.
- so that you can, for example, unmount and check the file system without loading in single mode when it is not necessary.

Answer 4

Make default debian breakdown from hatzner.
Everything is fine there.