From: Eric Sandeen <sandeen@sandeen.net>
To: Lance Reed <lreed@brightcove.com>
Cc: "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: Mon, 28 Apr 2008 18:00:06 -0500 [thread overview]
Message-ID: <481656F6.5030300@sandeen.net> (raw)
In-Reply-To: <6A32BC807C106440B7E23208F280DDAF01D21F3718@bcmail1.VIDMARK.LOCAL>
Lance Reed wrote:
> Thanks for the quick response.
>
> Actually, I was able to run an xfs_repair and all was well.(took 45 minutes...)
>
> But I would love to be able to expand the XFS file system out to the max.
>
> I guess I could expand it in < 2TB increments then maybe?
>
> Thanks for the update and I will look around.
>
> I did find this which I think is related.
>
> http://oss.sgi.com/archives/xfs/2008-01/msg00097.html
Yep, I think expanding it in, say, 1T increments should be fine, and it
should all (I think...) end up the same as if you'd done it all at once
(modulo the bug, of course...)
-Eric
next prev parent reply other threads:[~2008-04-28 22:59 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 [this message]
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
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=481656F6.5030300@sandeen.net \
--to=sandeen@sandeen.net \
--cc=lreed@brightcove.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