All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: waxhead <waxhead@dirtcellar.net>
Cc: Philip Seeger <philip@philip-seeger.de>,
	Andrei Borzenkov <arvidjaar@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Monitoring not working as "dev stats" returns 0 after read error occurred
Date: Sun, 12 Jan 2020 13:27:15 -0700	[thread overview]
Message-ID: <CAJCQCtTjEiimpuwy1kwPx73QcArhB7_Z3gjP_UWh1==2f7dg-Q@mail.gmail.com> (raw)
In-Reply-To: <01a333c2-b3fc-128c-073a-d7b4d455f13c@dirtcellar.net>

On Sun, Jan 12, 2020 at 10:39 AM waxhead <waxhead@dirtcellar.net> wrote:
>
> Speaking of... it would be great if btrfs device stats /mnt (or some
> other command) could offer to show a list of corrupted files with paths
> (which I assume the filesystem know about). That would make restoring
> files from backup a breeze!

Scrub does this. As well as any time a corrupt file is read. But such
information isn't stored anywhere. Path to file is reported in kernel
messages.

-- 
Chris Murphy

  reply	other threads:[~2020-01-12 20:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08 17:41 Monitoring not working as "dev stats" returns 0 after read error occurred philip
2020-01-08 19:35 ` Graham Cobb
2020-01-09 10:33   ` Philip Seeger
2020-01-09 12:04     ` Nikolay Borisov
2020-01-09 14:34       ` Philip Seeger
2020-01-09 23:50         ` Philip Seeger
2020-01-11  7:42           ` Andrei Borzenkov
2020-01-12 11:42             ` Philip Seeger
2020-01-12 17:39               ` waxhead
2020-01-12 20:27                 ` Chris Murphy [this message]
2020-01-12 22:45                 ` Philip Seeger
2020-01-08 21:47 ` Chris Murphy
2020-01-09 10:49   ` Philip Seeger
2020-01-16  1:16 ` Zygo Blaxell

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='CAJCQCtTjEiimpuwy1kwPx73QcArhB7_Z3gjP_UWh1==2f7dg-Q@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=arvidjaar@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=philip@philip-seeger.de \
    --cc=waxhead@dirtcellar.net \
    /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.