Return-Path: Delivered-To: apmail-builds-archive@minotaur.apache.org Received: (qmail 72688 invoked from network); 12 Dec 2010 16:28:30 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 Dec 2010 16:28:30 -0000 Received: (qmail 52281 invoked by uid 500); 12 Dec 2010 16:28:30 -0000 Delivered-To: apmail-builds-archive@apache.org Received: (qmail 52145 invoked by uid 500); 12 Dec 2010 16:28:28 -0000 Mailing-List: contact builds-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: builds@apache.org Delivered-To: mailing list builds@apache.org Received: (qmail 52137 invoked by uid 99); 12 Dec 2010 16:28:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 12 Dec 2010 16:28:27 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 209.85.216.171 is neither permitted nor denied by domain of niklas@protocol7.com) Received: from [209.85.216.171] (HELO mail-qy0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 12 Dec 2010 16:28:19 +0000 Received: by qyk32 with SMTP id 32so2554305qyk.2 for ; Sun, 12 Dec 2010 08:27:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.246.136 with SMTP id ly8mr2799263qcb.237.1292171277739; Sun, 12 Dec 2010 08:27:57 -0800 (PST) Received: by 10.220.188.8 with HTTP; Sun, 12 Dec 2010 08:27:57 -0800 (PST) In-Reply-To: <4D03B4A3.4030601@apache.org> References: <4CF7EDF3.1030201@lehmi.de> <4D03B4A3.4030601@apache.org> Date: Sun, 12 Dec 2010 17:27:57 +0100 Message-ID: Subject: Re: No space left on device From: Niklas Gustavsson To: builds@apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Sat, Dec 11, 2010 at 6:28 PM, Andreas Lehmkuehler wrote: > I'm afraid the issue still exists. The maven build[1] crashed on solaris2 > while the ant build[2] on solaris1 worked like a charm. Got this today as well. Googled and it might be caused by fragmentation which should be possible to verify with fsck. But, fsck doesn't seem to be available on the zone. Gav, would you be able to help out? /niklas