From: Russell Coker <russell@coker.com.au>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs dev sta not updating
Date: Tue, 23 Jun 2020 21:21:33 +1000 [thread overview]
Message-ID: <2562478.diVjGI8Sbc@liv> (raw)
In-Reply-To: <00ce925f-e8bb-be84-40bb-25fd215891e6@suse.com>
On Tuesday, 23 June 2020 9:13:04 PM AEST Nikolay Borisov wrote:
> > # btrfs fi usa .
> > Overall:
> > Device size: 62.50GiB
> > Device allocated: 19.02GiB
> > Device unallocated: 43.48GiB
> > Device missing: 0.00B
> > Used: 16.26GiB
> > Free (estimated): 44.25GiB (min: 22.51GiB)
> > Data ratio: 1.00
> > Metadata ratio: 2.00
> > Global reserve: 17.06MiB (used: 0.00B)
> >
> > Data,single: Size:17.01GiB, Used:16.23GiB (95.43%)
> > /dev/sdc1 17.01GiB
> >
> > Metadata,DUP: Size:1.00GiB, Used:17.19MiB (1.68%)
> > /dev/sdc1 2.00GiB
> >
> > System,DUP: Size:8.00MiB, Used:16.00KiB (0.20%)
> > /dev/sdc1 16.00MiB
> >
> > Unallocated:
> > /dev/sdc1 43.48GiB
>
> Do you use compression on this filesystem i.e have you mounted with
> -ocompression= option ?
No, used the default mount with the Debian build of kernel 5.6.14. Everything
was pretty much default with it. Made a filesystem, copied a bunch of large
files to it, tried to read it, got problems.
It was a storage device I suspected of having errors, copying files to/from it
with BTRFS is a good way of exposing errors.
> Based on this data alone it's evident that you don't really have mirrors
> of the data, in this case having experienced the checksum errors should
> have indeed resulted in error counters being incremented. I'll look into
> this.
Thanks.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2020-06-23 11:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 2:09 btrfs dev sta not updating Russell Coker
2020-06-23 6:03 ` Nikolay Borisov
2020-06-23 6:17 ` waxhead
2020-06-23 7:11 ` Nikolay Borisov
2020-06-23 8:00 ` Russell Coker
2020-06-23 8:17 ` Nikolay Borisov
2020-06-23 9:48 ` Russell Coker
2020-06-23 11:13 ` Nikolay Borisov
2020-06-23 11:21 ` Russell Coker [this message]
2020-06-24 11:39 ` Zygo Blaxell
2020-06-24 13:04 ` Nikolay Borisov
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=2562478.diVjGI8Sbc@liv \
--to=russell@coker.com.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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 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.