From: Eric Sandeen <sandeen@sandeen.net>
To: Lance Reed <lreed@brightcove.com>
Cc: "markgw@sgi.com" <markgw@sgi.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Problems with xfs_grow on large LVM + XFS filesystem 20TB size check 2 failed
Date: Tue, 29 Apr 2008 11:55:21 -0500 [thread overview]
Message-ID: <481752F9.8040600@sandeen.net> (raw)
In-Reply-To: <6A32BC807C106440B7E23208F280DDAF01D21F3870@bcmail1.VIDMARK.LOCAL>
Lance Reed wrote:
> Thanks,
>
> Sorry, I am a bit confused on the "data section" vs. the "real-time section"?
>
> Is it enough to just run "xfs_growfs -D XXX /mntpoint" and the rest should fall into place.
>
> Again, sorry for being dense.
> I really appraciate the rapid feedback.
>
Unless you specifically made a filesystem with a realtime subvol, just
ignore it, it's not created by default.
So yes, -D <size> (in blocks) is what you want. A little cumbersome but
not too bad :)
-Eric
next prev parent reply other threads:[~2008-04-29 16:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 21:42 Problems with xfs_grow on large LVM + XFS filesystem 20TB size check 2 failed Lance Reed
2008-04-28 22:34 ` Eric Sandeen
2008-04-28 22:40 ` Lance Reed
2008-04-28 23:00 ` Eric Sandeen
2008-04-29 0:38 ` Mark Goodwin
2008-04-29 0:43 ` Eric Sandeen
2008-04-29 16:15 ` Lance Reed
2008-04-29 16:43 ` Eric Sandeen
2008-04-29 16:52 ` Lance Reed
2008-04-29 16:55 ` Eric Sandeen [this message]
2008-04-30 21:53 ` Lance Reed
2008-04-30 23:24 ` Eric Sandeen
2008-04-30 11:31 ` CentOS project? <- (Re: Problems with xfs_grow on large LVM + XFS filesystem 20TB size check 2 failed) Tru Huynh
2008-04-30 14:54 ` Eric Sandeen
2008-04-29 1:59 ` Problems with xfs_grow on large LVM + XFS filesystem 20TB size check 2 failed David Chinner
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=481752F9.8040600@sandeen.net \
--to=sandeen@sandeen.net \
--cc=lreed@brightcove.com \
--cc=markgw@sgi.com \
--cc=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