From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: mounting hixfs (Hitachi "tuned" XFS) on 2.6 kernel
Date: Mon, 17 May 2010 23:37:58 -0500 [thread overview]
Message-ID: <4BF219A6.4010900@hardwarefreak.com> (raw)
In-Reply-To: <AANLkTin_WoxWP3JXHvflVVP_2fGzgbSVfpPW1KGiyd1z@mail.gmail.com>
big beer put forth on 5/17/2010 10:34 PM:
>> On Mon, May 17, 2010 at 6:24 PM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>> big beer put forth on 5/17/2010 7:08 PM:
>>
>>> If anyone has any ideas on what to do, and/or where to start, I'd
>>> greatly appreciate it.
>>
>> Why are you avoiding the obvious solution in favor of hacking?
>>
> Sending back to the list this time instead of Stan directly (Sorry Stan) :)
No problem. I love my Tbird "reply-to-list" option. :)
> The obvious solution for me would be a backup or rsync. Unfortunately
> both of those have issues with this particular setup.
>
> Using a backup over the network to migrate will be way too slow
> (days). There are way too many files to index and this poor little nas
> box is already falling over with cpu load from daily activities. I can
> quickly make a mirror on the storage, and move it over to another
> larger host quickly (minutes). Mounting the FS on another machine will
> greatly improve the time and accuracy, as I won't have to worry about
> inconsistencies as it's a block level copy.
> The black-box solution is also very painful to work with, no gcc, no
> automake, no rsync, etc.
> I would also think that for some reason I can't think of, it would be
> nice to have support for this version of XFS be available for free for
> others. Some other poor sap might find some value.
>
> 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.
Seems to me you're taking some big chances with live data. One wrong turn
and you could hose the FS and lose all the data, yes? I'd rather give you
recommendations not related to this current path you're taking. Would you
please provide the model or part number of this Hitachi NAS so I can get an
idea of what exactly it is you're dealing with, and possibly offer other
solutions?
Maybe someone else here can help you pull this off via XFS. I can't. But
I'll gladly spend some time researching other possible solutions, mainly
getting a high capacity drive connected so you can do a cp -a or tar and be
done with this overnight, in a data-safe manner.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-18 4:33 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 [this message]
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=4BF219A6.4010900@hardwarefreak.com \
--to=stan@hardwarefreak.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