similar to: Ensuring that rsync doesn't try to write to an unmounted drive

Displaying 20 results from an estimated 1600 matches similar to: "Ensuring that rsync doesn't try to write to an unmounted drive"

2018 Sep 11
1
Ensuring that rsync doesn't try to write to an unmounted drive
On Tue, 2018-09-11 at 12:56 -0400, Kevin Korb via rsync wrote: > --timeout is about network connection timeouts. You aren't using the > network so it doesn't apply at all. Even if you were networking an > unmounted filesystem is an empty directory as far as rsync is > concerned > and rsync would treat it that way with no idea that you intended to > have > something
2018 Sep 11
0
Ensuring that rsync doesn't try to write to an unmounted drive
--timeout is about network connection timeouts. You aren't using the network so it doesn't apply at all. Even if you were networking an unmounted filesystem is an empty directory as far as rsync is concerned and rsync would treat it that way with no idea that you intended to have something mounted there. Now, I see at the top of your script you check for the existence of the target
2004 Apr 07
2
--suffix problem - possibly bug?
I'm having an issue with the --suffix and -b flags - I've tried the following commands: rsync -avbr --backup-dir=/rsyncbackup rsynctest user@server.com::module rsync -avbr --backup-dir=/rsyncbackup --suffix="" rsynctest user@server.com::module and either way, I wind up with a tilde as a suffix on all the files moved into the backup directory at time of synchronization.
2003 Jun 29
2
rsync/jscript/cygwin problem
I'm using a javascript program to execute rsync 2.5.6 compiled with cygwin on Windows XP Pro machines. These backup the user's "My Documents" folder to a Linux server running rsync 2.5.6 in daemon mode when the user logs in to XP and certain conditions are met (e.g. user hasn't backed up for a few days, user on the network etc). This works great except every now and then
2008 Aug 15
6
Rsync of LVM Snapshots copies whole file
Hello, anybody has a clue why this happens? The scenario: Each night I create LVM snapshot of my volume which contains some virtual disk images (VirtualBox VDIs). Then I rsync the content of one of the snapshot directories to a backup server. Each file size is between 1.3 GB and 6GB. I run the following commmand: sudo -u rsyncbackup rsync -avzP --exclude-from /home/rsyncbackup/excludefile -e
2008 Jul 12
1
DO NOT REPLY [Bug 4621] "-p" option to simulate "mkdir -p" for rsync
https://bugzilla.samba.org/show_bug.cgi?id=4621 tkessler@ucdavis.edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tkessler@ucdavis.edu ------- Comment #2 from tkessler@ucdavis.edu 2008-07-12 12:01 CST ------- This would be an EXCEPTIONALLY useful
2001 Sep 23
2
destination dir doubles in size
I am using Rsync to mirror my primary drive to a mounted second drive. I am using a crontab to control it: 30 3 * * * /usr/bin/rsync -rpogl /* /mnt/backup2/systemBackup/ The first run seems fine. But the subsequent running seems to double the original directory size. I notice this by running df -k. The destination size increases two fold, as if each time Rsync runs, it repeats itself, rather
2005 Jan 29
1
rsync-ing on MacOS X.
Hi all, I'm setting up a backup script for my Mac, and I'm wondering about the rsync ability of dealing with HFS+ filesystem (resource-fork and such...). I've searched the mailing list archive for this topic and I've found some thread regarding it, but it's not clear to me what is the actual situation. Is the HFS+ officially supported? Will it be in the near future?
2002 Oct 11
2
mount_smbfs can't get server address
i am running freebsd 4.6.2 i am using this command to mount a windows share from windows xp mount_smbfs //user@server/share_name /path/to/mount_point and everytime i get this message mount_smbfs: can't get server address: ssyerr = operation timed out i have also tried this command mount -t smbfs //user@server/share_name /path/to/mount_point and get the same message can any one give me some
2003 Jan 09
2
Help With Restoring
Hi All, I have been using rsync to backup to a central server with a 7 day incremental script on 2 Redhat boxen. #!/bin/sh PATH=/usr/local/bin:/usr/bin:/bin DAY=`date +%A` export PATH DAY [ -d /root/emptydir ] || mkdir /root/emptydir rsync --rsh=/usr/bin/ssh --delete -a /root/emptydir/ CENTRAL_SERVER_IP:/backup2/BACKED_UP_SERVER_FQDN/$DAY rmdir /root/emptydir rsync --delete
2009 Jul 03
1
Bug? backup_dir sometimes reported on STDOUT, sometimes not.
Running rsync 3.0.6 on OS X 10.5.7 (on a MacBook Pro) and using the -b flag (and -v --verbose), the "backup_dir" is reported in the output, but sometimes on STDOUT and sometimes somewhere else. Note that the rsync daemon running on the "server" is 2.6.9 (on another MacBook Pro, OS X 10.5.7) For example, in bash, this happens: axe-MBP:bin work$ /usr/local/bin/rsync
2015 Jan 16
3
wrong transfer of app packages using --backup
Dear All, I have been seeing some strange behavior using rsync 3.1.1 on OSX with the 3 standard patches applied when using the --backup and --backup-Dir options. This works as expected on 3.0.9, moving any files on dest that are not on source to the backup folder. If no changes then the backup folder is not even created. -aHAXN --fileflags --force-change --protect-decmpfs ?delete --backup
2013 Jan 24
2
rsync parameters errors
In my new bash script, I'm doing what I think is a very simple rsync command the way I'm used to doing it. I just do a lot of setup and checking before I get to it. When I run it, it gets very unhappy with me. It's probably something very simple. I need to build the rsync command in a string so that some things can go away - like if my variables DRY_RUN and DELETE are undefined,
2003 Jul 29
1
"-b --suffix '' --delete --backup-dir /path/" combination does not act as expected
Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.samba.org/archive/rsync/attachments/20030728/49616c2f/attachment.bin
2005 Dec 07
2
incremental backup help required
Hi, This is my rsync command /usr/bin/rsync --compress \ --verbose \ --rsh=ssh \ --times \ --owner \ --group \ --ignore-times \ --links \ --perms \ --recursive \ --size-only \
2011 May 23
5
Integration branch pushed out to btrfs-unstable
Hi everyone, I''ve pushed out my current kernel git tree to a new branch called integration-test. This is meant for integration testing only and should not be run by anyone who doesn''t love crashes. I''ve pulled together a lot of important work from a lot of different people. It includes: The new inode number allocator Delayed inode and directory item updates Scrub,
2015 Nov 09
2
CentOS6: missing kernel module?
Testing out tipc for cluster development, and running into an immediate snag. tipcutils was found in EPEL but despite having a "compatible" kernel, it doesn't seem to actually work. It's a completely updated system, Intel i5 with 16 GB of RAM, nothing remarkable. Any ideas? [root at backup2 ~]# tipc-config -netid=1234 -a=1.1.1 -be=eth:eth0 TIPC module not installed
2002 Apr 02
2
Handling of backup files - two new features proposed
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear list members, there are two new rsync-features I made up and would like to discuss with you. If you think these new features might be useful for the whole rsync-community, please give me a note and I'll send you the patches (or post them here). 1.) Setting owner and/or group of backup files. In our servers I'm using rsync to backup
2006 Jan 03
2
Incremental help
hi all i'm playing with rsync to make a good incremental backup on Mac OS X and FreeBSD i use this with the --delete-excluded option to get a fresh copy with only modified files but today i ave a new thing: i would like to get a backup folder with all modified files on it, not the full backup, only modified files i'll tried -b --backup-dir but isn't working can any help me
2001 Oct 21
1
backup_dir problem
I am having a problem using the backup_dir option of rsync. The command being used is basically rsync --archive --delete --backup --backup_dir=PathToBackup/save user@fromsystem:FilePath/ PathToBackup/ The feature that is unique to this problem is that the "save" directory is under the path where the files are being backed up. Fortunately, rsync is clever enough to not delete