We have a particular file system that we're trying to keep in sync
between two FreeBSD/ZFS servers using Rsync.
The file system has many millions of files, and about 4TB of data
total. Rsync takes HOURS to run, even when there are no files to
transfer. Just the comparison itself takes hours.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you are using zfs then why not use zfs send and zfs receive?
Rsync has to stat every file on both ends which can take a long time
with millions of files. The zfs tools don't have to do any of that.
On 11/30/12 12:33, Tim Gustafson wrote:
We
If you are using zfs then why not use zfs send and zfs receive?
Rsync has to stat every file on both ends which can take a long time
with millions of files. The zfs tools don't have to do any of that.
Because zfs send/receive doesn't work well if the target file system ever
gets changed,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You are missing the snapshot part of it. You send/receive a snapshot
then both ends have the same snapshot.
On 11/30/12 13:00, Tim Gustafson wrote:
If you are using zfs then why not use zfs send and zfs receive?
Rsync has to stat every file on
Tim Gustafson wrote:
Because zfs send/receive doesn't work well if the target file system ever
gets changed, even for something like an atime.** Basically, the file
system can't be touched on the remote end, and you can't even set the
read-only property, because that would be a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, I am only using zfs as storage for rsync backups of non-zfs
systems so I might be wrong.
However, I was under the impression that you could send a zfs fs to
another system then send subsequent snapshots of it as well.
On 11/30/12 13:17, Kyle
zfs send receive should work perfectly for this.
If the destination has changes you don't mind loosing e.g. just permission
changes you can have the receive roll back to the last known source snapshot
before replaying changes. The result being two identical copies of everything.
If there are
