Date: Mon, 4 Nov 2019 16:07:03 +1100 From: MJ <mafsys1234@gmail.com> To: freebsd-questions@freebsd.org Cc: =?UTF-8?Q?Trond_Endrest=c3=b8l?= <trond.endrestol@ximalas.info> Subject: Re: doc listing of a full install's structure? Message-ID: <8b41fb80-6ad9-7a77-f8d4-96afeecb1675@gmail.com> In-Reply-To: <1DDBDC78-CFC3-4BF6-97A4-C4D808268D1F@council124.org> References: <20191101024817.GA60134@admin.sibptus.ru> <558fd145-ad3e-90dc-5930-c01ca0c27d3c@panix.com> <alpine.BSF.2.21.9999.1911010912090.73442@mail2.nber.org> <5A739711-3758-4FAB-BEA7-D37A06AB92B9@council124.org> <7138d654-93b3-42fc-93b7-e96e2613945e@gmail.com> <1DDBDC78-CFC3-4BF6-97A4-C4D808268D1F@council124.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/11/2019 2:32 pm, Frank Fenderbender wrote: > Thanks for your astute comments, questions, and requests for better clarification (which was definitely lacking in my query). > Sorry for that. > Hopefully I can distill down my goals as well as let be known my sense of what I am doing, which.. heh, heh... will also > expose what I do NOT know, but that's what this is all about: learning from the robust thinkers and experienced experimenters out there in the list. > For that (and all of you) I am grateful. So, thanks to anyone reviewing or commenting. > > I'm trying to research before accepting any installation or documentation "defaults" which may or may not be mins, maxs, optimum, cast-in-stone, etc.. > I know enough not to base the FreeBSD system needs/performance upon any other OS's, however, Ubuntu is all I have to go on thus far, so > I'll use it as an example. > > I can base this on a combination of different sources: guess, gut feeling, qualified-and-similar "solutions" from web posts from which I have to > interpolate, extrapolate, combine, and filter. The latter is always a lot of work sauced with chance and luck. > My gut says to go with the listees' experiences, as you are current and still full of imaginative zest and fire. > > Okay, maybe it's best to show what I've got so far (and it's less-than-"perfect", esp. since what the FreeBSD documentation wisely > suggests [listed below]). > > On Ubuntu, one can let the install all the OS's folders into 3 partitions, however, performance and backups are > easier when the pre-install space is modularized so that the install finds a mounted partition > for its larger and more-used folders. > It's even recommended that certain partitions be located in certain drive regions for "first" and "fast" access (e.g., EFI, MBR, > /boot, etc.). Hi Frank, Frankly (pun!), this is rather old information. In days of yore, this was the case when we had to grab sectors/bytes per sector/cylinders etc and put them on even boundaries and so on. Nowadays the disks are so fast, have such good firmware for seeking that it's really a moot point. For SSDs it's irrelevant. Anyway. > > Ubuntu 16.04/18.04 LTS installations will default to just three partitions: > label=ESP (type=fat32; flags=boot,esp) > label=OS; type=fat32; flag=msftdata) > label=UBUNTU (type=ext4; no flags). > > You add your swap from the "free space" left over.... > > My two systems have their Ubuntu 18.04 (1T) drives set up as: > > what type mount-pt input-size actual-size > ------- ------- ------------ --------------- --------------- > free space 1M > /dev/sda1 fat32 /boot/efi 1,001M 1,000M (1G) <== input-size covers the 'free space' preceding it > /dev/sda2 fat32 /biosgrub 10M 10M (0.01G) > /dev/sda3 ext4 /boot 4,000M 4,000M (4G) > /dev/sda4 ext4 / 300,000M 300,000M (300G) <== the "root partition" is used for the OS > /dev/sda5 ext4 swap 12,000M 12,000M (12G) > /dev/sda6 ext4 /usr 20,000M 20,000M (20G) > /dev/sda7 ext4 /tmp 12,000M 12,000M (12G) > /dev/sda8 ext4 /usr/local 50,000M 50,000M (50G) > /dev/sda9 ext4 /home 600,000M 600,000M (600G) > > Additional installs of Ubuntu would leave off the /boot/efi partition. As will FreeBSD. If you don't want FreeBSD to put its own boot manager on your disk, ensure you select that when it comes time to do so during the install. You can easily add FreeBSD partition to the existing Grub boot loader and enable it to be a boot option (even on another disk). > UEFI will map GRUB boot list choices to their respective bootloaders on their respective HDs. > > So, I seek to do the same (or similar) for FreeBSD on one of the additional internal HDs by partitioning it before > the installation defaults the drive into a series/set of default usage issues. > > The amount of swap is based on a multiplier of how much RAM you have. Each system has 32G. I look at swap as something I have in an emergency. I would consider 12G to be excessive swap. If you're swapping that much then you really need to look at getting more RAM. That's just my personal opinion made even more resolute by the fact RAM (either ECC or not) is just so cheap nowadays. 15 years ago, this was not the case. > The parttion-size numbers are different depending upon whether you're using ZFS -- which I will not -- and the size of the HD itself. > You don't just double what a 500G HD uses to get your partition-sizes for a 1T HD, etc. > At a certain point the numbers do not need to get larger, and certain ones have a minimum. > I seek that information. > > -------------------- > W/rt/ FreeBSD: [ handbook quotes removed] > I seek more than a description or documentation of where to find a default installation's partitions listed. The answer is, of course, 42. :-) :-) > I want to know from people who planned their partitions for performance, maintenance, and non-default use, in my case, development/testing I am not sure what you are trying to achieve. Everyone's usage differs. If I'm setting up a database server, it has different requirements to a proxy server or a web server to my home PC. A development server (source code) might require more cores and faster SSDs. In fact, SSDs are basically obligatory nowadays for any of the servers I have anything to do with (and not just FreeBSD). As well, a lot of servers are virtual with their storage in SANs. So everyone's feedback can only be from their own perspective and probably won't be yours. There is no ONE WAY to do things. However, it is prudent to have a partition for /var, /tmp and /usr if you're stuck on UFS. What sizes they are depends on your usage. It's just so variable it is (I think) impossible to give a definitive answer. Some people might run 10 jails, some might run 1 or none. You might decide you want to run a jail or two, so that's extra space. Is it going to go into /usr or perhaps /var? > of projects aiming for cross-platform and platform-independent Python, C, Java, PyQt5 code (using SQLite) and the dev/test OSs on two N-boot workstations are Windows10, FreeBSD, Fedora, Debian, Ubuntu, DragonflyBSD, and GhostBSD. > > So, I am researching what people have done with 1TB/2TB FreeBSD-exclusive HDs when ZFS is not used. Personally with 32G of RAM, I would be using ZFS. It's more reliable, you're able to use boot environments and it's a better choice for data security, snapshots and so on. So, if there's one recommendation I would add, it is use ZFS. Then you avoid partitions and just use the entire disk as ZFS. > Hope that makes it more clear. As mud ... :-) Regards, Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8b41fb80-6ad9-7a77-f8d4-96afeecb1675>