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

[John Stoffel]

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

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

Chris> Growing the FS is just either extending or adding a new extent
Chris> tree.  Shrinking is more complex.  The extent trees do have
Chris> back pointers to the objectids that own the extent, but
Chris> snapshotting makes that a little non-deterministic.  The good
Chris> news is there are no fixed locations for any of the metadata.
Chris> So it is at least possible to shrink and pop out arbitrary
Chris> chunks.

That's good to know.  Being able to grow (online of course!) is great,
but so would shrinking as well.   It makes life so much more flexible
for the SysAdmins, which is my particular focus... since it's my day
job. 

>> 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.

Chris> So far, I'm not planning quotas beyond the subvolume level.

So let me get this straight.  Are you saying that quotas would only be
on the volume level, and for the initial level of sub-volumes below
that level?  Or would *all* sub-volumes have quota support?  And does
that include snapshots as well?

>> 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.  

Chris> HSM in general is definitely interesting.  I'm afraid it is a
Chris> long ways off, but it could be integrated into the scrubber
Chris> that wanders the trees in the background.

Neat.  As long as the idea is kept around a bit, that would be nice
for an eventual addition.  Or maybe someone needs to come up with a
stackable filesystems to take care of this...

John

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/