From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS cannot remove empty directory pretending it is not empty
Date: Tue, 25 Aug 2015 10:18:26 +0200 [thread overview]
Message-ID: <4755396.RFUxGNmK6p@tethys> (raw)
In-Reply-To: <pan$3546e$3dbd1a66$4b200cff$9537e206@cox.net>
Le vendredi 21 août 2015 11:23:19 Duncan a écrit :
> So I'd suggest running btrfs check, without --repair, first, and see what
> it says. If the only reported problems have to do with inode refcounts,
> then (assuming your backups are current, just in case, admin's rule of
> backups, if you don't have them, you don't care about losing the data)
> I'd then go ahead and run it with --repair.
Hi Duncan,
Here's what I get using "btrfs check" on said device. Do you think that
running it with "--repair" would be beneficial, or risky ?
root@partedmagic:~# btrfs check /dev/VGZ/LINUX
Checking filesystem on /dev/VGZ/LINUX
UUID: 13c87f57-3a85-4daf-a4bf-ba777407c169
checking extents
checking free space cache
checking fs roots
root 267 inode 297 errors 200, dir isize wrong
root 267 inode 3341 errors 200, dir isize wrong
root 267 inode 324547 errors 200, dir isize wrong
root 9119 inode 297 errors 200, dir isize wrong
root 9119 inode 3341 errors 200, dir isize wrong
root 9119 inode 324547 errors 200, dir isize wrong
root 10972 inode 297 errors 200, dir isize wrong
root 10972 inode 3341 errors 200, dir isize wrong
root 10972 inode 324547 errors 200, dir isize wrong
root 12028 inode 297 errors 200, dir isize wrong
root 12028 inode 3341 errors 200, dir isize wrong
root 12028 inode 324547 errors 200, dir isize wrong
root 14103 inode 297 errors 200, dir isize wrong
root 14103 inode 3341 errors 200, dir isize wrong
root 14103 inode 324547 errors 200, dir isize wrong
root 16144 inode 297 errors 200, dir isize wrong
root 16144 inode 3341 errors 200, dir isize wrong
root 16144 inode 324547 errors 200, dir isize wrong
root 18136 inode 297 errors 200, dir isize wrong
root 18136 inode 3341 errors 200, dir isize wrong
root 18136 inode 324547 errors 200, dir isize wrong
root 20366 inode 297 errors 200, dir isize wrong
root 20366 inode 3341 errors 200, dir isize wrong
root 20366 inode 324547 errors 200, dir isize wrong
root 22870 inode 297 errors 200, dir isize wrong
root 22870 inode 3341 errors 200, dir isize wrong
root 22870 inode 324547 errors 200, dir isize wrong
root 23600 inode 297 errors 200, dir isize wrong
root 23600 inode 3341 errors 200, dir isize wrong
root 23600 inode 324547 errors 200, dir isize wrong
root 23700 inode 297 errors 200, dir isize wrong
root 23700 inode 3341 errors 200, dir isize wrong
root 23700 inode 324547 errors 200, dir isize wrong
root 23850 inode 297 errors 200, dir isize wrong
root 23850 inode 3341 errors 200, dir isize wrong
root 23850 inode 324547 errors 200, dir isize wrong
root 23993 inode 297 errors 200, dir isize wrong
root 23993 inode 3341 errors 200, dir isize wrong
root 23993 inode 324547 errors 200, dir isize wrong
root 24083 inode 297 errors 200, dir isize wrong
root 24083 inode 3341 errors 200, dir isize wrong
root 24083 inode 324547 errors 200, dir isize wrong
root 24133 inode 297 errors 200, dir isize wrong
root 24133 inode 3341 errors 200, dir isize wrong
root 24133 inode 324547 errors 200, dir isize wrong
root 24153 inode 297 errors 200, dir isize wrong
root 24153 inode 3341 errors 200, dir isize wrong
root 24153 inode 324547 errors 200, dir isize wrong
root 24163 inode 297 errors 200, dir isize wrong
root 24163 inode 3341 errors 200, dir isize wrong
root 24163 inode 324547 errors 200, dir isize wrong
root 24173 inode 297 errors 200, dir isize wrong
root 24173 inode 3341 errors 200, dir isize wrong
root 24173 inode 324547 errors 200, dir isize wrong
root 24183 inode 297 errors 200, dir isize wrong
root 24183 inode 3341 errors 200, dir isize wrong
root 24183 inode 324547 errors 200, dir isize wrong
root 24193 inode 297 errors 200, dir isize wrong
root 24193 inode 3341 errors 200, dir isize wrong
root 24193 inode 324547 errors 200, dir isize wrong
root 24205 inode 297 errors 200, dir isize wrong
root 24205 inode 3341 errors 200, dir isize wrong
root 24205 inode 324547 errors 200, dir isize wrong
root 24216 inode 297 errors 200, dir isize wrong
root 24216 inode 3341 errors 200, dir isize wrong
root 24216 inode 324547 errors 200, dir isize wrong
root 24226 inode 297 errors 200, dir isize wrong
root 24226 inode 3341 errors 200, dir isize wrong
root 24226 inode 324547 errors 200, dir isize wrong
root 24236 inode 297 errors 200, dir isize wrong
root 24236 inode 3341 errors 200, dir isize wrong
root 24236 inode 324547 errors 200, dir isize wrong
root 24246 inode 297 errors 200, dir isize wrong
root 24246 inode 3341 errors 200, dir isize wrong
root 24246 inode 324547 errors 200, dir isize wrong
root 24256 inode 297 errors 200, dir isize wrong
root 24256 inode 3341 errors 200, dir isize wrong
root 24256 inode 324547 errors 200, dir isize wrong
root 24266 inode 297 errors 200, dir isize wrong
root 24266 inode 3341 errors 200, dir isize wrong
root 24266 inode 324547 errors 200, dir isize wrong
root 24276 inode 297 errors 200, dir isize wrong
root 24276 inode 3341 errors 200, dir isize wrong
root 24276 inode 324547 errors 200, dir isize wrong
found 104803262666 bytes used err is 1
total csum bytes: 217220208
total tree bytes: 4058595328
total fs tree bytes: 3542876160
total extent tree bytes: 225337344
btree space waste bytes: 809904359
file data blocks allocated: 656106184704
referenced 364340379648
Btrfs v3.18.2
Kind regards.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
next prev parent reply other threads:[~2015-08-25 8:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 8:19 BTRFS cannot remove empry directory pretending it is not empty Swâmi Petaramesh
2015-08-21 8:47 ` Karsten Heymann
2015-08-21 9:15 ` Swâmi Petaramesh
2015-08-21 9:16 ` Roman Mamedov
2015-08-21 9:45 ` Hugo Mills
2015-08-21 11:23 ` Duncan
2015-08-21 15:39 ` Swâmi Petaramesh
2015-08-21 18:07 ` Duncan
2015-08-25 8:18 ` Swâmi Petaramesh [this message]
2015-08-25 8:37 ` BTRFS cannot remove empty " Duncan
2015-08-25 13:25 ` Swâmi Petaramesh
2015-08-25 14:03 ` Swâmi Petaramesh
2015-08-25 22:29 ` Duncan
2015-08-25 22:38 ` Hugo Mills
[not found] ` <9Aea1r00U2Q6ekd01Aebva>
2015-08-25 23:32 ` Duncan
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=4755396.RFUxGNmK6p@tethys \
--to=swami@petaramesh.org \
--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).