From: Hugo Mills <hugo-lkml@carfax.org.uk>
To: Yien Zheng <esprout@gmail.com>
Cc: Dmitri Nikulin <dnikulin@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Entirely unexpected ENOSPC?
Date: Mon, 9 Mar 2009 13:20:52 +0000 [thread overview]
Message-ID: <20090309132052.GA6698@vlad.carfax.org.uk> (raw)
In-Reply-To: <2c259a8f0903090608r36c50773qaa0bc1606beb5065@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
On Mon, Mar 09, 2009 at 07:08:16AM -0600, Yien Zheng wrote:
> At this point I'm wondering if this is a anomaly or if it has anything
> to do with using an SSD. It seems the pre-2.7.29-rc7 code had a hard
> stop at 85%. But the recent patch doesn't seem to have solve the
> issue for me. Is there another issue that makes btrfs want to reserve
> 2G free? I see another email with someone growing their filesystem
> from 48G to 70G because they ran out of space on their 50G disk, which
> should still have 2G free.
Not quite -- I was some 5G free on a 50G filesystem, without
errors. I expanded the filesystem online to 70G because I knew I would
run out within the next few hours. Despite the expansion, it still ran
out at (just short of) 50G.
Unless you've resized your filesystem online, I think we're seeing
different problems.
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
--- Do not meddle in the affairs of system administrators, for ---
they are subtle, and quick to anger.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-03-09 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 7:32 Entirely unexpected ENOSPC? Yien Zheng
2009-03-08 7:36 ` Yien Zheng
2009-03-08 8:35 ` Dmitri Nikulin
2009-03-09 13:08 ` Yien Zheng
2009-03-09 13:20 ` Hugo Mills [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-04 18:06 Hugo Mills
2009-03-04 18:50 ` Josef Bacik
2009-03-04 20:48 ` Hugo Mills
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=20090309132052.GA6698@vlad.carfax.org.uk \
--to=hugo-lkml@carfax.org.uk \
--cc=dnikulin@gmail.com \
--cc=esprout@gmail.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