On 07/13/2018 11:38 PM, Nathan Hunsperger wrote:
On 7/13/18 5:55 PM, Jim Conger wrote:
Use rsync with all the right options to copy pretty much every detail,
see man page for rsync, but "rsync -a --stats /mnt/hd/.
/mnt/NEWDRIVE/." should do it. Note the trailing /. on the paths, that
makes sure
On Fri, 13 Jul 2018, Jim Conger wrote:
> I have had some odd problems with corruption in ext4 file systems with
> vaults in them, so I fsck the vault file system after every backup. I
> think I read something about ext4 and hard links being a problem which
> would be bad news for dirvish since it
On Fri, 13 Jul 2018, Nathan Hunsperger wrote:
> So, the full command I would use is "sudo rsync -aSHAX -v --stats
> /mnt/olddrive/ /mnt/newdrive". The trailing slash on olddrive is required,
> and will result in the root of the new drive having the same attributes as
> the old drive.
Nathan,
On Sat, 14 Jul 2018, Jim Conger wrote:
> One more place to check is the master.conf file. If there are any
> rsync-options there that you need for your set up, you may need want them
> on the duplicate the backup drive rsync. I checked mine, and I don't have
> any. I did experiment with -c (checks
On 07/14/2018 08:46 AM, Rich Shepard wrote:
Very interesting. I've not needed to learn about inodes before. Thank you.
Wiki has a good summary of the inode,
https://en.wikipedia.org/wiki/Inode. Every file is has an inode. The
inode is the head of the file, it has all the meta data that is not p
On Sat, 14 Jul 2018, Jim Conger wrote:
> What dirvish truly beats the snot out of is the directory storage. Say you
> are keeping 30 days of snapshots. If a file hasn't changed in those 30
> days, it is stored once using one inode -- but it is in 30 directories. If
> you are investigating file sys
