From: Eric Sandeen <sandeen@sandeen.net>
To: johahoff <jh@not-dark-yet.de>
Cc: xfs@oss.sgi.com
Subject: Re: Fwd: xfs - fixing wrong xfs size
Date: Mon, 15 Nov 2010 10:26:33 -0600 [thread overview]
Message-ID: <4CE15F39.2010904@sandeen.net> (raw)
In-Reply-To: <30211747.post@talk.nabble.com>
On 11/14/10 5:16 AM, johahoff wrote:
>
>> You can use xfs_db to set it; or you could comment out the kernel
>> check... and mount readonly, and copy off the data you can get to?
>
> I have got the same problem after recovering a xfs volume using ddrescue. It
> seems that the new 1 TB drive I dd'ed to is a few blocks short ...
>
> I had a look at the xfs_db man page, but wasn't able to figure out which
> command would allow me to set the block count of the fs. Can you please give
> the appropriate commands? I think I'll be able to figure out the correct
> counts on my own.
>
> Thanks a lot!
>
> -Johannes
# xfs_db -w /dev/blah
xfs_db> sb 0
xfs_db> p
...
magicnum = 0x58465342
blocksize = 4096
dblocks = XXXXXX
...
xfs_db> w dblocks <NEW VALUE>
xfs_db> quit
You may have to do it for each of the superblocks but I think the first
should suffice.
If files reference the blocks past the device then of course you'll hit
errors trying to read them as well ...
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-15 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 14:13 xfs - fixing wrong xfs size Nebojsa Trpkovic
2009-04-13 15:02 ` Eric Sandeen
[not found] ` <dbd747120904130913p45c2979eu5afd15f5a6ca7b7f@mail.gmail.com>
2009-04-13 16:33 ` Fwd: " Nebojsa Trpkovic
2010-05-05 20:09 ` Rafal Blaszczyk
2010-05-05 22:12 ` Eric Sandeen
2010-05-05 22:22 ` Eric Sandeen
2010-11-14 11:16 ` johahoff
2010-11-15 16:26 ` Eric Sandeen [this message]
2010-12-19 14:37 ` johahoff
2010-12-19 17:27 ` 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=4CE15F39.2010904@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jh@not-dark-yet.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.