All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hendrik Friedel <hendrik@friedels.name>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: free space inode generation (0) did not match free space cache generation
Date: Sat, 22 Mar 2014 22:16:27 +0100	[thread overview]
Message-ID: <532DFDAB.7000600@friedels.name> (raw)
In-Reply-To: <532DF38B.40409@friedels.name>


Hello,

thanks for your help, I appreciate your hint.
I think (reboot into the system with the fs mounted as root still
outstanding), it fixed my problem.
I read through the FAQ you mentioned, but I must admit, that I do not
fully understand.
What I am wondering about is, what caused this problem to arise. The
filesystem was hardly a week old, never mistreated (powered down without
unmounting or so) and not even half full. So what caused the data chunks
all being allocated?

The only thing that I could think of is that I created hourly snapshots
with snapper.
In fact in order to be able to do the balance, I had to delete something
-so I deleted the snapshots.

Can you tell me where I can read about the causes for this problem?
Besides this:
You recommend monitoring the output of btrfs fi show and to do a
balance, whenever unallocated space drops too low. I can monitor this
and let monit send me a message once that happens. Still, I'd like to
know how to make this less likely.

Greetings,
Hendrik



       reply	other threads:[~2014-03-22 21:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <532DF38B.40409@friedels.name>
2014-03-22 21:16 ` Hendrik Friedel [this message]
2014-03-22 23:32   ` free space inode generation (0) did not match free space cache generation Duncan
2014-03-24 20:52     ` Hendrik Friedel
2014-03-25 13:00       ` Duncan
2014-03-25 20:03         ` Hendrik Friedel
2014-03-25 20:10           ` Hugo Mills
2014-03-25 21:28             ` Duncan
2014-03-25 21:50               ` Hugo Mills
2014-03-28  7:32             ` Hendrik Friedel
2014-03-22 18:13 Hendrik Friedel
2014-03-22 19:23 ` 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=532DFDAB.7000600@friedels.name \
    --to=hendrik@friedels.name \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.