From: Bryan Whitehead <driver@megahappy.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] rsync problems
Date: Tue, 30 Aug 2005 23:58:56 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0508302358330.28208@beavis.megahappy.net> (raw)
In-Reply-To: <1125429899.32498.1.camel@localhost>
Sounds like bad memory.
Run memtest86?
On Tue, 30 Aug 2005, Joshua Armstrong wrote:
> They are syncing from the same mirror. I haven't tried changing mirrors
> though. If it helps, when I read the kernel logs I notice that during
> the time it's syncing, I see a lot of readlink() failed: I/O error for
> files in /usr/portage. I've run fsck on the disk and it detects no
> errors. All other apps can read all the files in /usr/portage without a
> problem.
>
> Thanks for all your help!
>
> On Tue, 2005-08-30 at 21:02 +0200, Holly Bostick wrote:
>> Joshua Armstrong schreef:
>>> Hello, I'm having a problem with rsync on one of my servers. Every time
>>> I rsync from one of the gentoo portage mirrors, it tells me rsync error:
>>> some files could not be transferred (code 23) at main.c(1064). I've
>>> tried re-emerging rsync and re-emerging portage but to no avail. I know
>>> it isn't a firewall/routing issue because all my other Gentoo boxen can
>>> sync without a problem. Thanks!
>>>
>>
>> Are the other boxes that aren't having the problem syncing with the same
>> server as the box that is having the problem?
>>
>> Have you tried changing the mirror that the box with the problem is
>> syncing with?
>>
>> Holly
>
--
Bryan Whitehead
Email:driver@megahappy.net
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-08-31 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 19:05 [gentoo-user] rsync problems Joshua Armstrong
2005-08-30 19:02 ` Holly Bostick
2005-08-30 19:24 ` Joshua Armstrong
2005-08-31 6:58 ` Bryan Whitehead [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0508302358330.28208@beavis.megahappy.net \
--to=driver@megahappy.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox