From: Roman Mamedov <rm@romanrm.net>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: when btrfs scrub reports errors and btrfs check --repair does not
Date: Sun, 13 Nov 2016 20:13:29 +0500 [thread overview]
Message-ID: <20161113201329.1851b992@natsu> (raw)
In-Reply-To: <20161113150629.qiz3r6no3snrufuu@merlins.org>
On Sun, 13 Nov 2016 07:06:30 -0800
Marc MERLIN <marc@merlins.org> wrote:
> So first:
> a) find -inum returns some inodes that don't match
> b) but argh, multiple files (very different) have the same inode number, so finding
> files by inode number after scrub flagged an inode bad, isn't going to work :(
I wonder why do you even need scrub to verify file readability. Just try
reading all files by using e.g. "cfv -Crr", the read errors produced will
point you directly to files which are unreadable, without the need to lookup
them in a backward way via inum. Then just restore those from backups.
--
With respect,
Roman
next prev parent reply other threads:[~2016-11-13 15:13 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 2:16 Buffer I/O error on dev md5, logical block 7073536, async page read Marc MERLIN
2016-10-30 9:33 ` Andreas Klauer
2016-10-30 15:38 ` Marc MERLIN
2016-10-30 16:19 ` Andreas Klauer
2016-10-30 16:34 ` Phil Turmel
2016-10-30 17:12 ` clearing blocks wrongfully marked as bad if --update=no-bbl can't be used? Marc MERLIN
2016-10-30 17:16 ` Marc MERLIN
2016-11-04 18:18 ` Marc MERLIN
2016-11-04 18:22 ` Phil Turmel
2016-11-04 18:50 ` Marc MERLIN
2016-11-04 18:59 ` Roman Mamedov
2016-11-04 19:31 ` Roman Mamedov
2016-11-04 20:02 ` Marc MERLIN
2016-11-04 19:51 ` Marc MERLIN
2016-11-07 0:16 ` NeilBrown
2016-11-07 1:13 ` Marc MERLIN
2016-11-07 3:36 ` Phil Turmel
2016-11-07 1:20 ` Marc MERLIN
2016-11-07 1:39 ` Qu Wenruo
2016-11-07 4:18 ` Qu Wenruo
2016-11-07 5:36 ` btrfs support for filesystems >8TB on 32bit architectures Marc MERLIN
2016-11-07 6:16 ` Qu Wenruo
2016-11-07 14:55 ` Marc MERLIN
2016-11-08 0:35 ` Qu Wenruo
2016-11-08 0:39 ` Marc MERLIN
2016-11-08 0:43 ` Qu Wenruo
2016-11-08 1:06 ` Marc MERLIN
2016-11-08 1:17 ` Qu Wenruo
2016-11-08 15:24 ` Marc MERLIN
2016-11-09 1:50 ` Qu Wenruo
2016-11-09 2:05 ` Marc MERLIN
2016-11-11 3:48 ` Marc MERLIN
2016-11-11 3:55 ` Qu Wenruo
2016-11-12 3:17 ` when btrfs scrub reports errors and btrfs check --repair does not Marc MERLIN
2016-11-13 15:06 ` Marc MERLIN
2016-11-13 15:13 ` Roman Mamedov [this message]
2016-11-13 15:52 ` Marc MERLIN
2016-10-30 18:56 ` [ LR] Kernel 4.8.4: INFO: task kworker/u16:8:289 blocked for more than 120 seconds TomK
2016-10-30 19:16 ` TomK
2016-10-30 20:13 ` Andreas Klauer
2016-10-30 21:08 ` TomK
2016-10-31 19:29 ` Wols Lists
2016-11-01 2:40 ` TomK
2016-10-30 16:43 ` Buffer I/O error on dev md5, logical block 7073536, async page read Marc MERLIN
2016-10-30 17:02 ` Andreas Klauer
2016-10-31 19:24 ` Wols Lists
-- strict thread matches above, loose matches on Subject: below --
2016-10-30 18:34 btrfs check --repair: ERROR: cannot read chunk root Marc MERLIN
2016-10-31 1:02 ` Qu Wenruo
2016-10-31 2:06 ` Marc MERLIN
2016-10-31 4:21 ` Marc MERLIN
2016-10-31 5:27 ` Qu Wenruo
2016-10-31 5:47 ` Marc MERLIN
2016-10-31 6:04 ` Qu Wenruo
2016-10-31 6:25 ` Marc MERLIN
2016-10-31 6:32 ` Qu Wenruo
2016-10-31 6:37 ` Marc MERLIN
2016-10-31 7:04 ` Qu Wenruo
2016-10-31 8:44 ` Hugo Mills
2016-10-31 15:04 ` Marc MERLIN
2016-11-01 3:48 ` Marc MERLIN
2016-11-01 4:13 ` Qu Wenruo
2016-11-01 4:21 ` Marc MERLIN
2016-11-04 8:01 ` Marc MERLIN
2016-11-04 9:00 ` Roman Mamedov
2016-11-04 17:59 ` Marc MERLIN
2016-11-07 1:11 ` Qu Wenruo
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=20161113201329.1851b992@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.