From: Chris Mason <chris.mason@oracle.com>
To: Hugo Mills <hugo-lkml@carfax.org.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Online resize vs ENOSPC
Date: Tue, 10 Mar 2009 09:37:34 -0400 [thread overview]
Message-ID: <1236692254.23800.6.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20090309143501.GD6698@vlad.carfax.org.uk>
On Mon, 2009-03-09 at 14:35 +0000, Hugo Mills wrote:
> On Mon, Mar 09, 2009 at 10:31:41AM +0000, Hugo Mills wrote:
> > After an online resize, the filesystem reports its new size, but
> > still runs out of space at the old size:
> [...]
> > Unmounting and remounting the filesystem seems to make the new
> > space available for use again.
> >
> > This is the second time I've had this happen to me now, so it seems
> > to be more-or-less reproducible, although I haven't deliberately tried
> > to trigger the behaviour yet.
>
> Just to confirm, I can indeed reproduce it trivially:
>
Ok, thanks for tracking this down. I see the bug and will send out a
fix shortly for you to try.
-chris
prev parent reply other threads:[~2009-03-10 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 10:31 Online resize vs ENOSPC Hugo Mills
2009-03-09 14:35 ` Hugo Mills
2009-03-10 13:37 ` Chris Mason [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=1236692254.23800.6.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=hugo-lkml@carfax.org.uk \
--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