On Tue, May 30, 2006 at 12:30:50PM +0200, Constantin Gonzalez Schmitz wrote:
> Hi,
>
> >>Yes, a trivial wrapper could:
> >>1. Store all property values in a file in the fs
> >>2. zfs send...
> >>3. zfs receive...
> >>4. Set all the properties stored in that file
> >
> >IMHO 3. and 4. need to be sw
Hi,
Yes, a trivial wrapper could:
1. Store all property values in a file in the fs
2. zfs send...
3. zfs receive...
4. Set all the properties stored in that file
IMHO 3. and 4. need to be swapped - otherwise e.g. files will
not be compressed when restored.
hmm, I assumed that the ZFS stream
On Tue, May 30, 2006 at 04:11:13AM +0200, Franz Haberhauer wrote:
> Is the idea of 'zfs send -p' to only send the properities in addition
> to the content or without content? Actually I would expect sending the
> poperties as the default for send and an option for receive not to
> apply the propert
Is the idea of 'zfs send -p' to only send the properities in addition to
the content or
without content? Actually I would expect sending the poperties as the
default for send
and an option for receive not to apply the properties - and have an
option (-p) for
send to send only the properties e.g.
Yep, thanks for digging that up. FYI, this is RFE 6421959 "want zfs
send to preserve properties ('zfs send -p')".
--matt
On Mon, May 29, 2006 at 02:21:44PM -0400, Jeff Victor wrote:
> An earlier response from Matt Ahrens, to a similar question:
>
> > 'zfs backup/restore' (now 'zfs send/receive'
Jeff Victor wrote:
Yes, a trivial wrapper could:
1. Store all property values in a file in the fs
2. zfs send...
3. zfs receive...
4. Set all the properties stored in that file
IMHO 3. and 4. need to be swapped - otherwise e.g. files will
not be compressed when restored.
- Franz
Franz Habe
Yes, a trivial wrapper could:
1. Store all property values in a file in the fs
2. zfs send...
3. zfs receive...
4. Set all the properties stored in that file
Franz Haberhauer wrote:
Jeff Victor wrote:
An earlier response from Matt Ahrens, to a similar question:
> 'zfs backup/restore' (now 'zf
Jeff Victor wrote:
An earlier response from Matt Ahrens, to a similar question:
> 'zfs backup/restore' (now 'zfs send/receive') currently only sends the
> filesystem's contents, and not its settings. This is useful if, for
> example, you want to use different settings on the remote side (eg.
An earlier response from Matt Ahrens, to a similar question:
> 'zfs backup/restore' (now 'zfs send/receive') currently only sends the
> filesystem's contents, and not its settings. This is useful if, for
> example, you want to use different settings on the remote side (eg. turn
> on compression)
Where are properties of a ZFS filesystem stored (e.g. non-default
mountpoints, quota, reservation,
compression, exported shares etc.)?
Do backup/restore mechanisms (zfs send/receive, Networker/NetBackup/TSM,
*tar etc.)
handle (save/restore) them automagically or are there additional
procedures
10 matches
Mail list logo
