public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
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 22:47:31 -0500	[thread overview]
Message-ID: <4BF20DD3.50006@sandeen.net> (raw)
In-Reply-To: <AANLkTikek9K8-BqNgee_tXz72beHpWEUl41YtDPrD-3P@mail.gmail.com>

big beer wrote:
> Hello list,
> 
> I seem to find myself in the unlucky situation of having myself some
> hixfs filesystems I'm trying to migrate off of.
> Some background on hixfs (as I understand it).
> At some point in the past, prior to purchasing a NAS company, Hitachi
> decided that they could make their own NAS solution using
> linux/LVM/XFS. They give you a little integrated 2.4 linux blade in
> one of their storage subsystems with a nice (circa yr 2000) web
> frontend to manage samba and nfs serving. The disks that are presented
> to this little guy are encapsulated in LVM and formatted lv's with a
> variant of XFS that is shown as hixfs on the machine. You get a very
> limited shell on this guy and you have to run everything through sudo
> if you want cli access (which is heavily limited).
> 
> I'm in the process of trying to get off said solution and am running
> into some issues getting the file system on this black box to be
> mounted/recognized on a standard 2.6 linux host.
> 
> Here is some output from some xfs tools:
> 
> box ~ # xfs_check /dev/vghorclu00/lvARRAY2
> xfs_check: unexpected XFS SB magic number 0x48584653
> bad superblock magic number 48584653, giving up

'HXFS' - heh.

(58 46 53 42 'XFSB' is the proper magic)

> box ~ # xfs_repair -v /dev/vghorclu00/lvARRAY2
> Phase 1 - find and verify superblock...
> bad primary superblock - bad magic number !!!
> 
> attempting to find secondary superblock... Sorry, could not find valid
> secondary superblock
> Exiting now.
> 
> box ~ # xfs_db /dev/vghorclu00/lvARRAY2
> xfs_db: unexpected XFS SB magic number 0x48584653

...

 
> I would like to be able to get this FS mounted on a box that supports
> vanilla XFS.
> I'm hoping that Hitachi has done something like change the magic
> number so that the normal user land tools will just bail. I've got a
> way to make quick copies of this FS so I am fair game to experiment on
> it.
> 
> I've made some calls to Hitachi to find out what the deal is, so far
> no one there has been very helpful, nor provided me with any insight
> to getting these mounted. I'm thinking that since XFS is GPL'd and
> they made extensions to it, and sold it, they should at least provide
> source for their user land tools/kernel module for the FS. Unless they
> licensed it from SGI?

I can't speak to that, I dunno.
 
> I should note that on their black box solution they've got a different
> set of user land tools all prefixed with "hi" (hixfs_db, hixfs_repair,
> etc). While I do have ways to grab their userland tools, the kernel
> module is for 2.4 so I don't think I'll have much luck just c&p
> everything over.
> 
> If anyone has any ideas on what to do, and/or where to start, I'd
> greatly appreciate it.
> 
> Thanks!

*shrug* could try rewriting the magic with xfs_db and then having your
way with it, see if that works.

Or, just copy off this "solution" onto a new filesystem? :)

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2010-05-18  3:45 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
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 [this message]

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=4BF20DD3.50006@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