From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4AA69FD0.6030907@0x6a.com>
Date: Tue,  8 Sep 2009 13:17:52 -0500
From: Jack Norton <jack@0x6a.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
References: <728aafe49c38f76663622f541315ed73@quanstro.net>
In-Reply-To: <728aafe49c38f76663622f541315ed73@quanstro.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Petabytes on a budget: JBODs + Linux + JFS
Topicbox-Message-UUID: 6ad90bf0-ead5-11e9-9d60-3106f5b1d025

erik quanstrom wrote:
>> Also, another probably dumb question: did the the fileserver machine use
>> the AoE device as a kenfs volume or a fossil(+venti)?
>>
>
> s/did/does/.  the fileserver is running today.
>
> the fileserver provides the network with regular 9p fileserver
> with three attach points (main, dump, other) accessable via il/ip.
> from a client's view of the 9p messages, fossil, fossil+venti and
> ken's fs would be difficult to distinguish.
>
> - erik
>
>

Very cool.
So what about having venti on an AoE device, and fossil on a local drive
(say an ssd even)?  How would you handle (or: how would venti handle), a
resize of the AoE device?  Let's say you add more active drives to the
RAID pool on the AoE machine (which on a linux fileserver would then
involve resizing partition on block device, followed by growing the
volume groups if using lvm, followed by growing the filesystem).
Sorry for thinking out loud... I should get back to work anyway....  fun
thread though.

-Jack