All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantinos Skarlatos <k.skarlatos@gmail.com>
To: Josef Bacik <josef@redhat.com>
Cc: Calvin Walton <calvin.walton@kepstin.ca>, linux-btrfs@vger.kernel.org
Subject: Re: Do not use free space caching!
Date: Fri, 01 Apr 2011 16:27:19 +0300	[thread overview]
Message-ID: <4D95D2B7.4020202@gmail.com> (raw)
In-Reply-To: <20110331225956.GC7484@dhcp231-156.rdu.redhat.com>

On 1/4/2011 1:59 =CF=80=CE=BC, Josef Bacik wrote:
> On Thu, Mar 31, 2011 at 05:06:42PM -0400, Calvin Walton wrote:
>> On Wed, 2011-03-30 at 17:19 -0400, Josef Bacik wrote:
>>> Hello,
>>>
>>> Just found a big bug in the free space caching stuff that will resu=
lt in
>>> early ENOSPC.  I'm working on fixing this bug, but it won't be unti=
l
>>> 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 u=
se 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,
>> Any chance you could provide a little more information about which
>> kernels are affected? Is it any kernel with free space cache support=
 (is
>> 2.6.38.x included?) - and if so, do you plan on submitting the fix t=
o
>> the stable kernel series?
>>
> Yeah it affects any kernel that has the free space cache feature, whi=
ch I think
> started in .37.  Course you have to have specifically enabled it, so =
it's not a
> huge problem.  I've submitted a patch, but since it's currently an op=
tional
> feature I don't think it needs to go to stable.  Thanks,
So it will have to wait for 2.6.39? If possible please push it for=20
inclusion it in the next stable of 2.6.38, as 2.6.39 is a few months=20
away and i wont risk an early RC for my system

Thanks
> Josef
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs=
" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-04-01 13:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 21:19 Do not use free space caching! Josef Bacik
2011-03-31 21:06 ` Calvin Walton
2011-03-31 22:59   ` Josef Bacik
2011-04-01 13:27     ` Konstantinos Skarlatos [this message]
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=4D95D2B7.4020202@gmail.com \
    --to=k.skarlatos@gmail.com \
    --cc=calvin.walton@kepstin.ca \
    --cc=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.