I'm working on replication of ZFS. Using perl script and SSH access with
authorized key.
My script automatically creates a new snapshot for each ZFS filesystem.
It's too slow to send snapshots to remote server. Not because of size of
snapshot. Cause SSH with authorized key takes several seconds
hi there,
On Sun, 2006-09-10 at 23:49 -0700, Bui Minh Truong wrote:
I'm working on replication of ZFS. Using perl script
and SSH access with authorized key.
Cool - I did exactly same thing last week, adding send/receive
functionality to the SMF service I had been playing with. More at
On Mon, 2006-09-11 at 06:39 -0700, Bui Minh Truong wrote:
Do you have any suggestions?
Yeah, I think we need more information to debug this: I'm seeing -
[EMAIL PROTECTED] ptime ssh usuki hostname
usuki
real0.600
user0.065
sys 0.013
- Oh, and yeah - what James said
Hi,
I was looking for the zfs system calls to check zfs quotas from
within C code, analogous to the quotactl(7I) interface for UFS,
and realized that there was nothing similar. Is anything like this
planned? Why no public API for ZFS?
Do I start making calls to zfs_prop_get_int(), like in the
Luke Scharf wrote:
zfs set sharenfs='rw=.foo-internal.bar.edu insecure no_root_squash'
xr7/group/ntnt ; zfs share -a
Also, is this the proper syntax for the no_root_squash?
Thanks,
-Luke
smime.p7s
Description: S/MIME Cryptographic Signature
___
Dale Ghent wrote:
On Sep 11, 2006, at 4:49 PM, Luke Scharf wrote:
Luke Scharf wrote:
zfs set sharenfs='rw=.foo-internal.bar.edu insecure
no_root_squash' xr7/group/ntnt ; zfs share -a
Also, is this the proper syntax for the no_root_squash?
no_root_squash is a Linux-ism.
What you're
Here is a proposal for a new 'copies' property which would allow
different levels of replication for different filesystems.
Your comments are appreciated!
--matt
A. INTRODUCTION
ZFS stores multiple copies of all metadata. This is accomplished by
storing up to three DVAs (Disk Virtual
On 9/11/06, Matthew Ahrens [EMAIL PROTECTED] wrote:
B. DESCRIPTION
A new property will be added, 'copies', which specifies how many copies
of the given filesystem will be stored. Its value must be 1, 2, or 3.
Like other properties (eg. checksum, compression), it only affects
newly-written
James Dickens wrote:
On 9/11/06, Matthew Ahrens [EMAIL PROTECTED] wrote:
B. DESCRIPTION
A new property will be added, 'copies', which specifies how many copies
of the given filesystem will be stored. Its value must be 1, 2, or 3.
Like other properties (eg. checksum, compression), it only
Mike Gerdts wrote:
Is there anything in the works to compress (or encrypt) existing data
after the fact? For example, a special option to scrub that causes
the data to be re-written with the new properties could potentially do
this.
This is a long-term goal of ours, but with snapshots, this
On 9/11/06, Matthew Ahrens [EMAIL PROTECTED] wrote:
James Dickens wrote:
On 9/11/06, Matthew Ahrens [EMAIL PROTECTED] wrote:
B. DESCRIPTION
A new property will be added, 'copies', which specifies how many copies
of the given filesystem will be stored. Its value must be 1, 2, or 3.
Like
James Dickens wrote:
though I think this is a cool feature, I think i needs more work. I
think there sould be an option to make extra copies expendible. So the
extra copies are a request, if the space is availible make them, if
not complete the write, and log the event.
Are you asking for the
Hi Matt,
Interesting proposal. Has there been any consideration if free space being
reported for a ZFS filesystem would take into account the copies setting?
Example:
zfs create mypool/nonredundant_data
zfs create mypool/redundant_data
df -h /mypool/nonredundant_data
13 matches
Mail list logo
