linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Pionchon <pionchon.luc@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: hfs+: unable to access random files (after a while)
Date: Wed, 6 May 2015 11:41:38 +0200	[thread overview]
Message-ID: <CAEYyJDwHhkNtWezsVAVaX9f2Unt5Duw10+5aVQC3hQvZgSCfrQ@mail.gmail.com> (raw)

Hi,

my system randomly fails to access (random) files on a HFS+ partition.

Could anybody help me to identify the issue?


I have a HFS+ partition shared between Linux and OSX.
I created it with OSX Disk Utility as HFS+, Case sensitive, Not Journaled.

After "some time" the system fails to access random files.
It gives various error messages, like:
- "Error when getting information for file 'foo': Cannot allocate memory"
- "Error when getting information for file 'foo': invalid argument"
- "Error when getting information for file 'foo': input/output error"

Sometimes it is enough to unmount/remount the partition,
then it works fine again "for a while".

I am having this issue since 3.13.
It is still present in 4.1.0-rc1.
3.12.24 used to work fine.

Can it be an issue on my specific partition? Or in the driver?
OSX Disk Utility reports no issue on the partition,
and OSX Finder never complains.
fsck.hfsplus reports no issue either.

I gave more information at https://bugzilla.kernel.org/show_bug.cgi?id=78761


Could anybody help me to identify the issue?

             reply	other threads:[~2015-05-06  9:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06  9:41 Luc Pionchon [this message]
2015-05-06 16:44 ` hfs+: unable to access random files (after a while) Viacheslav Dubeyko
2015-05-06 17:33   ` Luc Pionchon
2015-05-06 20:06     ` Viacheslav Dubeyko
2015-08-19  8:24       ` Luc Pionchon

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=CAEYyJDwHhkNtWezsVAVaX9f2Unt5Duw10+5aVQC3hQvZgSCfrQ@mail.gmail.com \
    --to=pionchon.luc@gmail.com \
    --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).