All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Chip Turner <cturner@pattern.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Filesystem unable to recover from ENOSPC
Date: Fri, 11 Apr 2014 17:28:28 +0800	[thread overview]
Message-ID: <20140411092827.GD26503@localhost.localdomain> (raw)
In-Reply-To: <CAH3EO-qB91cTUT0ZAib4xAA82_RDGM4dOWmp3smtUfS_=e1uxg@mail.gmail.com>

On Thu, Apr 10, 2014 at 11:10:33PM -0700, Chip Turner wrote:
> Thank you for the extremely detailed and helpful reply.  I now
> understand what was happening.  To me, when I read "total=" I guess I
> thought that was capacity rather than allocated (but now "holey")
> chunks.  I agree that perhaps adjusting the phrasing of the output of
> df and show would be helpful in making this clearer (or perhaps some
> adjustment to the wiki; maybe I will do that).
> 
> I assume metadata is where filesystem information (directory entries,
> inodes, etc) are stored and not being able to delete was because there
> wasn't room in the metadata chunks, and no room to allocate more
> metadata chunks?  Or are those also data chunks and it was purely
> about data chunks?

Yes and no.  Deleting metadata also needs metadata, and metadata chunk and data
chunk are different ones.

> 
> Does defrag do similar reallocation to balance such that it would help
> combat this behavior?

I'm afraid it won't, since you have that many hardlinks, defrag may not help on
reducing metadata.

thanks,
-liubo

      reply	other threads:[~2014-04-11  9:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 20:00 Filesystem unable to recover from ENOSPC Chip Turner
2014-04-10 20:34 ` Hugo Mills
2014-04-10 22:40   ` Chip Turner
2014-04-11  2:09     ` Duncan
2014-04-11  6:10       ` Chip Turner
2014-04-11  9:28         ` Liu Bo [this message]

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=20140411092827.GD26503@localhost.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=cturner@pattern.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.