From: David Chinner <dgc@sgi.com>
To: Mark Magpayo <mmagpayo@purevideo.com>
Cc: xfs@oss.sgi.com
Subject: Re: Repairing a possibly incomplete xfs_growfs command?
Date: Thu, 17 Jan 2008 14:01:11 +1100 [thread overview]
Message-ID: <20080117030111.GH155259@sgi.com> (raw)
In-Reply-To: <9CE70E6ED2C2F64FB5537A2973FA4F0253594C@pvn-3001.purevideo.local>
On Wed, Jan 16, 2008 at 03:19:19PM -0800, Mark Magpayo wrote:
> Hi,
>
> So I have run across a strange situation which I hope there are some
> gurus out there to help.
>
> The original setup was a logical volume of 8.9TB. I extended the volume
> to 17.7TB and attempted to run xfs_growfs. I am not sure whether the
> command actually finished, as after I ran the command, the metadata was
> displayed, but there was no nothing that stated the the number of data
> blocks had changed. I was just returned to the prompt, so I'm not sure
> whether the command completed or not..
Hmmm - what kernel and what version of xfsprogs are you using?
(xfs_growfs -V).
Also, can you post the output of the growfs command if you still
have it?
If not, the output of:
# xfs_db -r -c 'sb 0' -c p <device>
# xfs_db -r -c 'sb 1' -c p <device>
because:
> I was unable write to the logical volume I had just created. I tried to
> remount it, but I kept getting an error saying the superblock could not
> be read. I tried running an xfs_repair on the filesystem, and get the
> following:
>
> Phase 1 - find and verify superblock...
> superblock read failed, offset 19504058859520, size 2048, ag 64, rval 0
That's a weird size for a superblock, and I suspect you should only
have AG's numbered 0-63 in your filesystem. (a 8.9TB filesystem will
have 32 AGs (0-31) by default, and doubling the size will take it
up to 64).
> I am not very experienced with xfs (I was following commands in some
> documentaion), and I was recommended to post to this mailing list. If
> anyone could provide some help, it would be greatly appreciate. Also,
> if there is any information I can provide to help, I will gladly provide
> it. Thanks in advance!
Seeing as the filesystem has not mounted, I think this should be
recoverable if you don't try to mount or write anything to the
filesystem until we fix the geometry back up....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-01-17 3:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 23:19 Repairing a possibly incomplete xfs_growfs command? Mark Magpayo
2008-01-17 2:31 ` Eric Sandeen
2008-01-17 3:01 ` David Chinner [this message]
2008-01-17 17:29 ` Mark Magpayo
2008-01-17 19:10 ` Eric Sandeen
2008-01-17 20:04 ` Mark Magpayo
2008-01-17 22:19 ` Eric Sandeen
2008-01-17 22:47 ` Nathan Scott
2008-01-17 23:15 ` David Chinner
2008-01-17 23:29 ` Mark Magpayo
2008-01-17 23:46 ` David Chinner
2008-01-18 17:50 ` Mark Magpayo
2008-01-18 18:34 ` Eric Sandeen
2008-01-19 0:40 ` David Chinner
2008-01-22 19:40 ` Mark Magpayo
2008-01-22 21:13 ` David Chinner
2008-01-22 21:46 ` Mark Magpayo
2008-01-22 22:48 ` Mark Goodwin
2008-01-22 22:50 ` Mark Magpayo
2008-01-23 2:57 ` Barry Naujok
2008-01-23 17:24 ` Mark Magpayo
2008-01-24 1:02 ` Barry Naujok
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=20080117030111.GH155259@sgi.com \
--to=dgc@sgi.com \
--cc=mmagpayo@purevideo.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