[no subject]

eader.dragonflybsd.org> <45d98a2c$0$833$415eb37d@crater_reader.dragonflybsd.org> <200702192245.l1JMjH7a091153@apollo.backplane.com> <45DA49B7.7000806@exemail.com.au> <200702200711.l1K7B7n1094896@apollo.backplane.com>
From: Robert Clark <Robert_Clark@mac.com>
Subject: Re: Plans for 1.8+ (2.0?)
Date: Wed, 21 Feb 2007 00:02:22 -0800
BestServHost: crater.dragonflybsd.org
List-Post: <mailto:users@crater.dragonflybsd.org>
List-Subscribe: <mailto:users-request@crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:users-request@crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:users-request@crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-users@crater.dragonflybsd.org>
MIME-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
In-Reply-To: <200702200711.l1K7B7n1094896@apollo.backplane.com>
Sender: users-errors@crater.dragonflybsd.org
Errors-To: users-errors@crater.dragonflybsd.org
Lines: 42
NNTP-Posting-Host: 216.240.41.25
X-Trace: 1172045591 crater_reader.dragonflybsd.org 831 216.240.41.25
Xref: crater_reader.dragonflybsd.org dragonfly.users:8921


Would file locking and range locking be handled separately?

On Feb 19, 2007, at 11:11 PM, Matthew Dillon wrote:

>
> :Hey Matt,
> :1) Does your filesystem plan include the ability to grow and shrink a
> :partition/volume? ie. /home is running out of space so we could run
> :"shrinkfs" ... on /usr which has a lot of space and "growfs" ...  
> on /home
>
>     The filesystem's backing store will be segmented.  Segment size  
> can
>     range from 1MB to 4GB (ish).  A 'partition' would be able to hold
>     multiple segments from the filesystem's point of view, but the  
> main
>     purpose of the segmentation is to create large, near-independant
>     blocks of data which can be dealt with on a segment-by-segment  
> basis
>     (e.g. for recovery, fsck/check, replication, growing, and  
> shrinking
>     purposes).

Having partition affinity would allow a LUN to be moved to a new  
host, and the vkernel moved along with it.

>     Segmentation also means the filesystem's backing store is not
>     restricted to a single block device but can be glued together
>     with several block devices, or even mixed-and-matched between
>     separate replicated data stores for recovery purposes.

Maybe we can pull in some iSCSI initiator code.

>     So, yes, it will be possible to grow or shrink the filesystem on
>     a segment-by-segment basis.
>
<snip>
> 					-Matt
> 					Matthew Dillon
> 					<dillon@backplane.com>