Skip to contentSkip to conversation

hfsplus: add necessary declarations for journal replay

PATCH Superseded Vyacheslav Dubeyko 3 participants 11 messages Feb 12, 2014 – Feb 15, 2014

Subsystems (2)

v3 of 4 Superseded Latest is v4 →

lore
Share & tools
lore

Vyacheslav Dubeyko

author maintainer
#0 lore raw

PATCH v3 1/15 hfsplus: add necessary declarations for journal replay

From: Vyacheslav Dubeyko <[email protected]>
Subject: [PATCH v3 01/15] hfsplus: add necessary declarations for journal replay

The patch adds necessary declarations of HFS+ journal's on-disk structures, declaration of structure for journal's object in memory and different journal related flags.

If HFSPLUS_VOL_JOURNALED is set in the volume header's attributes field, the volume has a journal. The journal data stuctures consist of a journal info block, journal header, and journal buffer. The journal info block indicates the location and size of the journal header and journal buffer. The journal buffer is the space set aside to hold transactions. The journal header describes which part of the journal buffer is active and contains transactions waiting to be committed.

A single transaction consists of several blocks, including both the data to be written, and the location where that data is to be written. This is represented on disk by a block list header, which describes the number and sizes of the blocks, immediately followed by the contents of those blocks.

The journal info block (struct hfsplus_journal_info_block) is big-endian structure. The rest structures of HFS+ journal (struct hfsplus_journal_header, struct hfsplus_blhdr, struct hfsplus_block_info) are little-endian.

---
 fs/hfsplus/hfsplus_fs.h  |   23 ++++++++++++++++++++
 fs/hfsplus/hfsplus_raw.h |   53 +++++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 75 insertions(+), 1 deletion(-)
fs/hfsplus/hfsplus_fs.h +23 -0
index 08846425b..18ca92c 100644
@@ -31,6 +31,11 @@
 #define DBG_BITMAP	0x00000040
 #define DBG_ATTR_MOD	0x00000080
 #define DBG_ACL_MOD	0x00000100
+#define DBG_JOURNAL	0x00000200
+#define DBG_JREPLAY	0x00000400
+#define DBG_JTRANS	0x00000800
+#define DBG_JCOMMIT	0x00001000
+#define DBG_JCHKPT	0x00002000
 
 #if 0
 #define DBG_MASK	(DBG_EXTENT|DBG_INODE|DBG_BNODE_MOD)
@@ -126,6 +131,23 @@ struct hfs_bnode {
 #define HFS_BNODE_DIRTY		3
 #define HFS_BNODE_DELETED	4
 
+/* An HFS+ Journal held in memory */
+struct hfsplus_journal {
+	struct mutex jnl_lock;
+
+	/* Journal info block specific */
+	void *jib_buf;
+	struct hfsplus_journal_info_block *jib;
+
+	/* Journal header specific */
+	void *jh_buf;
+	struct hfsplus_journal_header *jh;
+
+	/* TODO: Pointer of JBD */
+
+	struct super_block *sbp;
+};
+
 /*
  * Attributes file states
  */
@@ -146,6 +168,7 @@ struct hfsplus_sb_info {
 	struct hfsplus_vh *s_vhdr;
 	void *s_backup_vhdr_buf;
 	struct hfsplus_vh *s_backup_vhdr;
+	struct hfsplus_journal *jnl;
 	struct hfs_btree *ext_tree;
 	struct hfs_btree *cat_tree;
 	struct hfs_btree *attr_tree;
fs/hfsplus/hfsplus_raw.h +52 -1

69 lines not on this page · raw message

Signature · 1 line
1.7.9.5
#1 lore raw
Quoted 15 lines · Vyacheslav Dubeyko

From: Vyacheslav Dubeyko <[email protected]>
Subject: [PATCH v3 01/15] hfsplus: add necessary declarations for journal replay

The patch adds necessary declarations of HFS+ journal's on-disk structures, declaration of structure for journal's object in memory and different journal related flags.

If HFSPLUS_VOL_JOURNALED is set in the volume header's attributes field, the volume has a journal. The journal data stuctures consist of a journal info block, journal header, and journal buffer. The journal info block indicates the location and size of the journal header and journal buffer. The journal buffer is the space set aside to hold transactions. The journal header describes which part of the journal buffer is active and contains transactions waiting to be committed.

Quoted 8 lines

A single transaction consists of several blocks, including both the data to be written, and the location where that data is to be written. This is represented on disk by a block list header, which describes the number and sizes of the blocks, immediately followed by the contents of those blocks.

The journal info block (struct hfsplus_journal_info_block) is big-endian structure. The rest structures of HFS+ journal (struct hfsplus_journal_header, struct hfsplus_blhdr, struct hfsplus_block_info) are little-endian.

Journal header and block lists are either big-endian or little-endian. See JOURNAL_NEED_SWAP in Apple's code.

Quoted 89 lines
---
 fs/hfsplus/hfsplus_fs.h  |   23 ++++++++++++++++++++
 fs/hfsplus/hfsplus_raw.h |   53 +++++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 75 insertions(+), 1 deletion(-)
fs/hfsplus/hfsplus_fs.h +23 -0
index 08846425b..18ca92c 100644
@@ -31,6 +31,11 @@
 #define DBG_BITMAP     0x00000040
 #define DBG_ATTR_MOD   0x00000080
 #define DBG_ACL_MOD    0x00000100
+#define DBG_JOURNAL    0x00000200
+#define DBG_JREPLAY    0x00000400
+#define DBG_JTRANS     0x00000800
+#define DBG_JCOMMIT    0x00001000
+#define DBG_JCHKPT     0x00002000
 
 #if 0
 #define DBG_MASK       (DBG_EXTENT|DBG_INODE|DBG_BNODE_MOD)
@@ -126,6 +131,23 @@ struct hfs_bnode {
 #define HFS_BNODE_DIRTY                3
 #define HFS_BNODE_DELETED      4
 
+/* An HFS+ Journal held in memory */
+struct hfsplus_journal {
+       struct mutex jnl_lock;
+
+       /* Journal info block specific */
+       void *jib_buf;
+       struct hfsplus_journal_info_block *jib;
+
+       /* Journal header specific */
+       void *jh_buf;
+       struct hfsplus_journal_header *jh;
+
+       /* TODO: Pointer of JBD */
+
+       struct super_block *sbp;
+};
+
 /*
  * Attributes file states
  */
@@ -146,6 +168,7 @@ struct hfsplus_sb_info {
        struct hfsplus_vh *s_vhdr;
        void *s_backup_vhdr_buf;
        struct hfsplus_vh *s_backup_vhdr;
+       struct hfsplus_journal *jnl;
        struct hfs_btree *ext_tree;
        struct hfs_btree *cat_tree;
        struct hfs_btree *attr_tree;
fs/hfsplus/hfsplus_raw.h +9 -1
index 8ffb3a8..a50ad9d 100644
@@ -46,6 +46,7 @@
 #define HFSP_SYMLINK_CREATOR   0x72686170      /* 'rhap' */
 
 #define HFSP_MOUNT_VERSION     0x482b4c78      /* 'H+Lx' */
+#define HFSP_MOUNT_JOURNALED_VERSION 0x4846534A        /* 'HFSJ' */
 
 /* Structures used on disk */
 
@@ -105,7 +106,7 @@ struct hfsplus_vh {
        __be16 version;
        __be32 attributes;
        __be32 last_mount_vers;
-       u32 reserved;
+       __be32 journal_info_block;
 
        __be32 create_date;
        __be32 modify_date;
@@ -401,4 +402,54 @@ typedef union {
        struct hfsplus_attr_key attr;
 } __packed hfsplus_btree_key;
 
+/* HFS+ on-disk journal structures */
+struct hfsplus_journal_info_block {
+#define HFSPLUS_JOURNAL_IN_FS          0x01
+#define HFSPLUS_JOURNAL_ON_OTHER_DEVICE        0x02
+#define HFSPLUS_JOURNAL_NEED_INIT      0x04
+       __be32 flags;
+       __be32 device_signature[8];

fs/hfsplus/hfsplus_raw.h typedef union { · line 421

Quoted 10 lines
fs/hfsplus/hfsplus_raw.h +10 -0
+       __be64 offset;
+       __be64 size;
+       u32 reserved[32];
+} __packed;
+
+/* Valid magic and endian value */
+#define HFSPLUS_JOURNAL_HEADER_MAGIC   0x4A4E4C78
+#define HFSPLUS_JOURNAL_HEADER_ENDIAN  0x12345678
+
+/* !!! Litle-endian structure !!! */

Not necessarily little-endian.

Quoted 25 lines
fs/hfsplus/hfsplus_raw.h +25 -0
+struct hfsplus_journal_header {
+       __le32 magic;
+       __le32 endian;
+       __le64 start;
+       __le64 end;
+       __le64 size; /* Includes the header and the buffer */
+       __le32 blhdr_size;
+       __le32 checksum;
+       __le32 jhdr_size;
+} __packed;
+
+/* !!! Litle-endian structure !!! */
+struct hfsplus_block_info {
+       __le64 bnum;
+       __le32 bsize;
+       union {
+               __le32 checksum;
+               __le32 seq_num; /* only used in binfo[0] */
+       } block;
+} __packed;
+
+/* !!! Litle-endian structure !!! */
+struct hfsplus_blhdr {
+       __le16 max_blocks;
+       __le16 num_blocks;

fs/hfsplus/hfsplus_raw.h typedef union {

Quoted 10 lines
fs/hfsplus/hfsplus_raw.h +8 -1
+       __le32 bytes_used;
+       __le32 checksum;
+#define HFSPLUS_BLHDR_CHECK_CHECKSUMS  0x0001
+#define HFSPLUS_BLHDR_FIRST_HEADER     0x0002
+       __le32 flags;
+       struct hfsplus_block_info binfo[1];
+} __packed;
+
 #endif
--

So in your patchset functions hfsplus_verify_journal_header() etc. refuse to understand BE journal.

author maintainer
#2 lore raw
Quoted 6 lines · Sergei Antonov
Quoted 3 lines

The journal info block (struct hfsplus_journal_info_block) is big-endian structure. The rest structures of HFS+ journal (struct hfsplus_journal_header, struct hfsplus_blhdr, struct hfsplus_block_info) are little-endian.

Journal header and block lists are either big-endian or little-endian. See JOURNAL_NEED_SWAP in Apple's code.

Do you know how to create journal with BE internal structures? Or have you examples of journal with such structures? I haven't such examples. And I can't see such opportunities in newfs_hfs tool. So, I don't think that Journal header and block lists can be not little-endian. I can't implement or test something unreal. Could you share the way of creation HFS+ journal with big-endian Journal header and block lists?

Thanks,
Vyacheaslav Dubeyko.

#3 lore raw
Quoted 10 lines · Vyacheslav Dubeyko
Quoted 6 lines · Sergei Antonov
Quoted 3 lines

The journal info block (struct hfsplus_journal_info_block) is big-endian structure. The rest structures of HFS+ journal (struct hfsplus_journal_header, struct hfsplus_blhdr, struct hfsplus_block_info) are little-endian.

Journal header and block lists are either big-endian or little-endian. See JOURNAL_NEED_SWAP in Apple's code.

Do you know how to create journal with BE internal structures?

You need a PowerPC Mac I guess.

Quoted 1 line

And I can't see such opportunities in newfs_hfs tool.

Ha! New_hfs does not initialize journal at all.

Quoted 2 lines

Could you share the way of creation
HFS+ journal with big-endian Journal header and block lists?

As I said, header and block lists are BE.

author maintainer
#4 lore raw
Quoted 7 lines · Sergei Antonov
Quoted 6 lines · Vyacheslav Dubeyko
Quoted 4 lines · Sergei Antonov
Quoted 3 lines

The journal info block (struct hfsplus_journal_info_block) is big-endian structure. The rest structures of HFS+ journal (struct hfsplus_journal_header, struct hfsplus_blhdr, struct hfsplus_block_info) are little-endian.

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

Journal header and block lists are either big-endian or little-endian. See JOURNAL_NEED_SWAP in Apple's code.

Do you know how to create journal with BE internal structures?

You need a PowerPC Mac I guess.

You guess or you know? Please, share concrete way.

Quoted 4 lines
Quoted 1 line

And I can't see such opportunities in newfs_hfs tool.

Ha! New_hfs does not initialize journal at all.

Namely, newfs_hfs create journal. Otherwise, what tool does it?

Quoted 4 lines
Quoted 2 lines

Could you share the way of creation
HFS+ journal with big-endian Journal header and block lists?

As I said, header and block lists are BE.

I can only repeat. Could you share the way of creation HFS+ journal with big-endian Journal header and block lists?

Thanks,
Vyacheslav Dubeyko.

#5 lore raw
Quoted 30 lines · Vyacheslav Dubeyko
Quoted 7 lines · Sergei Antonov
Quoted 6 lines · Vyacheslav Dubeyko
Quoted 4 lines · Sergei Antonov
Quoted 3 lines

The journal info block (struct hfsplus_journal_info_block) is big-endian structure. The rest structures of HFS+ journal (struct hfsplus_journal_header, struct hfsplus_blhdr, struct hfsplus_block_info) are little-endian.

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

Journal header and block lists are either big-endian or little-endian. See JOURNAL_NEED_SWAP in Apple's code.

Do you know how to create journal with BE internal structures?

You need a PowerPC Mac I guess.

You guess or you know? Please, share concrete way.

Quoted 4 lines
Quoted 1 line

And I can't see such opportunities in newfs_hfs tool.

Ha! New_hfs does not initialize journal at all.

Namely, newfs_hfs create journal. Otherwise, what tool does it?

Quoted 3 lines
Quoted 2 lines

Could you share the way of creation
HFS+ journal with big-endian Journal header and block lists?

Quoted 7 lines
Quoted 1 line

As I said, header and block lists are BE.

I can only repeat. Could you share the way of creation HFS+ journal with big-endian Journal header and block lists?

Thanks,
Vyacheslav Dubeyko.

I saw big-endian journal on Panther installed on PearPC emulator.

author maintainer
#6 lore raw
Quoted 8 lines · Sergei Antonov
Quoted 6 lines

I can only repeat. Could you share the way of creation HFS+ journal with big-endian Journal header and block lists?

Thanks,
Vyacheslav Dubeyko.

I saw big-endian journal on Panther installed on PearPC emulator.

I need to have HFS+ volume with big-endian journal in my hand or clear description of creation way of such HFS+ volume.

Frankly speaking, I haven't time for installation of some emulator. So, I would like to have ready image of HFS+ volume in my hand.

Thanks,
Vyacheslav Dubeyko.

#7 lore raw
In reply to Vyacheslav Dubeyko

--------------------------------------------
On Wed, 12/2/14, Vyacheslav Dubeyko <[email protected]> wrote:

Subject: Re: [PATCH v3 01/15] hfsplus: add necessary declarations for journal replay
To: "Sergei Antonov" <[email protected]>
Cc: "Linux FS devel list" <[email protected]>, "Al Viro" <[email protected]>, "ChristophHellwig" <[email protected]>, "Hin-Tak Leung" <[email protected]>, "Andrew Morton" <[email protected]>
Date: Wednesday, 12 February, 2014, 17:59

Quoted 1 line · Sergei Antonov

On 12 February 2014 17:38, Vyacheslav Dubeyko <[email protected]>

Quoted 1 line · wrote:
Quoted 1 line

On Wed, 2014-02-12 at 17:15 +0100, Sergei Antonov

Quoted 2 lines · wrote:
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

The journal info block (struct

hfsplus_journal_info_block) is big-endian

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

structure. The rest structures of HFS+

journal (struct hfsplus_journal_header,

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

struct hfsplus_blhdr, struct

hfsplus_block_info) are little-endian.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Journal header and block lists are either

big-endian or little-endian.

Quoted 3 lines
Quoted 3 lines
Quoted 1 line

See JOURNAL_NEED_SWAP in Apple's code.

Do you know how to create journal with BE internal

structures?

Quoted 3 lines

You need a PowerPC Mac I guess.

You guess or you know? Please, share concrete way.

Quoted 1 line
Quoted 1 line

And I can't see such opportunities in newfs_hfs

tool.

Quoted 3 lines

Ha! New_hfs does not initialize journal at all.

Namely, newfs_hfs create journal. Otherwise, what tool does it?

Quoted 2 lines
Quoted 2 lines

Could you share the way of creation
HFS+ journal with big-endian Journal header and

block lists?

Quoted 2 lines

As I said, header and block lists are BE.

I can only repeat. Could you share the way of creation HFS+ journal
with big-endian Journal header and block lists?

Thanks,
Vyacheslav Dubeyko.

Hi all,

I Have mentioned earlier that I have the powerpc version of Darwin 8 (equivalent to Mac OS X 10.4) running inside pearpc, and have other uses of it and therefore have given it some use. I can look into this - and probably will, when I try v3 of Vyacheslav's patch set.

Darwin 8 does certainly noticed it was uncleanly shut down and display a message about journal replay the next time it starts; also it seems to notice the journal had been played with by somebody else - there is a message about invalid/invalidating journal entries when I ran fsck.hfsplus manually between unclean shut down and restart. (That's assuming fsck.hfsplus can cope with disk images written by the powerpc version of darwin 8 correctly, one way or another - I should hope so, as it is not unthinkable for a mac user to own both kind of macs).

So it appears that the journal is not emptied by fsck.hfsplus, but simply marked done and no longer relevant, and the darwin kernel code notices that.

HTH.

Hin-Tak

author maintainer
#8 lore raw
Quoted 7 lines · Hin-Tak Leung

Hi all,

I Have mentioned earlier that I have the powerpc version of Darwin 8 (equivalent to Mac OS X 10.4) running inside pearpc, and have other uses of it and therefore have given it some use. I can look into this - and probably will, when I try v3 of Vyacheslav's patch set.

So, had you any error messages when you tried patchset v3? If you really have HFS+ volume with big-endian structures in journal then failure with journal replay or volume corruption is inevitable.

Quoted 11 lines

Darwin 8 does certainly noticed it was uncleanly shut down and display a message about journal replay the next time it starts; also it seems to notice the journal had been played with by somebody else - there is a message about invalid/invalidating journal entries when I ran fsck.hfsplus manually between unclean shut down and restart. (That's assuming fsck.hfsplus can cope with disk images written by the powerpc version of darwin 8 correctly, one way or another - I should hope so, as it is not unthinkable for a mac user to own both kind of macs).

So it appears that the journal is not emptied by fsck.hfsplus, but simply marked done and no longer relevant, and the darwin kernel code notices that.

As far as I can judge, fsck tool doesn't replay journal, usually. It need to take into account presence of journal with transactions. But namely file system driver is responsible for journal replay. And, as I remember correctly, fsck.hfsplus claims about presence of journal and it suggests to use force option for volume checking in such case.

Thanks,
Vyacheslav Dubeyko.

#9 lore raw

--------------------------------------------
On Fri, 14/2/14, Vyacheslav Dubeyko <[email protected]> wrote:

Subject: Re: [PATCH v3 01/15] hfsplus: add necessary declarations for journal replay
To: [email protected]
Cc: "Sergei Antonov" <[email protected]>, "Linux FS devel list" <[email protected]>, "Al Viro" <[email protected]>, "ChristophHellwig" <[email protected]>, "Andrew Morton" <[email protected]>
Date: Friday, 14 February, 2014, 7:22

Quoted 4 lines · Hin-Tak Leung


  Hi all,

I Have mentioned earlier that I have the powerpc

version of Darwin 8 (equivalent

Quoted 1 line

to Mac OS X 10.4) running inside pearpc, and have other

uses of it and therefore have given it

Quoted 1 line

some use. I can look into this - and probably will,

when I try v3 of  Vyacheslav's patch set.

Quoted 1 line

So, had you any error messages when you tried patchset v3? If you really
have HFS+ volume with big-endian structures in journal then failure with
journal replay or volume corruption is inevitable.

Quoted 1 line

Darwin 8 does certainly noticed it was uncleanly shut

down and display a message about

Quoted 1 line

journal replay the next time it starts; also it seems

to notice the journal had been played

Quoted 1 line

with by somebody else - there is a message about

invalid/invalidating journal entries

Quoted 1 line

when I ran fsck.hfsplus manually between unclean shut

down and restart.

Quoted 1 line

(That's assuming  fsck.hfsplus can cope with disk

images written by the powerpc

Quoted 1 line

version of darwin 8 correctly, one way or another - I

should hope so, as it is

Quoted 1 line

not unthinkable for a mac user to own both kind of

macs).

Quoted 2 lines

So it appears that the journal is not emptied by

fsck.hfsplus, but simply marked done

Quoted 1 line

and no longer relevant, and the darwin kernel code

notices that.

Quoted 1 line

As far as I can judge, fsck tool doesn't replay journal, usually. It
need to take into account presence of journal with transactions. But
namely file system driver is responsible for journal replay. And, as I
remember correctly, fsck.hfsplus claims about presence of journal and it
suggests to use force option for volume checking in such case.

Thanks,
Vyacheslav Dubeyko.

Hi Vyacheslav,

I am afraid I have bad news for you - Sergei may be right.

This is what shows on an unclean-shutdown image:

[179982.068363] hfsplus: invalid journal header
[179982.068375] hfsplus: journal replay failed, mounting read-only
[179982.068378] hfsplus: filesystem was not cleanly unmounted, mounting read-only
[179982.068380] hfsplus: running fsck.hfsplus is recommended

This is on the clean shutdown after:

[182188.224271] hfsplus: invalid journal header
[182188.224287] hfsplus: journal replay failed, mounting read-only

Obviously my virtual machine is still working, so the file system
must be valid.
I have also recorded that the darwin kernel outputs this when replaying the journal:

 Feb 14 19:15:55 localhost kernel[0]: jnl: replay_journal: from: 3365376 to: 2762752 (joffset 0x1a000)

which might be interesting to try to replicate.

The good news is I have saved the unclean image, and the clean one after, they compress to just over 600MB each (and expands to 3GB each).
Since they are just darwin 8 (plus some open-source software I tried to work on within) and *not* full Mac OS X, I suppose you can have them, if you
can find the space for me to upload them to.

As I mentioned earlier that the darwin kernel seems to notice that its filesystem had been manipulated by fsck.hfsplus. To be precise, it seems
that whenever I had done a fsck.hfsplus between, the darwin kernel outputs this kind of message:

Feb 12 07:23:20 localhost kernel[0]: jnl: journal start/end pointers reset! (jnl 0x1838e60; s 0x232a00 e 0x722600)
Feb 12 15:22:37 localhost kernel[0]: jnl: journal start/end pointers reset! (jnl 0x17dbe60; s 0x96600 e 0x322600)

So it might be also worth looking at the XNU source what that means, and whether fsck.hfsplus is behaving correctly on x86_64 linux on manipulating powerpc HFS+ images.

OTOH, I am happy if you have debug patches, etc to try thing out at this end.

Hin-Tak

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

author maintainer
#10 lore raw

Hi Hin-Tak,

Quoted 12 lines · Hin-Tak Leung

Hi Vyacheslav,

I am afraid I have bad news for you - Sergei may be right.

This is what shows on an unclean-shutdown image:

[179982.068363] hfsplus: invalid journal header
[179982.068375] hfsplus: journal replay failed, mounting read-only
[179982.068378] hfsplus: filesystem was not cleanly unmounted, mounting read-only
[179982.068380] hfsplus: running fsck.hfsplus is recommended
Quoted 5 lines

This is on the clean shutdown after:

[182188.224271] hfsplus: invalid journal header
[182188.224287] hfsplus: journal replay failed, mounting read-only

Ok. Now I can see the issue. :) It is the real evidence. Thank you.

Quoted 5 lines

Obviously my virtual machine is still working, so the file system
must be valid.
I have also recorded that the darwin kernel outputs this when replaying the journal:

 Feb 14 19:15:55 localhost kernel[0]: jnl: replay_journal: from: 3365376 to: 2762752 (joffset 0x1a000)
Quoted 8 lines

which might be interesting to try to replicate.

The good news is I have saved the unclean image, and the clean one after, they compress to just over 600MB each (and expands to 3GB each).
Since they are just darwin 8 (plus some open-source software I tried to work on within) and *not* full Mac OS X, I suppose you can have them, if you
can find the space for me to upload them to.

It is really great. I send you the information about place and credentials for upload in private e-mail.

I am looking forward to have these images in my hands for investigation.

Quoted 5 lines

As I mentioned earlier that the darwin kernel seems to notice that its filesystem had been manipulated by fsck.hfsplus. To be precise, it seems
that whenever I had done a fsck.hfsplus between, the darwin kernel outputs this kind of message:

Quoted 9 lines
Feb 12 07:23:20 localhost kernel[0]: jnl: journal start/end pointers reset! (jnl 0x1838e60; s 0x232a00 e 0x722600)
Feb 12 15:22:37 localhost kernel[0]: jnl: journal start/end pointers reset! (jnl 0x17dbe60; s 0x96600 e 0x322600)

So it might be also worth looking at the XNU source what that means, and whether fsck.hfsplus is behaving correctly on x86_64 linux on manipulating powerpc HFS+ images.

OTOH, I am happy if you have debug patches, etc to try thing out at this end.

Thank you for all efforts. I really appreciate it.

Thanks,
Vyacheslav Dubeyko.