All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: free space inode generation (0) did not match free space cache generation
Date: Sat, 22 Mar 2014 19:23:48 +0000 (UTC)	[thread overview]
Message-ID: <pan$ed109$9aee6786$583238bb$64d8ada4@cox.net> (raw)
In-Reply-To: 532DD2DC.3030408@friedels.name

Hendrik Friedel posted on Sat, 22 Mar 2014 19:13:48 +0100 as excerpted:

> I have a file-system on which I cannot write anymore (no space left on
> device, which is not true

> root@homeserver:~/btrfs/integration/devel# df -h
> Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
> /dev/sdd2        30G     24G  5,1G   83% /mnt/test1

> root@homeserver:~/btrfs/integration/devel# ./btrfs fi show /mnt/test1
> Label: 'ROOT_BTRFS_RAID'  uuid: a2d5f2db-04ca-413a-aee1-cb754aa8fba5
>          Total devices 2 FS bytes used 11.84GiB
>          devid    1 size 14.85GiB used 14.67GiB path /dev/sde2
>          devid    2 size 14.65GiB used 14.65GiB path /dev/sdd2
> Btrfs this-will-become-v3.13-48-g57c3600

That's a FAQ and I just replied to a different thread with a detailed 
explanation and procedure for fixing.  See

http://permalink.gmane.org/gmane.comp.file-systems.btrfs/33643

It's linked there, but you'll also want to read up on the btrfs wiki, 
particularly the free-space and balance sections of the FAQ, along with 
the balance filters page.

https://btrfs.wiki.kernel.org

Bookmark it! =:^)

-- 
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


  reply	other threads:[~2014-03-22 19:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22 18:13 free space inode generation (0) did not match free space cache generation Hendrik Friedel
2014-03-22 19:23 ` Duncan [this message]
     [not found] <532DF38B.40409@friedels.name>
2014-03-22 21:16 ` Hendrik Friedel
2014-03-22 23:32   ` 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

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$ed109$9aee6786$583238bb$64d8ada4@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 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.