From: Andrei Popa <ierdnah@gmail.com>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Btrfs-progs: support get/reset device stats via ioctl
Date: Thu, 17 May 2012 12:18:20 +0300 [thread overview]
Message-ID: <1337246300.28385.13.camel@ierdnac-hp> (raw)
In-Reply-To: <4FB4BA87.7090709@giantdisaster.de>
On Thu, 2012-05-17 at 10:44 +0200, Stefan Behrens wrote:
> On 05/16/2012 19:03, Andrei Popa wrote:
> > It would be nice if this function could show the file names affected by
> > errors, in case of a single, non-redundant drive, btrfs-progs should
> > show what files are affected by errors.
> > Then, an admin could restore only those files from backup.
> >
> > On Wed, 2012-05-16 at 18:50 +0200, Stefan Behrens wrote:
> >> "btrfs device stats" is used to retrieve and print the device stats.
> >> "btrfs device stats -z" is used to atomically retrieve, reset and
> >> print the stats.
>
>
> In case of disk errors, it is recommended to run scrub on that disk. It
> checks the in-use disk contents for errors, repairs errors where
> possible, and the scrub tool does print the paths and filenames of
> errored files into the kernel log.
In an automated script or for the usual user it would be easier to get
the output from btrfs-progs scrub command with the affected files,
instead from kernel log.
prev parent reply other threads:[~2012-05-17 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 16:50 [PATCH v3 0/3] Btrfs-progs: support get/reset device stats via ioctl Stefan Behrens
2012-05-16 16:50 ` [PATCH v3 1/3] Btrfs-progs: move open_file_or_dir() to utils.c Stefan Behrens
2012-05-16 16:50 ` [PATCH v3 2/3] Btrfs-progs: make two utility functions globally available Stefan Behrens
2012-05-16 16:50 ` [PATCH v3 3/3] Btrfs-progs: add command to get/reset device stats via ioctl Stefan Behrens
2012-05-16 17:03 ` [PATCH v3 0/3] Btrfs-progs: support " Andrei Popa
2012-05-17 8:44 ` Stefan Behrens
2012-05-17 9:18 ` Andrei Popa [this message]
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=1337246300.28385.13.camel@ierdnac-hp \
--to=ierdnah@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
/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).