From mboxrd@z Thu Jan 1 00:00:00 1970 References: <868ttidh05.fsf@cmarib.ramside> From: Steve Simon Content-Type: text/plain; charset=us-ascii In-Reply-To: Message-Id: Date: Thu, 20 Oct 2016 22:54:24 +0100 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: [9fans] Fossil+Venti system memory requirements to be aware of? Topicbox-Message-UUID: a60eb824-ead9-11e9-9d60-3106f5b1d025 i agree absolutely with steve here, expanding venture arena by arena is easy= , the ventibackup scripts show you how. even easier is to add arenas on a di= fferent disk partition to the same venti. personally i wouldn't keep music or videos in venti. they don't compress wel= l using the arithmetic techniques in venti and the de duplication is unlikel= y to be a win either. just put them on a separate mirrored partition. i wrote a doc called venti rescue which details replacing disks and rebuildi= ng your venti. it may be of help. -Steve > On 20 Oct 2016, at 19:41, Steven Stallion wrote: >=20 >> On Thu, Oct 20, 2016 at 1:15 PM, wro= te: >> Steven Stallion writes: >>=20 >>> Sizing venti is also simple. >>=20 >> I disagree with this. The best way to configure venti depends largely >> on how you plan to use it. I have multiple venti servers configured for >> different uses. For example, I keep my DVD images on a different venti >> server than I do for smaller, more frequently-used files such as mail. >=20 > see venti(8); there's plenty of advice on configuring your store with > rough estimations for an initial conf file. Once you decide your > geometry, it's trivial to extend the number of arenas in the store, > just remember to reindex. >=20 >> I don't know that to be true. If the source and destination volumes are >> the same size, yes, it's easy to just dd the arenas. But if you're >> relocating to a smaller/larger partition, what would be an easy way to >> do that? >=20 > see venti-backup(8).