Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 515CB1018E for ; Wed, 10 Dec 2014 22:47:34 +0000 (UTC) Received: (qmail 33408 invoked by uid 500); 10 Dec 2014 22:47:33 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 33376 invoked by uid 500); 10 Dec 2014 22:47:33 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 33361 invoked by uid 99); 10 Dec 2014 22:47:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2014 22:47:32 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of mohsinchandia@gmail.com does not designate 162.253.133.43 as permitted sender) Received: from [162.253.133.43] (HELO mwork.nabble.com) (162.253.133.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2014 22:47:27 +0000 Received: from msam.nabble.com (unknown [162.253.133.85]) by mwork.nabble.com (Postfix) with ESMTP id C86B3D49494 for ; Wed, 10 Dec 2014 14:47:06 -0800 (PST) Date: Wed, 10 Dec 2014 15:47:06 -0700 (MST) From: Mohsin To: users@subversion.apache.org Message-ID: <1418251626222-191208.post@n5.nabble.com> In-Reply-To: <5488BB92.90500@wandisco.com> References: <1418245277325-191202.post@n5.nabble.com> <5488BB92.90500@wandisco.com> Subject: Re: SVN Issue On Solaris OS MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org >This really shouldn't matter, unless you now have a directory with tens >of thousands of entries in it. And your use of the term "100% disk >usage" seems to be about I/O, not capacity (which is quite strange). On >the other hand, if you're actually rsyncing lots of data to or from your >machine, it's not surprising that you use up all available disk >bandwidth. But I still don't know how Subversion would be related to rsync. We have 900 GB total space on server in which half of the space is free on server. We have 430 GB data in all repos so by r syncing all disk bandwidth of server is being consumed that caused 100 % disk usage.That the point which i understand. Mohsin -- View this message in context: http://subversion.1072662.n5.nabble.com/SVN-Issue-On-Solaris-OS-tp191202p191208.html Sent from the Subversion Users mailing list archive at Nabble.com.