linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Konstantin V. Gavrilenko" <k.gavrilenko@arhont.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: btrfs errors
Date: Tue, 13 Aug 2019 10:48:46 +0100 (BST)	[thread overview]
Message-ID: <347523577.41.1565689723208.JavaMail.gkos@xpska> (raw)
In-Reply-To: <632175948.36.1565689408284.JavaMail.gkos@xpska>

Hi list

I have run the btrfs check, and that reported multiple errors on the FS.

# btrfs check --readonly --force /dev/kubuntu-vg/lv_root
<SKIP>
root 9214 inode 6850330 errors 2001, no inode item, link count wrong
        unresolved ref dir 266982 index 22459 namelen 36 name 9621041045a17a475428a26fcfb5982f.png filetype 1 errors 6, no dir index, no inode ref
        unresolved ref dir 226516 index 9 namelen 28 name GYTSPMxjwCVp8kXB7+j91O8kcq4= filetype 1 errors 4, no inode ref
root 9214 inode 6877070 errors 2001, no inode item, link count wrong
        unresolved ref dir 226516 index 11 namelen 28 name VSqlYzl4pFqJpvC3GA9bQ0mZK8A= filetype 1 errors 4, no inode ref
root 9214 inode 6878054 errors 2001, no inode item, link count wrong
        unresolved ref dir 266982 index 22460 namelen 36 name 52e74e9d2b6f598038486f90f8f911c4.png filetype 1 errors 4, no inode ref
root 9214 inode 6888414 errors 2001, no inode item, link count wrong
        unresolved ref dir 226391 index 122475 namelen 14 name the-real-index filetype 1 errors 4, no inode ref
root 9214 inode 6889202 errors 100, file extent discount
Found file extent holes:
        start: 0, len: 4096
root 9214 inode 6889203 errors 100, file extent discount
Found file extent holes:
        start: 0, len: 4096
ERROR: errors found in fs roots
found 334531551237 bytes used, error(s) found
total csum bytes: 291555464
total tree bytes: 1004404736
total fs tree bytes: 411713536
total extent tree bytes: 242974720
btree space waste bytes: 186523621
file data blocks allocated: 36730163200
 referenced 42646511616


However, scrub and badblock find no errors.

# btrfs scrub status /mnt/
scrub status for 7b19fb5e-4e16-4b62-b803-f59364fd61a2
        scrub started at Tue Aug 13 07:31:38 2019 and finished after 00:02:47
        total bytes scrubbed: 311.15GiB with 0 errors

# badblocks -sv /dev/kubuntu-vg/lv_root 
Checking blocks 0 to 352133119
Checking for bad blocks (read-only test):  done                                                 
Pass completed, 0 bad blocks found. (0/0/0 errors)

# btrfs dev stats /dev/kubuntu-vg/lv_root                                                                                                                                                       
[/dev/mapper/kubuntu--vg-lv_root].write_io_errs    0
[/dev/mapper/kubuntu--vg-lv_root].read_io_errs     0
[/dev/mapper/kubuntu--vg-lv_root].flush_io_errs    0
[/dev/mapper/kubuntu--vg-lv_root].corruption_errs  0
[/dev/mapper/kubuntu--vg-lv_root].generation_errs  0



FS mount fine, and is operational.
would you recommend executing the btrfs check --repair option or is there something else that I can try.

#  uname -a                                                                                                                                                                                         Linux xps 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
# btrfs --version                                                                                                                                                                               
btrfs-progs v4.15.1


mount options
on / type btrfs (rw,relatime,compress-force=lzo,ssd,discard,space_cache=v2,autodefrag,subvol=/@)

thanks,
Konstantin

       reply	other threads:[~2019-08-13  9:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <632175948.36.1565689408284.JavaMail.gkos@xpska>
2019-08-13  9:48 ` Konstantin V. Gavrilenko [this message]
2019-08-13 10:55   ` btrfs errors Qu Wenruo
     [not found]     ` <744798339.29.1565703591504.JavaMail.gkos@xpska>
2019-08-13 14:01       ` Qu Wenruo
     [not found]         ` <1425294964.32.1565720950325.JavaMail.gkos@xpska>
2019-08-13 23:24           ` Qu Wenruo
2019-08-14  9:12             ` Konstantin V. Gavrilenko
2021-05-09 22:08 BTRFS Errors Michael Stickel
2021-05-15  2:24 ` Zygo Blaxell
  -- strict thread matches above, loose matches on Subject: below --
2018-03-14  2:07 btrfs errors higuita
2018-03-14  4:24 ` Chris Murphy
2018-03-17  1:34   ` higuita
2018-03-17 17:31     ` Chris Murphy
     [not found] <AFB7E63B2FEE4449B3DBF47BC3AA36F085956971@server2k8.thomii.com>
2011-12-02 12:34 ` Mike Thomas
2011-12-02 12:38   ` Fajar A. Nugraha
2011-12-02 12:42     ` Mike Thomas

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=347523577.41.1565689723208.JavaMail.gkos@xpska \
    --to=k.gavrilenko@arhont.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;
as well as URLs for NNTP newsgroup(s).