From: Hugo Mills <hugo@carfax.org.uk>
To: Marc MERLIN <marc@merlins.org>
Cc: Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0
Date: Mon, 18 Jan 2016 12:45:33 +0000 [thread overview]
Message-ID: <20160118124533.GU422@carfax.org.uk> (raw)
In-Reply-To: <20160118002748.GE12045@merlins.org>
[-- Attachment #1: Type: text/plain, Size: 2669 bytes --]
On Sun, Jan 17, 2016 at 04:27:48PM -0800, Marc MERLIN wrote:
> So, I had an FS with a few issues, I ran btrfs check --repair to completion
>
> Then, after mounting, I still get this warning.
> Shouldn't those error counters be reset after check --repair?
>
> Kernel: 4.2.5
> Btrfs-tools: 4.3-1
>
> If that matters, here's the output of check --repair (captured with script
> -f, so the output is a bit wrong):
> gargamel:~# btrfs check --repair -p /dev/mapper/dshelf1
> enabling repair mode
> Checking filesystem on /dev/mapper/dshelf1
> UUID: 6358304a-2234-4243-b02d-4944c9af47d7
> badcextentx[29368320, 29372416), type mismatch with chunk
> bad extent [29372416, 29376512), type mismatch with chunk
>
> (2856970 lines deleted)
>
> bad extent [8697338122240, 8697338126336), type mismatch with chunk
> bad extent [8697338126336, 8697338130432), type mismatch with chunk
> bad extent [8697338130432, 8697338134528), type mismatch with chunk
This is, I think, a symptom of an FS created with a broken
mkfs.btrfs, and it needs to be re-created. Take a look for that error
message in the mailing list archives -- there's been a few posts about
it in the last couple of months.
Hugo.
> checking extents [.]
>
> repaired damaged extent references
>
> Fixed 0 roots.
> cache and super generation don't match, space cache will be invalidated
> Fixedidiscountofileoextents for inode: 204450 in root: 45851
> FixedidiscountofileOextents for inode: 204452 in root: 45851
> root 45851 inode 204452 errors 40, bad file extent
> Fixedidiscountofileoextents for inode: 204452 in root: 45851
> root 45851 inode 204452 errors 40, bad file extent
> rootk45851sinodes204452 errors 40, bad file extent
> FixedidiscountofileOextents for inode: 204450 in root: 45852
> FixedidiscountofileOextents for inode: 204452 in root: 45852
> checking fs roots [o]
> rootk45851sinodes204452 errors 40, bad file extent
> Fixedidiscountofile.extents for inode: 204450 in root: 45856
> Fixed discount file extents for inode: 204452 in root: 45856
> rootk45851sinodes204452 errors 40, bad file extent
> warninggliner3653 [o]
>
> checking csums
> checking root refs
> found 9826147025859 bytes used err is 0
> total csum bytes: 9584068648
> total tree bytes: 12200706048
> total fs tree bytes: 330457088
> total extent tree bytes: 498716672
> btree space waste bytes: 1372963760
> file data blocks allocated: 9976766078976
> referenced 9987816431616
> btrfs-progs v4.3
>
> Thanks,
> Marc
--
Hugo Mills | In my day, we didn't have fancy high numbers. We had
hugo@... carfax.org.uk | "nowt", "one", "twain" and "multitudes".
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2016-01-18 12:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 0:27 BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0 Marc MERLIN
2016-01-18 3:21 ` Duncan
2016-01-18 23:39 ` Marc MERLIN
2016-01-19 9:39 ` Duncan
2016-01-21 4:52 ` Marc MERLIN
2016-01-23 17:03 ` Marc MERLIN
2016-01-23 23:13 ` Marc MERLIN
2016-01-25 1:37 ` Qu Wenruo
2016-01-25 15:55 ` 4.4.0: btrfs-send BUG_ON(sctx->cur_ino != sctx->cmp_key->objectid); Marc MERLIN
2016-01-25 19:46 ` Filipe Manana
2016-01-25 19:56 ` Marc MERLIN
2016-01-25 20:24 ` Filipe Manana
2016-01-25 21:21 ` Marc MERLIN
2016-01-25 20:55 ` BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0 Marc MERLIN
2016-01-26 1:03 ` Qu Wenruo
2016-02-11 6:31 ` btrfs-image failure (btrfs-tools 4.4) Marc MERLIN
2016-02-11 7:16 ` Qu Wenruo
2016-02-11 15:09 ` Marc MERLIN
2016-02-11 15:13 ` Marc MERLIN
2016-02-12 0:33 ` Qu Wenruo
2016-02-12 17:26 ` Marc MERLIN
2016-02-14 17:26 ` Marc MERLIN
2016-02-15 0:17 ` Qu Wenruo
2016-02-15 16:40 ` Marc MERLIN
2016-01-18 12:45 ` Hugo Mills [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=20160118124533.GU422@carfax.org.uk \
--to=hugo@carfax.org.uk \
--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.