From: NeilBrown <neilb@suse.com>
To: Alfred Matthews <asm13243546@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: on assembly and recovery of a hardware RAID
Date: Fri, 12 May 2017 08:27:06 +1000 [thread overview]
Message-ID: <87o9uzkp1h.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAAZLhTf=GHmSDcY8Eb9SzevofFbDD7f-N8DKZiFkq9j2XV4mQA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2533 bytes --]
On Wed, May 03 2017, Alfred Matthews wrote:
> Sorry to disappear for a bit.
>
> Of necessity I've migrated to another working system and I'm in Arch.
> Utility here is fsck.hfs as opposed to hpfsck. I'd like to post that
> output.
I wonder if they are the same thing, or completely different.
>
> mdadm --build /dev/md0 --level=0 -n2 --chunk=8K /dev/sdb2 /dev/sdc2
>
> works, then,
>
> fsck.hfs -v /dev/md0
> *** Checking volume MDB
> drSigWord = 0xffffffff
> drCrDate = Mon Feb 6 06:28:15 2040
> drLsMod = Mon Feb 6 06:28:15 2040
> drAtrb = BUSY | HLOCKED | UMOUNTED | BBSPARED | BVINCONSIS |
> COPYPROT | SLOCKED
> drNmFls = 65535
> drVBMSt = 65535
> drAllocPtr = 65535
> drNmAlBlks = 65535
> drAlBlkSiz = 4294967295
> drClpSiz = 4294967295
> drAlBlSt = 65535
> drNxtCNID = 4294967295
> drFreeBks = 65535
> drVN = ""
> drVolBkUp = Mon Feb 6 06:28:15 2040
> drVSeqNum = 4294967295
> drWrCnt = 4294967295
> drXTClpSiz = 4294967295
> drCTClpSiz = 4294967295
> drNmRtDirs = 65535
> drFilCnt = 4294967295
> drDirCnt = 4294967295
> drEmbedSigWord = 0xffff
> drEmbedExtent = 65535[65535..131069]
> drXTFlSize = 4294967295
> drXTExtRec =
> 65535[65535..131069]+65535[65535..131069]+65535[65535..131069]
> drCTFlSize = 4294967295
> drCTExtRec =
> 65535[65535..131069]+65535[65535..131069]+65535[65535..131069]
> Bad volume signature (0xffffffff); should be 0x4244. Fix? y
> Volume creation date is in the future (Mon Feb 6 06:28:15 2040). Fix? y
> Volume last modify date is in the future (Mon Feb 6 06:28:15 2040). Fix? y
> Volume bitmap starts at unusual location (1), not 3. Fix? y
> *** Checking volume structure
> *** Checking extents overflow B*-tree
>
> It's possible that I was unwise in accepting the changes from fsck.
Definitely possible.
Given how many of the numbers listed above are 0xffff or 0xffffffff, it
is unlikely that the tool found anything useful.
>
>>>
>>> How is your C coding? You could
>>> apt-get source hfsplus
>>> and hack the code and try to build it yourself....
>>>
>
> Still fine. By now not clear if this is what's needed.
I don't think I can be of further help, sorry.
NeilBrown
>
> Al
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-05-11 22:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 20:37 on assembly and recovery of a hardware RAID Alfred Matthews
2017-03-13 21:32 ` NeilBrown
2017-03-14 17:27 ` Alfred Matthews
2017-03-15 2:56 ` NeilBrown
2017-03-18 17:11 ` Alfred Matthews
2017-03-18 18:08 ` Alfred Matthews
2017-03-20 5:34 ` NeilBrown
2017-03-20 21:42 ` Alfred Matthews
2017-03-21 2:38 ` NeilBrown
2017-03-21 12:09 ` Alfred Matthews
2017-05-03 15:44 ` Alfred Matthews
2017-05-11 17:18 ` Alfred Matthews
2017-05-11 22:27 ` NeilBrown [this message]
2017-05-12 15:57 ` Alfred Matthews
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=87o9uzkp1h.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=asm13243546@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).