From: Nathan Scott <nscott@aconex.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Mark Magpayo <mmagpayo@purevideo.com>,
David Chinner <dgc@sgi.com>,
xfs@oss.sgi.com
Subject: Re: Repairing a possibly incomplete xfs_growfs command?
Date: Fri, 18 Jan 2008 09:47:34 +1100 [thread overview]
Message-ID: <1200610054.9463.218.camel@edge.scott.net.au> (raw)
In-Reply-To: <478FD48F.1060707@sandeen.net>
On Thu, 2008-01-17 at 16:19 -0600, Eric Sandeen wrote:
>
> Yep, in 1k units, so:
>
> 19046932480*1024
> 19504058859520
>
> and:
>
> superblock read failed, offset 19504058859520, size 2048, ag 64, rval
> 0
>
> so it's trying to read a 2k (?) superblock right in the last 1k of the
> device? Hrm. (Dave, Barry - isn't that 2048 the sector size, not
> block
> size?)
>
> Also from your sb 0 printout:
>
> blocksize = 4096
> dblocks = 11904332800
sectsize = 512
sectlog = 9
So, SB reckons its a regular 512 byte sector size. Perhaps the device
driver is reporting a 2K sector size from the BLKSSZGET ioctl? That'd
be wierd, cos mkfs would have issued a warning when creating with 512
byte sectors. *shrug*.
> is 48760147148800, exactly 2.5x bigger than your device is. Weird.
cheers.
--
Nathan
next prev parent reply other threads:[~2008-01-17 22:44 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
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 [this message]
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=1200610054.9463.218.camel@edge.scott.net.au \
--to=nscott@aconex.com \
--cc=dgc@sgi.com \
--cc=mmagpayo@purevideo.com \
--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