https://bugzilla.samba.org/show_bug.cgi?id=3099
--- Comment #8 from Chip Schweiss c...@innovates.com ---
I would argue that optionally all directory scanning should be made parallel.
Modern file systems perform best when request queues are kept full. The
current mode of rsync scanning
I dont understand - scanning metadata is sped up by thrashing the head
all over the disk instead of mostly-sequentially scanning through?
How does that work out?
/kc
On Fri, Jul 17, 2015 at 02:37:21PM +, samba-b...@samba.org said:
https://bugzilla.samba.org/show_bug.cgi?id=3099
---
https://bugzilla.samba.org/show_bug.cgi?id=3099
--- Comment #7 from Rainer rai...@voigt-home.net ---
Hi,
I'm experiencing the very same problem: I'm trying to sync a set of VMWare disk
files (about 2.5TB) with not too many changes, and direct copying is still
faster than the checksumming by a
Sounds to me like maintaining the metadata cache is important - and tuning the
filesystem to do so would be more beneficial than caching writes, especially
with a backup target where a write already written will likely never be read
again (and isnt a big deal if it is since so few files are
Hi TG,
You can keep an up-to-date copy of the files/folders/pipes/etc. in the
100GB space using rsync, but not a true clone of the partition.
To get a true clone of the boot partition, you'd need to boot from a
rescue CD, mount the other machine's 100GB space and dd the boot
partition device
Thierry Granier th.gran...@free.fr wrote:
i have a machine A with 2 disks 1 et 2 running Debian Jessie
on 1 is the system and the boot and the swap
on 2 different partitions like /home /opt ETC.
i have a machine B with 1 disk running kali-linux and 100G free
Can i clone the disk 1 of
Hello
i have a machine A with 2 disks 1 et 2 running Debian Jessie
on 1 is the system and the boot and the swap
on 2 different partitions like /home /opt ETC.
i have a machine B with 1 disk running kali-linux and *100G free*
Can i clone the disk 1 of machine A on the 100G free on machine B
Ken, this just happens to be a special case where your configuration has a
huge number of spindles. If you have multiple threads reading the same
spindle you'll just be thrashing the heads back forth. If there is one
thread reading at the front of the disk and another thread reading at the
end
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is good info for backing up the MBR (which includes the partition
table).
However, if you are going to image a partition use either ddrescue
(does the same thing but has a status screen, can resume, and works
around read errors) or partimage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would add --numeric-ids and --itemize-changes. Up to you if you
need --xattrs or --acls.
Also, I prefer to do backups by filesystem so I would add
- --one-file-system and run one rsync per filesystem. This means you
don't have to exclude things
10 matches
Mail list logo
