From: Eric Sandeen <sandeen@sandeen.net>
To: big beer <bigbeerjr@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: mounting hixfs (Hitachi "tuned" XFS) on 2.6 kernel
Date: Mon, 17 May 2010 23:23:27 -0500 [thread overview]
Message-ID: <4BF2163F.5070908@sandeen.net> (raw)
In-Reply-To: <AANLkTin_WoxWP3JXHvflVVP_2fGzgbSVfpPW1KGiyd1z@mail.gmail.com>
big beer wrote:
> So I went and changed the magic number to 0x58465342 by dumping the
> 1st 512 bytes off the volume, editing, and writing back, now I'm
> getting "Can't verify primary superblock". Using xfs_db to look at the
> other superblocks indeed still shows HXFS. Any advise how I can
> find/dump/re-write one of the other superblocks? I'd like to see if I
> can change another one of them if xfs_repair will run.
You can select each superblock and write it.
xfs_db -x /dev/blah
xfs_db> sb 1
xfs_db> write magicnum 0x58465342
xfs_db> sb 2
xfs_db> write magicnum 0x58465342
...
this could be scripted with -c <command1> -c <command2>
I don't know if they changed anything other than the magic though,
so you get to keep all pieces if it breaks!
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-18 4:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 0:08 mounting hixfs (Hitachi "tuned" XFS) on 2.6 kernel big beer
2010-05-18 1:24 ` Stan Hoeppner
2010-05-18 3:34 ` big beer
2010-05-18 4:21 ` Dave Chinner
2010-05-18 4:23 ` Eric Sandeen [this message]
2010-05-18 4:37 ` Stan Hoeppner
2010-05-18 15:19 ` big beer
2010-05-18 16:44 ` Benjamin Lau
2010-05-18 16:57 ` Roger Willcocks
2010-05-18 22:43 ` big beer
2010-05-19 4:19 ` Stan Hoeppner
2010-05-19 13:53 ` Eric Sandeen
2010-05-19 14:03 ` Stan Hoeppner
2010-05-18 23:34 ` Stan Hoeppner
2010-05-18 3:47 ` 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=4BF2163F.5070908@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bigbeerjr@gmail.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