From: David Chinner <dgc@sgi.com>
To: Christian Guggenberger <christian.guggenberger@physik.uni-regensburg.de>
Cc: David Chinner <dgc@sgi.com>, Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com
Subject: Re: mount failed after xfs_growfs beyond 16 TB
Date: Tue, 7 Nov 2006 19:17:48 +1100 [thread overview]
Message-ID: <20061107081748.GA8394166@melbourne.sgi.com> (raw)
In-Reply-To: <20061103154448.GA26647@pc51072.physik.uni-regensburg.de>
On Fri, Nov 03, 2006 at 04:44:48PM +0100, Christian Guggenberger wrote:
> > The superblock:
> >
> > blocksize = 4096
> > dblocks = 18446744070056148512
> > ...
> > agblocks = 84976608
> > agcount = 570
> >
> > An AG is ~43.5GB, so 570 AGs is 24.8TB. It's to big, and
> > we will only shrink by whole AGs. Hence we have to correct
> > agcount and dblocks.
>
> isn't the AG size 'agblocks * blocksize' == ~324 GB here ?
Yes, you are right - I was thinking 512 byte blocks which
then gave the right size that you grew to. Otherwise 570*324GB
gives 200TB, which is somewhat larger than you apparently tried
to grow to...
Sorry for the misdirection, but I'm glad to see that you got
it fixed.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2006-11-07 8:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 17:26 mount failed after xfs_growfs beyond 16 TB Christian Guggenberger
2006-11-02 18:38 ` Eric Sandeen
2006-11-03 9:32 ` Christian Guggenberger
2006-11-03 12:34 ` David Chinner
2006-11-03 15:44 ` Christian Guggenberger
2006-11-03 15:54 ` Eric Sandeen
2006-11-06 13:41 ` Christian Guggenberger
2006-11-07 8:17 ` David Chinner [this message]
2006-11-03 0:41 ` David Chinner
2006-11-03 14:54 ` Eric Sandeen
2006-11-06 1:15 ` Timothy Shimmin
2006-11-06 3:25 ` Eric Sandeen
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=20061107081748.GA8394166@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=christian.guggenberger@physik.uni-regensburg.de \
--cc=sandeen@sandeen.net \
--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