From: Eric Sandeen <sandeen@sandeen.net>
To: christian.guggenberger@physik.uni-regensburg.de
Cc: David Chinner <dgc@sgi.com>, xfs@oss.sgi.com
Subject: Re: mount failed after xfs_growfs beyond 16 TB
Date: Fri, 03 Nov 2006 09:54:51 -0600 [thread overview]
Message-ID: <454B664B.6030701@sandeen.net> (raw)
In-Reply-To: <20061103154448.GA26647@pc51072.physik.uni-regensburg.de>
Christian Guggenberger wrote:
>> xfs_db mojo.... ;)
>>
>> Note - no guarantee this will work - practise on an expendable
>> sparse loopback filessytem image by making a filesystem of slightly less
>> than 16TB then growing it to corrupt it the same way and then fixing it up
>> successfully.
>>
>> Once it's corrupted, unmount and run xfs_db in expert mode.
>> 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 ?
>
> got further input on a secondray superblock form the colleague:
> looks more reasonable, I'd say. Is there a way to manually recover sb0
> from sb1 ?
you can copy it over field-by-field.... not sure if there's an easier way.
-Eric
next prev parent reply other threads:[~2006-11-03 15:55 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 [this message]
2006-11-06 13:41 ` Christian Guggenberger
2006-11-07 8:17 ` David Chinner
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=454B664B.6030701@sandeen.net \
--to=sandeen@sandeen.net \
--cc=christian.guggenberger@physik.uni-regensburg.de \
--cc=dgc@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