www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin A. McGrail (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-9754) Rsync between spamassassin-vm.apache.org and spamassassin2.zones.apache.org is SLOOOW
Date Mon, 01 Jun 2015 20:05:18 GMT

    [ https://issues.apache.org/jira/browse/INFRA-9754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567914#comment-14567914

Kevin A. McGrail commented on INFRA-9754:

I believe the issue might have been caused by the diskspace issue.  I thought we had 160GB
free but likely lots of small files took all the disk space is my guess. After clearing a
small amount of space, things seem much better already.

> Rsync between spamassassin-vm.apache.org and spamassassin2.zones.apache.org is SLOOOW
> -------------------------------------------------------------------------------------
>                 Key: INFRA-9754
>                 URL: https://issues.apache.org/jira/browse/INFRA-9754
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: Kevin A. McGrail
> Every two hours from cron on spamassassin-vm, the script /export/home/svn-trunk/build/automc/rsync_to_spamassassin2
is run.
> In checking cron logs, I see this on 5/27:
> rsync: write failed on "/export/home/corpus-rsync/corpus/ham-bb-jhardin.log~": No space
left on device (28)
> Checking df, looks odd showing a 535G partition with 362G used representing 100%:
> Anyway, sometime around the May 27th, I think is when the issue started.
> I've rebooted spamassassin2.zones.apache.org on 6/1.
> I'm trying to figure out what's taking diskspace but the server is very slow even on
ls requests for /export/home.
> I'll try and clear some space if I can figure out something to delete but if someone
can look at odyne and see if it's running ok, the zonestorage *might* be problematic.
> 535G   362G   864K   100%    /zonestorage/spamassassin2

This message was sent by Atlassian JIRA

View raw message