From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] BTRFS problem? [WAS Quick check on net-print/hplip-3.14.10]
Date: Fri, 18 Sep 2015 14:15:50 -0400 [thread overview]
Message-ID: <CAGfcS_mDj0xynrHicB_LP5U2HMCoqpg4UorEQZB2tsA6nsuKRw@mail.gmail.com> (raw)
In-Reply-To: <201509181857.00834.michaelkintzios@gmail.com>
On Fri, Sep 18, 2015 at 1:56 PM, Mick <michaelkintzios@gmail.com> wrote:
> On Friday 18 Sep 2015 17:16:54 Marc Joliet wrote:
>> On Friday 18 September 2015 10:31:01 Mick wrote:
>> >A couple of months ago the akonadi DB went sideways and kmail played up as
>> >a result. Again I was suspicious of btrfs, but neither the logs nor fsck
>> >showed up anything.
>>
>> I take it "btrfs scrub" didn't turn up anything, or is that what you meant
>> by fsck?
>
> Am I supposed to run scrub with I do not have a RAID running? I thought scrub
> was meant for comparing checksums between mirrored fs - have I got this wrong?
>
You can actually run scrub on a non-raid btrfs setup. Btrfs will
report any errors that it detects (using the checksumming in the
filesystem), but it would not be able to fix errors unless you have it
storing redundant data somewhere (even on non-raid it still stores
redundant metadata by default, and you can choose to do this with data
as well which protects against block-level failures but not disk-level
failures, obviously).
However, you'd have gotten the same errors in dmesg just trying to
read the files - btrfs checks the checksum on all file read
operations. That is a big part of the value of both btrfs and zfs.
--
Rich
next prev parent reply other threads:[~2015-09-18 18:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 21:22 [gentoo-user] Quick check on net-print/hplip-3.14.10 Mick
2015-09-16 22:43 ` Dale
2015-09-17 5:52 ` Mick
2015-09-17 7:12 ` Dale
2015-09-17 17:36 ` Mick
2015-09-17 19:25 ` Alan McKinnon
2015-09-17 22:26 ` Mick
2015-09-17 22:33 ` Alan McKinnon
2015-09-18 9:31 ` Mick
2015-09-18 16:16 ` Marc Joliet
2015-09-18 17:56 ` [gentoo-user] BTRFS problem? [WAS Quick check on net-print/hplip-3.14.10] Mick
2015-09-18 18:15 ` Rich Freeman [this message]
2015-09-18 18:19 ` Mick
2015-09-18 18:30 ` Rich Freeman
2015-09-18 21:58 ` Mick
2015-09-19 20:14 ` Stefan G. Weichinger
2015-09-19 20:24 ` Mick
2015-09-20 5:25 ` J. Roeleveld
2015-09-17 0:45 ` [gentoo-user] Re: Quick check on net-print/hplip-3.14.10 walt
2015-09-17 6:03 ` Mick
2015-09-17 1:11 ` [gentoo-user] " wabenbau
2015-09-17 6:06 ` Mick
2015-09-17 20:28 ` [gentoo-user] " james
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGfcS_mDj0xynrHicB_LP5U2HMCoqpg4UorEQZB2tsA6nsuKRw@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox