linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Antonov <saproj@gmail.com>
To: Hin-Tak Leung <htl10@users.sourceforge.net>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 2.6 to 4.0] hfsplus: fix B-tree corruption after insertion at position 0
Date: Mon, 8 Jun 2015 15:30:23 +0200	[thread overview]
Message-ID: <CABikg9wqmsp1aAsp9BBcteqauDNfQe+xQqoB-DPPxQeRc=Uxzw@mail.gmail.com> (raw)
In-Reply-To: <1426786824.70252.YahooMailBasic@web172303.mail.ir2.yahoo.com>

On 19 March 2015 at 18:40, Hin-Tak Leung <htl10@users.sourceforge.net> wrote:
> ------------------------------
> On Wed, Mar 18, 2015 11:05 PM GMT Sergei Antonov wrote:
>
>>On 18 March 2015 at 16:28, Hin-Tak Leung <htl10@users.sourceforge.net> 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.

  parent reply	other threads:[~2015-06-08 13:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1426786824.70252.YahooMailBasic@web172303.mail.ir2.yahoo.com>
2015-03-26  2:06 ` [PATCH 2.6 to 4.0] hfsplus: fix B-tree corruption after insertion at position 0 Sergei Antonov
2015-06-08 13:30 ` Sergei Antonov [this message]
     [not found] <1426692505.88311.YahooMailBasic@web172305.mail.ir2.yahoo.com>
2015-03-18 23:05 ` Sergei Antonov
2015-03-17  2:10 Sergei Antonov
2015-03-17 16:50 ` Viacheslav Dubeyko

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='CABikg9wqmsp1aAsp9BBcteqauDNfQe+xQqoB-DPPxQeRc=Uxzw@mail.gmail.com' \
    --to=saproj@gmail.com \
    --cc=htl10@users.sourceforge.net \
    --cc=linux-fsdevel@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).