From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: cancel btrfs delete job
Date: Thu, 26 Jun 2014 11:30:26 +0000 (UTC) [thread overview]
Message-ID: <pan$29732$53f31aa9$65c1c12$13bb56c9@cox.net> (raw)
In-Reply-To: 1403780795.7657.7.camel@hsew-frn.HIPERSCAN
Franziska Näpelt posted on Thu, 26 Jun 2014 13:06:35 +0200 as excerpted:
> There are a lot of following messages:
> btrfs free space inode generation (0) did not match free space cache
> generation
Well, set of messages at least is somewhat expected after a hard
shutdown, and shouldn't be a problem as the filesystem should rebuild the
cache. In fact, that space_cache rebuild might be why you were seeing
such high I/O after the reboot and fresh mount.
If the space-cache rebuild is all the problems you see, you may be lucky,
and the hard-terminated delete and reboot might not have resulted in any
permanent damage. OTOH, if it seems the space_cache rebuild is
interfering with further activity for too long and you end up doing
another hard reset anyway, there's the nospace_cache mount option to turn
it off.
(Just a user and list regular with that single comment... I'll let you
get back to the expert help now.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-06-26 11:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 7:50 cancel btrfs delete job Franziska Näpelt
2014-06-26 7:17 ` Satoru Takeuchi
[not found] ` <1403777123.7657.5.camel@hsew-frn.HIPERSCAN>
[not found] ` <53AC013E.5000702@jp.fujitsu.com>
2014-06-26 11:34 ` Franziska Näpelt
2014-06-26 23:29 ` Satoru Takeuchi
2014-06-27 8:55 ` Satoru Takeuchi
2014-06-26 11:06 ` Franziska Näpelt
2014-06-26 11:30 ` Duncan [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-26 11:47 Franziska Näpelt
2014-06-26 13:25 ` Duncan
2014-06-26 13:47 ` Franziska Näpelt
2014-06-27 0:49 ` Russell Coker
2014-06-27 5:26 ` Duncan
2014-06-27 5:00 Franziska Näpelt
2014-06-27 5:58 ` Satoru Takeuchi
2014-06-27 8:09 ` Satoru Takeuchi
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='pan$29732$53f31aa9$65c1c12$13bb56c9@cox.net' \
--to=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).