I currently take the approach that unless I have specific IO needs for a volume, I will work with one partition for OS and data as it is the most efficient use of disk space.
This means typically 3 volumes 1) boot/UEFI FAT 32 partition 2) swap 3) file system. I only have 1 disk though so raid doesn't enter the equation... however, I took a look at my Synology NAS recently... it's rather informative... TLDR: synology takes the first slice (~2-3GB) of every disk in the device and makes a RAID 1 volume for the operating system, then does the same with the second slice to make a swap partition. You can lose all but one disk and still have a bootable working machine. the rest of the disk is available to make volumes out of. it uses md for managing the raid disks and lvm for managing the volumes. in the case of a 3 disk machine, I'd take the same approach. Make a RAID 5 array across all three disk using mdadm. make a boot partition, a swap partition and an ext4 partition. Use lvm to make a single mount point attached to / On 23 May 2018 at 22:47, Russell Coker via luv-main <[email protected]> wrote: > On Wednesday, 23 May 2018 1:08:22 AM AEST Craig Sanders via luv-main wrote: > > Russell's probably got some DDR 1333 in the LUV hardware library to give > > away. > > > > Dunno if he'll have ECC or not, but 8 or 16 GB of non-ECC is probably > better > > than 4GB of ECC. > > Probably not ECC and we keep running out of DDR3 as that's in demand. If > anyone has upgraded to a DDR4 system and has some spare DDR3 RAM then > please > donate it. > > > For lvm and mdadm, last I checked the best advice was to use LVM on top > of > > mdadm. Just make one big RAID-1 of the entire disk with mdadm and then > > use LVM to create logical volumes for /, /home, and any other > "partitions" > > you might want. > > Or just use mdadm and skip LVM. Have a single large filesystem. > > > > How do I restrict the system install to the first 100Gb on each disk > for / > > > and the other 900Gb /home for general duty data (music and some > > > instructional videos) > > > > On zfs, by setting a quota of 900GB on the /home dataѕet. Maybe a > > reservation on the rootfs too, so that / has a guaranteed minimum 100GB. > > If you later find you need more or less space reserverd, it's one simple > > command to change either a quota or a reservation. > > For a single user system it's usually better to avoid quotas but use > separate > ZFS filesystems for different purposes. Then if the zpool runs low on > space > you can just run "df -h" to see where it's being used. You don't really > want > programs to start crashing because some filesystem has run out of space > while > others have plenty. > > -- > My Main Blog http://etbe.coker.com.au/ > My Documents Blog http://doc.coker.com.au/ > > > > _______________________________________________ > luv-main mailing list > [email protected] > https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main > -- Dr Paul van den Bergen
_______________________________________________ luv-main mailing list [email protected] https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
