On 19 March 2015 at 18:40, Hin-Tak Leung <htl10@xxxxxxxxxxxxxxxxxxxxx> wrote:
> ------------------------------
> On Wed, Mar 18, 2015 11:05 PM GMT Sergei Antonov wrote:
>
>>On 18 March 2015 at 16:28, Hin-Tak Leung <htl10@xxxxxxxxxxxxxxxxxxxxx> wrote:
>>> Can you describe a bit more about the symptom please?
>>
>>Some files and directories are gone. Depending on which of the catalog
>>file's nodes reside in the unavailable extents, it may vary from "some
>>data can be salvaged" to "screw it, reformat the volume".
>>
>>> I am
>>> wondering whether it is related to an issue I have had which is quite reproducible:
>>> If I merely run "du" repeatedly on a large directory on an HFS+ formatted
>>> drive, on a somewhat resource-tight system (having firefox running with lots
>>> windows seems to make it happens sooner, and it was on a system with only 2GB memory).
>>
>>Then what?
>>
>
> The kernel getting very confused, not being able to read some files/directories
> on the HFS+ volume, and having lots of messages in the kernel log about inconsistent
> b-tree.
>
> This appears to be entirely in-memory and has no effect on on-disk data;
> also I can reproduce the problem by mounting read-only. If I reboot,
> fsck always says the hfs+ volume is clean, and I can repeat the exercise.
The patch I published recently ("hfsplus: release bnode pages after
use, not before") will fix your problem. Please, test.
--
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
