From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: BTRFS cannot remove empty directory pretending it is not empty
Date: Tue, 25 Aug 2015 15:25:12 +0200 [thread overview]
Message-ID: <1474026.LQOmDW8fG5@tethys> (raw)
In-Reply-To: <pan$d4557$9c42de4e$12e74017$2f692aea@cox.net>
Le mardi 25 août 2015 08:37:46 vous avez écrit :
> The errors 200 flags are reasonably common, and I believe
> btrfs check --repair handles them well.
Uh, I've started it hours ago, and it has been eating 100% CPU on one of my
cores since, without apparently yet finding a single error. It seems that
without the --repair flag, btrfs check goes relatively fast, but with this
flag (and even on an half-full 500GB SSD), it seems to take forever.
I've started it (just for checking) on another machine which FS looked clean
in use, and on this other machine it has displayed that it was correcting a
huge number of apparently more serious errors. However on this 2nd machine as
well, it's taking houuuuurs...
> I already stressed the admin rule that no backups means you don't care if
> it's lost
I'm a white-haired long-beared sysadmin. Nobody ever had more backups than I
do ;-))) -- which tends to show that I care about my data. However restoring a
complete machine with complex filesystems and snapshots remains a tedious
process...
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
next prev parent reply other threads:[~2015-08-25 13:25 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 ` BTRFS cannot remove empty " Swâmi Petaramesh
2015-08-25 8:37 ` Duncan
2015-08-25 13:25 ` Swâmi Petaramesh [this message]
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=1474026.LQOmDW8fG5@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).