From: Andrea Gelmini <andrea.gelmini@gelma.net>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Linux-next regression?
Date: Tue, 27 Nov 2018 15:11:44 +0100 [thread overview]
Message-ID: <20181127141144.GA23269@glet> (raw)
In-Reply-To: <845890af-0659-fbfa-c445-d6f109bd5015@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
On Tue, Nov 27, 2018 at 09:13:02AM +0800, Qu Wenruo wrote:
>
>
> On 2018/11/26 下午11:01, Andrea Gelmini wrote:
> > One question: I can completely trust the ok return status of scrub? I know is made for this, but shit happens...
>
> No, scrub only checks csum of data and tree blocks, it doesn't ensure
> the content of tree blocks are OK.
Hi Qu,
and thanks a lot, really. Your answers are always the best: short,
detailed and very kind. You rock.
I'm going to send a patch to propose to add your explanation above
on the relative man page, if you agree.
> For comprehensive check, go "btrfs check --readonly".
I'll do it.
At the moment I just compared the file existance between my laptop and
latest backup. Everything is fine.
>
> However I don't think it's something "btrfs check --readonly" would
> report, but some strange behavior, maybe from LVM or cryptsetup.
Well, I'm using this setup with ext4 and xfs, on same machine, without
troubles.
I've got files checksummed on the backup machine, so I can be sure about
comparing integrity.
Anyway, thanks a lot again,
Andrea
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2018-11-27 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 15:01 Linux-next regression? Andrea Gelmini
2018-11-27 1:13 ` Qu Wenruo
2018-11-27 14:11 ` Andrea Gelmini [this message]
2018-11-27 14:16 ` Qu Wenruo
2018-11-28 16:05 ` Andrea Gelmini
2018-12-04 22:29 ` Chris Mason
2018-12-05 10:59 ` Andrea Gelmini
2018-12-05 19:32 ` Chris Mason
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=20181127141144.GA23269@glet \
--to=andrea.gelmini@gelma.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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;
as well as URLs for NNTP newsgroup(s).