linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/inode.c:2260!
Date: Fri, 10 Jun 2011 00:52:24 -0400	[thread overview]
Message-ID: <m3vcwes2xr.fsf@jhcloos.com> (raw)
In-Reply-To: <20110610002208.GQ12709@twin.jikos.cz> (David Sterba's message of "Fri, 10 Jun 2011 02:22:08 +0200")

>>>>> "DS" == David Sterba <dave@jikos.cz> writes:

DS> confirmed, -ENOSPC == -28

So not a novel BUG_ON() after all.

On the plus side, it has not re-appeared in the 3.0 rc's.

That (4 Gig) fs currently has:

:; find /usr/local/portage|wc -l
444073

:; df /usr/local/portage
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/sda12       4194304 1278124   1767252  42% /usr/local/portage

:; btrfs filesystem df /usr/local/portage/
Data: total=1.21GB, used=822.17MB
System: total=4.00MB, used=4.00KB
Metadata: total=1.51GB, used=426.00MB

Most of the files are quite small, even before compression.
About 40% are directories.

I've never run balance or defragment on that filesystem.  Should I?

(It is a single-disk, single-partition fs; it has no subvolumes;
it is mounted with rw,noatime,compress=zlib; it is in exports and
does get mounted over nfs3.)

(I take it balance is for multi-device applications?  --help uses the
singular 'the device' but the btrfs(8) man page uses the plural 'the
devices'....)

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

      reply	other threads:[~2011-06-10  4:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30 17:33 kernel BUG at fs/btrfs/inode.c:2260! James Cloos
2011-06-10  0:22 ` David Sterba
2011-06-10  4:52   ` James Cloos [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=m3vcwes2xr.fsf@jhcloos.com \
    --to=cloos@jhcloos.com \
    --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).