From: Lubos Kolouch <lubos.kolouch@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: scrub to delete files
Date: Sat, 24 Mar 2012 13:22:43 +0000 (UTC) [thread overview]
Message-ID: <jkkhr3$26m$1@dough.gmane.org> (raw)
In-Reply-To: 201203241410.42465.Martin@lichtvoll.de
Martin Steigerwald, Sat, 24 Mar 2012 14:10:42 +0100:
> Am Samstag, 24. M=C3=A4rz 2012 schrieb Lubos Kolouch:
>> Hello,
>=20
> Hi Lubos,
>=20
>> 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, sect=
or
>> 492918400, root 5232, inode 3360637, offset 217088, length 4096, lin=
ks
>> 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?
>=20
> What kernel version are you using?
>=20
> I thought that with newer kernel versions it would put the name of th=
e
> file which failed into kernel log as well. Then you could grep for
> those, awk them out of the log file and delete them then.
>=20
> Since my filesystems all scrub well I have no example log message.
>=20
> Thanks,
> --
> Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C
> 0040 0710 4AFA B82F 991B EAAC A599 84C7
Hallo Martin,
Thank you for reply...
I'm using 3.3.0 - yes, it is in the log file so I will do that. Just=20
though if scrub does not have a (non-documented) option to do it.
Thanks
Lubos
--
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
prev parent reply other threads:[~2012-03-24 13:22 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
2012-03-24 13:22 ` Lubos Kolouch [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='jkkhr3$26m$1@dough.gmane.org' \
--to=lubos.kolouch@gmail.com \
--cc=linux-btrfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox