linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hendrik Friedel <hendrik@friedels.name>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: btrfsck errors is it save to fix?
Date: Sat, 16 Nov 2013 13:32:48 +0100	[thread overview]
Message-ID: <528765F0.7080909@friedels.name> (raw)
In-Reply-To: <pan$a3720$6cf50f31$9d15d3bf$b3bbf4bb@cox.net>

Hello,

 >> Possible? Yes. Although I did not implicitly mention it, you would
>> combine "clear_cache" and "nospace_cache" - that should do the trick.
>> Then unmount and check.
>
> Thanks and mentally noted for further reference.  I didn't think about
> combining the options, but it makes perfect sense now that I have, thanks
> to you. =:^)

For me, it unfortunately did not work:

  mount /dev/sdc1  /mnt/BTRFS/Video/VDR -o clear_cache,nospace_cache

[wait a day or two]

Checking filesystem on /dev/sdc1
UUID: 989306aa-d291-4752-8477-0baf94f8c42f
checking extents
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
root 256 inode 9579 errors 100, file extent discount
root 256 inode 9580 errors 100, file extent discount
root 256 inode 14258 errors 100, file extent discount
root 256 inode 14259 errors 100, file extent discount
root 4444 inode 9579 errors 100, file extent discount
root 4444 inode 9580 errors 100, file extent discount
root 4444 inode 14258 errors 100, file extent discount
root 4444 inode 14259 errors 100, file extent discount
found 2928473450130 bytes used err is 1
total csum bytes: 3206482672
total tree bytes: 3902070784
total fs tree bytes: 38912000
total extent tree bytes: 136044544
btree space waste bytes: 411777432
file data blocks allocated: 3447164817408
  referenced 3446445981696
Btrfs v0.20-rc1-596-ge9ac73b

Same as before (just a bit more verbose).

Does it help to delete the files at the affected inodes? How do I find, 
which files are stored at these inodes?

Greetings,
Hendrik


-- 
Hendrik Friedel
Auf dem Brink 12
28844 Weyhe
Mobil 0178 1874363

      reply	other threads:[~2013-11-16 12:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 22:29 btrfsck errors is it save to fix? Hendrik Friedel
2013-11-02  8:12 ` cwillu
2013-11-02  8:58   ` Hendrik Friedel
2013-11-04 21:14     ` Hendrik Friedel
2013-11-05  2:03       ` cwillu
2013-11-06  6:45         ` Hendrik Friedel
2013-11-07 19:16           ` Hendrik Friedel
2013-11-08 10:09             ` Duncan
2013-11-09  8:33               ` Hendrik Friedel
2013-11-11 19:06                 ` Hendrik Friedel
2013-11-11 23:58                   ` Kai Krakow
2013-11-12  7:32                     ` Duncan
2013-11-12 19:37                       ` Kai Krakow
2013-11-13 12:20                         ` Duncan
2013-11-13 12:24                         ` Duncan
2013-11-16 12:32                           ` Hendrik Friedel [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=528765F0.7080909@friedels.name \
    --to=hendrik@friedels.name \
    --cc=1i5t5.duncan@cox.net \
    --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).