Re: [PATCH v3 01/15] hfsplus: add necessary declarations for journal replay

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Hin-Tak,

On Sat, 2014-02-15 at 04:04 +0000, Hin-Tak Leung wrote:
>  
> 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
> 

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

> 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.
> 

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.

> 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.
> 

Thank you for all efforts. I really appreciate it.

Thanks,
Vyacheslav Dubeyko.


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




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux