public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Mark Magpayo <mmagpayo@purevideo.com>
Cc: xfs@oss.sgi.com
Subject: Re: Repairing a possibly incomplete xfs_growfs command?
Date: Wed, 16 Jan 2008 20:31:08 -0600	[thread overview]
Message-ID: <478EBDEC.2070305@sandeen.net> (raw)
In-Reply-To: <9CE70E6ED2C2F64FB5537A2973FA4F0253594C@pvn-3001.purevideo.local>

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..
> 
> 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
> 
> fatal error -- Invalid argument

hm, how big is your block device for starters - look in /proc/partitions.

-Eric

  reply	other threads:[~2008-01-17  2:31 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 [this message]
2008-01-17  3:01 ` David Chinner
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=478EBDEC.2070305@sandeen.net \
    --to=sandeen@sandeen.net \
    --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