Per Jessen wrote:
Linda Walsh wrote:
Another reason I have "smallish" system drives .. I use 15K SAS drives which are smaller. To get the space I have & optimize speed, I 'short-stroke' the array, using only the first half of 3-72GB drives, with 1 being parity. Effectively I only have 72GB for all of '/', '/usr', 'var, var/cache, swap, boot.
That ought to be more than plenty, even for a desktop machine? I mean, I usually allocate 10Gb for a server (without data volumes), and a typical install will usually take up about 2-3Gb.
I don't even have room for /usr/share on the root drives anymore -- it grew too big -- so my /usr/share lives on /home/share, which is then mounted via bind to /usr/share.
Hmm, you have 72Gb for your root filesystem, but not enough for /usr/share ??
73GB is usable for the root Hard disk -- not '/' HD: Isn't /var, and /tmp also needed for boot .. Also I tried to create my disks such that they'd have no more than 60% usage, 75% being the worst for a system disk (of these sizes == not same percentages for TB disks)... 128M /boot 1 swap 4 /var (+ /tmp mounted on /var/rtmp) -extended- 6 / 10 9.2 /usr Number Size Type File system 1 13GB primary xfs type=83 (root or "/") 64MB, boot 2 8.5GB primary xfs type=83 (/var + /tmp) 3 1GB primary xfs boot, type=83 (boot) [4 49.5GB extended type=05 (---) 5 8.5MB logical swap(v1) type=82 (swap) 6 16.1GB logical xfs type=83 (/usr/) 7 10.7GB logical xfs type=8 (/var/cache) ] ---- 72GB total 15G (/usr/share - another device).
One thing that doesn't get advertised much, is that /usr/share -- specifically meant to be non-arch-specific, shared-content, is ALSO being required now in order to boot.
I agree, I haven't seen that mentioned, but then I also haven't seen (m)any convincing reasons for keeping it on a separate filesystem.
---- I didn't have room? I would have kept it with /usr, but ran out of space on my root disk...
Right.
Someone put in a superfluous and ill-considered check to make sure your root disk is read-only upon booting, because they "know"[sic], that you can't run a file system's "fsck" script on a writable disk.
I could be wrong, but hasn't openSUSE been like that for years and years?
---- On this one -- it may be it has been there, and I only recently changed to mounting my rootfs 'rw', as there is no need to mount it 'ro' for 'fsck'.. as fsck doesn't check or need it to be. My workaround was to "chkconfig boot.rootfsck off" as it is not needed. If only instead of boot.localfs, they had boot.localfsck as a separate pre-step, then I wouldn't have to bother with making /bin/fsck.xfs a link to /bin/true. Good thing it was a hard-link, or it would have failed.
It's bad enough when one can't mount /usr because mount is on /usr, but if you can't get udev running, and that forces /usr/share to not be mountable (which udev needs), OpenSuse has created a maintenance nightmare.
Isn't your /usr/share issue a bit contrived, Linda?
--- Not at all... 15K SCSI drives (now SAS) aren't the size of SATA's... They are up to about 450GB now with SATA @ 3TB, but when SATA was at 1TB, SAS's were about 143, and when SATA was ATT and SAS was SCSI, SCSI drives were in the 18.2 for 'cheap', and 36.4 for expensive. That's about when I setup my 1st server on a workstation. This server's root was setup with 73GB was reasonable, and 146GB was affordable, BUT -- compared to 1TB SATA's, .. so the system disks got a short-stroked, 3-disk RAID5 with cheap 73GB disks @ 15.5K speed -- with the short stroking, cuts the the nominal seek time from 5-6ms, down to 2-3ms. Figured that was fine for my boot files.. The shorter seek times are good for booting. So really, when /usr/share grew to ~ 20GB by itself (I think I have it down to about 15GB used now, but not as much SW installed, it pegged out /usr... So I moved it to my /home partition that's slower on seeks but faster on large fiels (RAID50). So not contrived in the slightest.
I also find the move /usr to be a solution looking for a problem, but I personally don't have a real problem with it as long as /usr can still be put on a separate filesystem (nfs etc). I guess that is taken care of by keeping /usr/bin/mount in the initrd.
--- If you look in initrd, for /usr/bin/mount, you won't find it. It's in "/bin".... ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org