From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Q9hSc-0001Ak-PC for garchives@archives.gentoo.org; Tue, 12 Apr 2011 17:33:06 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D9C141C042; Tue, 12 Apr 2011 17:31:32 +0000 (UTC) Received: from mail-pv0-f181.google.com (mail-pv0-f181.google.com [74.125.83.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 838151C042 for ; Tue, 12 Apr 2011 17:31:32 +0000 (UTC) Received: by pvg13 with SMTP id 13so3678427pvg.40 for ; Tue, 12 Apr 2011 10:31:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=may6uF3TK/vG27A9XsXhDg0SCE012v1q7/A2PM8tx1s=; b=JkMGPGdhp2ABmcjPQpPp81GCvetgRSHWzsmiBz+8xNK+vbnL0I//DXjGDiPQiH6Wjd D0coK4CeWKzwIqQmp+XoJX/Fs7c9h7GfNelPjm9Odxx1W3x33eVLPfsZu5vbBHsco+9z vxqkta4hg7wifYDlRRHPF3FJmzCPU9ogba9MU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=mYngcgucgOJx9A+R/R0wCQsR7I9NVyfoksdBUaG61Ec3EepvBKIOsc/g975e4aaV62 +6Y92E1CdtwXdwD9I7g6QpLW5LAEYoBvcUUwWtcXzc8Z8ZB5rCNuA3rmaspYp3fCTEYw Q+6AItKOVg7+4UAJiyHOPLLShFM8yTeUsesuE= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.143.21.31 with SMTP id y31mr1128870wfi.377.1302629491709; Tue, 12 Apr 2011 10:31:31 -0700 (PDT) Received: by 10.68.64.201 with HTTP; Tue, 12 Apr 2011 10:31:31 -0700 (PDT) Date: Tue, 12 Apr 2011 10:31:31 -0700 Message-ID: Subject: [gentoo-user] Can a forced volume check be interrupted? From: Grant To: Gentoo mailing list Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: X-Archives-Hash: 5fc8ee75b90405342bb066863669d183 Sometimes the ext3 forced volume check at boot triggers at an inopportune time. Is there a way to skip it and let it run at the next boot? - Grant