Date: Tue, 15 Feb 2000 12:36:54 -0600 (CST) From: Joe Greco <jgreco@ns.sol.net> To: kris@hiwaay.net (Kris Kirby) Cc: peter@netplex.com.au, chat@FreeBSD.ORG Subject: Re: Filesystem size limit? Message-ID: <200002151836.MAA64919@aurora.sol.net> In-Reply-To: <Pine.BSF.4.10.10002151159000.20738-100000@barricuda.bsd.nws.net> from Kris Kirby at "Feb 15, 2000 12: 1:27 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > I figured somebody'd have a fast, smart answer :-) > > Is this one of those "three things, pick two" things? :-) > > > The trick to fsck is that you don't want more inodes than you really need. > > Once you get past that, fsck flies. The previous generation of binaries > > server, worked on 27 36GB drives split into 10 partitions, designed for > > parallelism. Hit RESET and the news filesystems take ~30 seconds to fsck. > > 10 partitions? How do you accomplish this? BSD disklabel is only 8, and > DOS is 4. I could see > 20 this way, but it seems a waste on a *real* > machine. (PS: How many procs? How much RAM?) I meant 10 filesystems. I shouldn't send mail when I've been up so many hours (I didn't realize that the hardware had arrived until I was just about ready to leave for the day, and then built a 1.8TB server with removable drive modules and all the extras). You can do 10 partitions: /dev/da1s1d 7847616 1521664 5698144 21% /news /dev/da1s2e 93656576 83496896 2667168 97% /news/spool/news/N.00 /dev/da1s2f 93656576 83900832 2263232 97% /news/spool/news/N.01 /dev/da1s2g 93656576 83749792 2414272 97% /news/spool/news/N.02 /dev/da1s2h 93656576 83566928 2597136 97% /news/spool/news/N.03 /dev/da1s3e 93656576 83991808 2172256 97% /news/spool/news/N.04 /dev/da1s3f 93656576 83811168 2352896 97% /news/spool/news/N.05 /dev/da1s3g 93656576 84474864 1689200 98% /news/spool/news/N.06 /dev/da1s3h 93656576 83931312 2232752 97% /news/spool/news/N.07 on one of the old Mylex DAC960SX SCSI-SCSI controllers. Use multiple slices. There's invisible slices for copies of the OS boot drive too. This is one of the machines being replaced with what's below. I'm doing /dev/vinum/news 14149612 9705 14139907 0% /news /dev/vinum/n0 192125401 2 192125399 0% /news/spool/news/N.00 /dev/vinum/n1 192125401 2 192125399 0% /news/spool/news/N.01 /dev/vinum/n2 192125401 2 192125399 0% /news/spool/news/N.02 /dev/vinum/n3 192125401 2 192125399 0% /news/spool/news/N.03 /dev/vinum/n4 192125401 2 192125399 0% /news/spool/news/N.04 /dev/vinum/n5 192125401 2 192125399 0% /news/spool/news/N.05 /dev/vinum/n6 192125401 2 192125399 0% /news/spool/news/N.06 /dev/vinum/n7 192125401 2 192125399 0% /news/spool/news/N.07 /dev/vinum/n8 192125401 2 192125399 0% /news/spool/news/N.08 on the new machines, a pair of AHA-3940UW's talking to 4 shelves of 9 50GB drives each, and vinum to stripe each of the drives together, cross-wise across the busses (i.e. scbus1:0, 2:0, 3:0, 4:0 striped, 1:1, 2:1,...) To get a redundant /news partition, I take 768MB from each drive, stripe them together as two plexes, and the plexes are mirrored. Losing a single drive will therefore trash the corresponding "N.0x" filesystem, causing me to lose 1/9th my spool, but it won't cause me to lose history. Additional note: vinum can be used as a great way to put many "partitions" on a single disk. My production spool servers run a few hundred proc's on half a gig of RAM. Works fine. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002151836.MAA64919>