Date: Sat, 12 Jan 2013 19:58:18 +0000 From: "Simon L. B. Nielsen" <simon@FreeBSD.org> To: John Marshall <john.marshall@riverwillow.com.au> Cc: freebsd-hubs@freebsd.org Subject: Re: SLOW rsync from bit0.us-west Message-ID: <CAC8HS2EBKhS2t8hpGZnmwzh06fKAd1d69fdHz7VU=CxZDk=iEg@mail.gmail.com> In-Reply-To: <CAC8HS2E8KB67U_m_gWznXMZNHRCZNB%2BNe_u5BGsCnrh%2BiYxAHg@mail.gmail.com> References: <50F0F2CE.9050605@riverwillow.com.au> <CAC8HS2E8KB67U_m_gWznXMZNHRCZNB%2BNe_u5BGsCnrh%2BiYxAHg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12 January 2013 15:37, Simon L. B. Nielsen <simon@freebsd.org> wrote: > On 12 January 2013 05:21, John Marshall > <john.marshall@riverwillow.com.au> wrote: >> I have been updating the gnats collection on our mirror via rsync since >> the CVSup updates stopped but noticed this morning that the updates >> appeared to be stalled. I killed off jobs that appeared to be stuck >> downloading incremental file list (after about 20 minutes) but then >> thought to run rsync manually with -vvv. What I saw then was short >> bursts of messages like 'recv_file_name(bin/nnnn)' interspersed with >> 15-20 seconds of nothing. tcpdump showed just a handful of packets every >> 15 seconds or so. The update eventually finished after more than 2 hours. > > The server which runs bit0.us-west (which is also svn0.us-west), is > totally bogged down. > > CPU: 3.1% user, 0.0% nice, 96.0% system, 0.0% interrupt, 1.0% idle > > As it has just been updated to the latest stable/9 I'm a bit > suspicious of that... > > Thanks for letting us know. I will start poking people. Please have another look and see if things aren't better now. It looks like we are stressing nullfs more than people had before - at least with way more vnode / files so the server was spending all of its time doing vnode lookups. -- Simon L. B. Nielsen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAC8HS2EBKhS2t8hpGZnmwzh06fKAd1d69fdHz7VU=CxZDk=iEg>