From: Josef Bacik <josef@redhat.com>
To: linux-btrfs@vger.kernel.org
Subject: Do not use free space caching!
Date: Wed, 30 Mar 2011 17:19:50 -0400 [thread overview]
Message-ID: <4D939E76.1060801@redhat.com> (raw)
Hello,
Just found a big bug in the free space caching stuff that will result in
early ENOSPC. I'm working on fixing this bug, but it won't be until
tomorrow that I'll have it completely working, so for now make sure to
mount -o clear_cache so that it just clears the cache and doesn't use it.
NOTE: It doesn't cause problems other than early ENOSPC, you won't get
corruption or anything like that, tho you could possibly panic.
Sorry for the inconvenience. Thanks,
Josef
next reply other threads:[~2011-03-30 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 21:19 Josef Bacik [this message]
2011-03-31 21:06 ` Do not use free space caching! Calvin Walton
2011-03-31 22:59 ` Josef Bacik
2011-04-01 13:27 ` Konstantinos Skarlatos
2011-04-01 17:56 ` Calvin Walton
2011-04-01 18:00 ` Chris Mason
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=4D939E76.1060801@redhat.com \
--to=josef@redhat.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 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.