Re: [ANNOUNCE] Btrfs: a copy on write, snapshotting FS

["John Stoffel" <john@stoffel.org>]

>>>>> "Chris" == Chris Mason <chris.mason@oracle.com> writes:

Chris> After the last FS summit, I started working on a new filesystem
Chris> that maintains checksums of all file data and metadata.  Many
Chris> thanks to Zach Brown for his ideas, and to Dave Chinner for his
Chris> help on benchmarking analysis.

Chris> The basic list of features looks like this:

Chris> 	* Extent based file storage (2^64 max file size)
Chris> 	* Space efficient packing of small files
Chris> 	* Space efficient indexed directories
Chris> 	* Dynamic inode allocation
Chris> 	* Writable snapshots
Chris> 	* Subvolumes (separate internal filesystem roots)
Chris> 	- Object level mirroring and striping
Chris> 	* Checksums on data and metadata (multiple algorithms available)
Chris> 	- Strong integration with device mapper for multiple device support
Chris> 	- Online filesystem check
Chris> 	* Very fast offline filesystem check
Chris> 	- Efficient incremental backup and FS mirroring

So, can you resize a filesystem both bigger and smaller?  Or is that
implicit in the Object level mirroring and striping?  

As a user of Netapps, having quotas (if only for reporting purposes)
and some way to migrate non-used files to slower/cheaper storage would
be great.

Ie. being able to setup two pools, one being RAID6, the other being
RAID1, where all currently accessed files are in the RAID1 setup, but
if un-used get migrated to the RAID6 area.  

And of course some way for efficient backups and more importantly
RESTORES of data which is segregated like this.  

John