Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: Lubos Kolouch <lubos.kolouch@gmail.com>
Subject: Re: scrub to delete files
Date: Sat, 24 Mar 2012 14:10:42 +0100	[thread overview]
Message-ID: <201203241410.42465.Martin@lichtvoll.de> (raw)
In-Reply-To: <jkka60$qin$2@dough.gmane.org>

Am Samstag, 24. M=C3=A4rz 2012 schrieb Lubos Kolouch:
> Hello,

Hi Lubos,

> I have a (rather historical btrfs) filesystem running here.
> When I run scrub, I get a lot of messages like :
> btrfs: checksum error at logical 2153033760768 on dev /dev/md2, secto=
r
> 492918400, root 5232, inode 3360637, offset 217088, length 4096, link=
s
> 1 (path: ....)
>=20
> and
>=20
> btrfs: unable to fixup (regular) error at logical 2154979917824
>=20
> Is there a way how to have scrub delete the broken files?
> What to do with the unable to fixup messages?

What kernel version are you using?

I thought that with newer kernel versions it would put the name of the =
file=20
which failed into kernel log as well. Then you could grep for those, aw=
k=20
them out of the log file and delete them then.

Since my filesystems all scrub well I have no example log message.

Thanks,
--=20
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-03-24 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 11:12 scrub to delete files Lubos Kolouch
2012-03-24 13:10 ` Martin Steigerwald [this message]
2012-03-24 13:22   ` Lubos Kolouch

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=201203241410.42465.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lubos.kolouch@gmail.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