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 1Q9tH4-00042B-K9 for garchives@archives.gentoo.org; Wed, 13 Apr 2011 06:09:58 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E8D4B1C02C; Wed, 13 Apr 2011 06:08:21 +0000 (UTC) Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 96FBA1C02C for ; Wed, 13 Apr 2011 06:08:21 +0000 (UTC) Received: by wwj40 with SMTP id 40so280289wwj.10 for ; Tue, 12 Apr 2011 23:08:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:reply-to:to:subject:date:user-agent :references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=65PV07t4FK+btISJbcudT6bJf8JKpf/AQIByz6a+6r4=; b=vFAZXRQuT89Tdqt6GmeE3VkYHfCQxg5AD3Hky1f6o54xbQDDg5UcqvgJpgMXsFbY3D oC5p6zAoC8oVOnRHTOWZCV/XJC0EWufdDSxEKRyJG/5xtHWPwAhBO74iZqq6P0cXYc++ YN0WorrvKeTsItVenQv9uwKoedMiVJVchfcb0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=bZEggU9YSJI6Tvgx0CywcLD1zVTleJnVSCI1jUK7+m71w4HUo8Yf55073WE/Dfx2RY DpBnBYAGYWv88SWVjevzZmUmvVUC76iPc7K6Qo9mKtxlcBoQTF+gXSSD46oVjlEulRRF c1S/EYl5zoGr73Bmfq++CF6L8HVnA7dku1rNw= Received: by 10.216.230.153 with SMTP id j25mr4944170weq.22.1302674900794; Tue, 12 Apr 2011 23:08:20 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id e13sm109184wbi.40.2011.04.12.23.08.18 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2011 23:08:18 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can a forced volume check be interrupted? Date: Wed, 13 Apr 2011 07:08:37 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.36-gentoo-r8; KDE/4.4.5; x86_64; ; ) References: <1302655543.3973.12.camel@troll> In-Reply-To: <1302655543.3973.12.camel@troll> 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 Content-Type: multipart/signed; boundary="nextPart1647235.kpyZU3vGhH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201104130708.47315.michaelkintzios@gmail.com> X-Archives-Salt: X-Archives-Hash: fe049d6096453360d3a2b68f9971033f --nextPart1647235.kpyZU3vGhH Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Wednesday 13 April 2011 01:45:43 Bill Kenworthy wrote: > On Tue, 2011-04-12 at 14:52 -0500, Paul Hartman wrote: > > On Tue, Apr 12, 2011 at 12:31 PM, Grant wrote: > > > 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? > >=20 > > Not once it has started, but there are some ways to avoid it running > > in the first place: > >=20 > > Add "fastboot" to your kernel commandline to make it bypass the > > auto-fsck. A grub entry for "skip fsck" might be handy. > >=20 > > Edit /etc/fstab to prevent the auto-fsck from ever running by changing > > the last field to 0. > >=20 > > If it's an ext[123] you can use tune2fs -i 0 to set the auto-check > > interval to never. >=20 > Thats one reason I have been looking at btrfs - online fsck. Has been > solid even on unexpected crashes (I am setting up remote power on/off > and pressed the wrong button - more than once :) I actually had some > minor corruption on reiserfs, but btrfs was fine and could be checked > online anyway in a lot less time than reiserfsck took. ext4 takes only a second if not less at boot time - depending on the size o= f=20 the partition of course. =2D-=20 Regards, Mick --nextPart1647235.kpyZU3vGhH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEABECAAYFAk2lPe8ACgkQVTDTR3kpaLbeSgCglg9Isi7sVpo5GqOsGeo5NTMu bPgAnivuKHfGN5UVnrYcsNXWnOO0G9uG =NANl -----END PGP SIGNATURE----- --nextPart1647235.kpyZU3vGhH--