From: Hugo Mills <hugo-lkml@carfax.org.uk>
To: Hugo Mills <hugo-lkml@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: Online resize vs ENOSPC
Date: Mon, 9 Mar 2009 14:35:01 +0000 [thread overview]
Message-ID: <20090309143501.GD6698@vlad.carfax.org.uk> (raw)
In-Reply-To: <20090309103141.GA5335@vlad.carfax.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
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:
$ sudo lvcreate scratch -n testresize -L 5G
$ sudo mkfs.btrfs /dev/scratch/testresize
$ sudo mount /dev/scratch/testresize /mnt
$ sudo chmod ug+w /mnt
$ sudo chown hrm. /mnt
$ cd /mnt
$ dd if=/dev/zero of=foo.txt bs=1M count=4096
$ sudo lvextend scratch/testresize -L 9G
$ sudo btrfsctl -r 9G /mnt
$ dd if=/dev/zero of=foo2.txt bs=1M count=4096
and I get an out-of-space error within a few hundred blocks.
$ cd ..
$ sudo umount /mnt
$ sudo mount /dev/scratch/testresize /mnt
$ cd /mnt
$ dd if=/dev/zero of=foo2.txt bs=1M count=4096
and then I can write the full 4G of data.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- There are three mistaiks in this sentance. ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-03-09 14:35 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 [this message]
2009-03-10 13:37 ` 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=20090309143501.GD6698@vlad.carfax.org.uk \
--to=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