From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roman Zippel Subject: Re: [PATCH 2/2] Fix journal detection on HFS+. Date: Mon, 1 Dec 2008 15:27:04 +0100 (CET) Message-ID: References: <1227240087-29413-1-git-send-email-wt@penguintechs.org> <1227240087-29413-2-git-send-email-wt@penguintechs.org> <1227240087-29413-3-git-send-email-wt@penguintechs.org> <200811230552.02221.zippel@linux-m68k.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Andrew Morton , linux-fsdevel@vger.kernel.org To: Warren Turkal Return-path: Received: from smtp-vbr8.xs4all.nl ([194.109.24.28]:3121 "EHLO smtp-vbr8.xs4all.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752652AbYLAO1X (ORCPT ); Mon, 1 Dec 2008 09:27:23 -0500 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi, On Mon, 1 Dec 2008, Warren Turkal wrote: > I have a drive that has the property of having the journal bit set and > having 0 in the journal_info_block field that mounts in rw on MacOS X. > That's how I discovered the problem. Which OS X version? How was that drive created? Is the journal info block still zero after being mounted in OS X? Does Disk Utility report the drive as journaled? The main point I don't understand is how it became zero in first place. OS X will certainly mount such a drive, but I'd expect it'll simply reinitialize the journal. bye, Roman