On 2020-07-06 12:40 -0700 Perry Hutchison wrote:
> we either need to read the part of the output file that
> we're about to seek over -- and overwrite anything that reads back
> non-zero with zeros
The files that give verification errors are just small text files
with no null bytes. The sparse co
Getting some puzzling errors doing the following backup procedure on a
root filesystem that's on LVM, when using sparse flag:
lvcreate --snapshot --name baksnap --size 3G /dev/vg0/root
mount -o ro /dev/vg0/baksnap /var/tmp/snapmnt
rsync -izaHx \
--delete --delete-excluded --delete-after \
ries to look at.
if you're going to do that, just automate it:
http://code.google.com/p/lsyncd/
--
Scott Mcdermott | Omnisys Technologies | --=! sc...@omnisys.com !=--
415-730-5477|www.omnisys.com | UNIX Sysadmin & Netadmin
--
Please use reply-all for most replies
DALJIT TAMANA, BLOOMBERG/ LONDON on 2011/05/27 -0400 @08:19:36:
> I'm getting the following error occasional and can't
> find out why; rsync: write failed on
> "/dbtmp.new/file.dmp": File too large (27) rsync
rsync --version output please
--
Please use reply-all for most replies to avoid omitting
I have rsync 3.0.8 on both ends, over ssh, which on
remote server appears to be hung in select():
Process has fd 0, 1, 2, and all are unix sockets
it's just hung, keeps timing out every 60 seconds then calls
select again
it's been hung for 15 hours
flags on the remote are:
--server --sender
Dave Dykstra on Thu 16/01 14:57 -0600:
> > > The patch from 2-1/2 years ago for changing copy-unsafe-links to
> > > follow unsafe links on the destination side also included
> > > essentially this patch.
> >
> > just to be clear, without using copy-unsafe-links, rsync still
> > copies absolute sym
Dave Dykstra on Thu 16/01 14:33 -0600:
> The patch from 2-1/2 years ago for changing copy-unsafe-links to follow
> unsafe links on the destination side also included essentially this patch.
just to be clear, without using copy-unsafe-links, rsync still copies
absolute symlinks which point out of t
Seth Olsen on Thu 2/01 15:02 -0800:
> I'm a bit confused about what the '--copy-unsafe-links' option
> considers the 'source tree'. In the man page it says that for links
> pointing outside the 'source tree' the file will be copied,
I think it means, any link that points to a location whose par
Eckebrecht von Pappenheim on Thu 26/10 10:06 +0200:
> Back to your question: How can I tell, if it's compiled with USE_PIPES?
[~] $ nm `type -p ssh` | grep pipe
U pipe@@GLIBC_2.0
Neil Schellenberger on Tue 17/10 23:55 -0400:
> In particular, is anyone who is using --timeout=0 (the default) on the
> server nonetheless seeing unexpected EOF?
It's been a while, but to my recollection, yes, I didn't (never have)
set any timeout values, but I still got this error at seemingly
10 matches
Mail list logo
