From: "Geir A. Myrestrand" <geir.myrestrand@falconstor.com>
To: linux-xfs@oss.sgi.com
Subject: Re: Will xfs_growfs succeed on a full file system?
Date: Tue, 23 Jan 2007 21:34:44 -0500 [thread overview]
Message-ID: <45B6C5C4.50005@falconstor.com> (raw)
In-Reply-To: <20070124020750.GD44411608@melbourne.sgi.com>
David Chinner wrote:
> On Tue, Jan 23, 2007 at 10:19:27AM -0500, Geir A. Myrestrand wrote:
>> Does xfs_growfs depend on some space left on the file system in order to
>> be able to grow it?
>
> Yes, it does require some space to be left because growing the
> filesystem can require extending the original last AG to the full
> size and that means there may be btree work to be journalled
> and hence we have to reserve blocks for that to succeed in all
> cases.
>
>> I have a colleague who ran into an issue where a file system resize
>> failed. The file system is 100% full.
>
> Yup, we hit that in QA recently and have an open bug for it.
>
>> Aside from analyzing what happened in his case, should XFS be able to
>> grow a file system that is 100% full?
>
> Yes, it should.
>
>> The device has already been expanded, it is the XFS file system that
>> fails to resize. I just wonder if that is by design, or whether it is an
>> issue.
>
> It's a bug, really, but one you can easily work around by freeing
> up about 50k of space. If you've got a really large filesystem, then
> you might need to free more space than that.
>
> At some point in my copious amounts of free time I'll fix it properly...
Thanks a lot for your feedback David. We look forward to a fix, but just
knowing that it is an issue and that we easily can work around it helps
a lot. Thanks again!
--
Geir A. Myrestrand
prev parent reply other threads:[~2007-01-24 2:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 15:19 Will xfs_growfs succeed on a full file system? Geir A. Myrestrand
2007-01-23 16:41 ` Eric Sandeen
2007-01-23 17:18 ` Geir A. Myrestrand
2007-01-24 2:07 ` David Chinner
2007-01-24 2:34 ` Geir A. Myrestrand [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=45B6C5C4.50005@falconstor.com \
--to=geir.myrestrand@falconstor.com \
--cc=linux-xfs@oss.sgi.com \
/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