zfs discuss - Sep 2009 - moving files from one fs to another, splittin/merging

I may have missed something in the docs, but if I have a file in one FS, 
and want to move it to another FS (assuming both filesystems are on the 
same ZFS pool), is there a way to do it outside of the standard 
mv/cp/rsync commands? For example, I have a pool with my home directory as 
a FS, and I have another FS with ISOs. I download an ISO of an OpenSolaris 
DVD (say, 3GB), but it goes into my home directory. Since ZFS is all about 
pools and shared storage, it seems like it would be natural to move the 
file vi a ''zfs'' command, rather mv/cp/etc...

On a related(?) note, is there a way to split an existing filesystem? To 
use the example above, let''s say I have an ISO directory in my home 
directory, but it''s getting big, plus I''d like to share it out
on my
network. Is there a way to split my home directory''s FS, so that the
ISO
directory becomes its own FS?

Paul Archer

On Thu, 24 Sep 2009, Paul Archer wrote:
> I may have missed something in the docs, but if I have a file in one FS, 
> and want to move it to another FS (assuming both filesystems are on the 
> same ZFS pool), is there a way to do it outside of the standard 
> mv/cp/rsync commands?
Not yet.  CR 6483179 covers this.
> On a related(?) note, is there a way to split an existing filesystem?
Not yet.  CR 6400399 covers this.


Regards,
markm

Thanks for the info. Glad to hear it''s in the works, too.

Paul


1:21pm, Mark J Musante wrote:
> On Thu, 24 Sep 2009, Paul Archer wrote:
>
>> I may have missed something in the docs, but if I have a file in one
FS,
>> and want to move it to another FS (assuming both filesystems are on the
>> same ZFS pool), is there a way to do it outside of the standard
mv/cp/rsync
>> commands?
>
> Not yet.  CR 6483179 covers this.
>
>> On a related(?) note, is there a way to split an existing filesystem?
>
> Not yet.  CR 6400399 covers this.
>
>
> Regards,
> markm
>

> Thanks for the info. Glad to hear it''s in the works, too.
It is not in the works. If you look at the bug IDs in the bug database
you will find no indication of work done on them.

>
> Paul
>
>
> 1:21pm, Mark J Musante wrote:
>
>> On Thu, 24 Sep 2009, Paul Archer wrote:
>>
>>> I may have missed something in the docs, but if I have a file in
one FS,
>>> and want to move it to another FS (assuming both filesystems are on
the same
>>> ZFS pool), is there a way to do it outside of the standard
mv/cp/rsync
>>> commands?
>>
>> Not yet. ?CR 6483179 covers this.
>>
>>> On a related(?) note, is there a way to split an existing
filesystem?
>>
>> Not yet. ?CR 6400399 covers this.
>>
>>
>> Regards,
>> markm
>>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>

Once data resides within a pool, there should be an efficient method of moving
it from one ZFS file system to another. Think Link/Unlink vs. Copy/Remove.

Here''s my scenario... When I originally created a 3TB pool, I
didn''t know the best way carve up the space, so I used a single, flat
ZFS file system. Now that I''m more familiar with ZFS, managing the
sub-directories as separate file systems would have made a lot more sense
(seperate policies, snapshots, etc.). The problem is that some of these
directories contain tens of thousands of files and many hundreds of gigabytes.
Copying this much data between file systems within the same disk pool just seems
wrong.

I hope such a feature is possible and not too difficult to implement, because
I''d like to see this capability in ZFS.

Regards,
mikebo
-- 
This message posted from opensolaris.org

On 21/10/2009, at 7:39 AM, Mike Bo wrote:
> Once data resides within a pool, there should be an efficient method  
> of moving it from one ZFS file system to another. Think Link/Unlink  
> vs. Copy/Remove.
I agree with this sentiment, it''s certainly a surprise when you first  
notice.
> Here''s my scenario... When I originally created a 3TB pool, I
didn''t
> know the best way carve up the space, so I used a single, flat ZFS  
> file system. Now that I''m more familiar with ZFS, managing the
sub-
> directories as separate file systems would have made a lot more  
> sense (seperate policies, snapshots, etc.). The problem is that some  
> of these directories contain tens of thousands of files and many  
> hundreds of gigabytes. Copying this much data between file systems  
> within the same disk pool just seems wrong.
>
> I hope such a feature is possible and not too difficult to  
> implement, because I''d like to see this capability in ZFS.
It doesn''t seem unreasonable. It seems like the different properties  
available on the given datasets (recordsize, checksum, compression,  
encryption, copies, version, utf8only, casesensitivity) would have to  
match, or else fall back to blind copying?
>
> Regards,
> mikebo
> -- 
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Mike Bo wrote:
> Once data resides within a pool, there should be an efficient method of
moving it from one ZFS file system to another. Think Link/Unlink vs.
Copy/Remove.
>
> Here''s my scenario... When I originally created a 3TB pool, I
didn''t know the best way carve up the space, so I used a single, flat
ZFS file system. Now that I''m more familiar with ZFS, managing the
sub-directories as separate file systems would have made a lot more sense
(seperate policies, snapshots, etc.). The problem is that some of these
directories contain tens of thousands of files and many hundreds of gigabytes.
Copying this much data between file systems within the same disk pool just seems
wrong.
>
> I hope such a feature is possible and not too difficult to implement,
because I''d like to see this capability in ZFS.
>
>   
Alternatively, (and I don''t know if this is feasible,) it might be 
easier and/or better to be able to set those properties on, and 
independently snapshot regular old sub directories.

Just an idea....

  -Kyle
> Regards,
> mikebo
>

Is there a way to use only 2 or 3 digits for the second level of the
var/pkg/download cache?  This directory hierarchy is particularly problematic
relative to moving, copying, sending, etc.  This would probably speed up lookups
as well.
-- 
This message posted from opensolaris.org