From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id BC8271381FA for ; Sat, 17 May 2014 07:53:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CA3B2E0BB4; Sat, 17 May 2014 07:53:18 +0000 (UTC) Received: from mail-we0-f173.google.com (mail-we0-f173.google.com [74.125.82.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9F998E0B54 for ; Sat, 17 May 2014 07:53:17 +0000 (UTC) Received: by mail-we0-f173.google.com with SMTP id u57so3464862wes.18 for ; Sat, 17 May 2014 00:53:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=4ejj6C7ZWxACHJP849uwoiXabIbMSKscjOoxkkaUsfM=; b=lXM1cYRrwRPBmSD+e7XwAkwKdittHXL1V9ta9Nt8zaD6ojDwtN6urDyHyKl55E1AFk /ddLQsVNo0zLCeZL2w11jDSDlkR4sYyuNx+72FNdY/zqWKY0ea3gVM0aaDcN+SCiF1No npwr91b+Bo1zjnk/0cDVSG83iWgFiKlKJJJbHhyjrGUHG2P1LXmcqX439uGOX+RvBsFF 37xeQDRhlZ4/FvCO+BwOS4vVdS2v2UhBpBrX0/suxcIPos+Mn5vEq+R58UfsN+SaYidb FeKs0LocCd2O6Jw3RCkmLv50vSkgLqKiUkLHHwjbTyBfVhX9skLRXZJ+0U76pJXEgl9a ktLw== X-Received: by 10.180.89.1 with SMTP id bk1mr2054821wib.35.1400313196518; Sat, 17 May 2014 00:53:16 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPSA id l5sm4966137wja.12.2014.05.17.00.53.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 17 May 2014 00:53:15 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] experience thus far Date: Sat, 17 May 2014 08:53:11 +0100 User-Agent: KMail/1.13.7 (Linux/3.12.13-gentoo; KDE/4.12.5; x86_64; ; ) References: <20140506121832.678ae781@marcec> <5376A871.7010609@iinet.net.au> <5376D14B.9010306@iinet.net.au> In-Reply-To: <5376D14B.9010306@iinet.net.au> 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="nextPart200048189.NKi8sjfNP4"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201405170853.12888.michaelkintzios@gmail.com> X-Archives-Salt: 9a3d9f51-1e80-49a9-9a93-53087df868cf X-Archives-Hash: 003654edc953304156bf500b5c808caf --nextPart200048189.NKi8sjfNP4 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Saturday 17 May 2014 04:02:35 William Kenworthy wrote: > On 17/05/14 08:08, William Kenworthy wrote: > > On 17/05/14 04:15, Marc Joliet wrote: > >> So, a week has passed since my conversion to btrfs. > > > >... > > > >> Have a nice weekend, > >=20 > > Don't forget to have a maintenance program - run a scrub regularly once > > a week or so - I have enough btrfs drives (22 qemu files, 4 WD Greens > > att) to see about one or two scrub fixable errors a week with no obvious > > cause, sometimes serious (in a critical file). My experience is that if > > you ignore these errors they seem to increase over time resulting in a > > crash and burn. Keep an eye on your logs as btrfs will list the errors > > there as well ("grep -i btrfs /var/log/messages"). For the ones scrub > > cant fix, delete the file and restore from backup. Errors that require > > off-line fixing (btrfsck) are the ones where I have lost file systems - > > though I have not seen this in the last 6 months. > >=20 > > I am quite practised in restoring from backups because of btrfs :) > >=20 > > BillK >=20 > This is from this mornings grep of the log: > May 15 07:00:34 myth kernel: btrfs: checksum error at logical 1775247360 > on dev /dev/vda3, sector 5580816, root 5, inode 6423718, offset 1839104, > length 4096, links 1 (path: > var/log/mythtv/old/mythbackend.20140421061150.6275.log-20140515) > May 15 07:00:34 myth kernel: btrfs: bdev /dev/vda3 errs: wr 0, rd 0, > flush 0, corrupt 1, gen 0 > May 15 07:00:34 myth kernel: btrfs: unable to fixup (regular) error at > logical 1775247360 on dev /dev/vda3 > May 15 07:41:40 myth kernel: btrfs: bdev /dev/vda3 errs: wr 0, rd 0, > flush 0, corrupt 1, gen 0 >=20 > and >=20 > May 16 20:40:33 moriah kernel: btrfs: bdev /dev/mapper/vg1-backups errs: > wr 0, rd 250, flush 0, corrupt 13, gen 0 Thank you all for sharing your experiences with btrfs. It looks like it wi= ll=20 be come the fs of choice in the future. I am not clear on one thing: is the corruption that you show above *becaus= e*=20 of btrfs, or it would occur silently with any other fs, like e.g. ext4? =2D-=20 Regards, Mick --nextPart200048189.NKi8sjfNP4 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAABCAAGBQJTdxVoAAoJELAdA+zwE4Yec2EIAIhNzfpdFWO97TCiSAsWZ1kt lv80UViHGmBhQxsobrkpZQerEg3HHhiIsM42G5oQ9oplWTJcip+8eaa3woI67xhg MWNUDDVzaDRVXbmG17I1XMaNd9Rf11ggjzRgNRunBnw/I2EVPr8xt7EdguVJM6xP aKCYf6vOvJDaqueNqLCTgqrHwwRunv2es2s/V/eappNu5xXtQNALydjljSLU4r4w ONU26KGt55hR93Kqxt/TBravHN7NsiQ+iDlEQThej/JzQmRmmT95QYQdZDiX5+/R gFlrq961cu4XJmW9JcceRZcCI1eWcTIyE9mBg/aSQegxePZKGIjkmYzgTXXJ1RY= =xEfp -----END PGP SIGNATURE----- --nextPart200048189.NKi8sjfNP4--