linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Pionchon <pionchon.luc@gmail.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: hfs+: unable to access random files (after a while)
Date: Wed, 19 Aug 2015 10:24:01 +0200	[thread overview]
Message-ID: <CAEYyJDwZRdED+56VOBqbv9a3Fqus5un-Dd8Omy=t3Lp-+84e5A@mail.gmail.com> (raw)
In-Reply-To: <1430942765.2766.23.camel@slavad-ubuntu-14.04>

On 6 May 2015 at 22:06, Viacheslav Dubeyko <slava@dubeyko.com> wrote:
>
> On Wed, 2015-05-06 at 19:33 +0200, Luc Pionchon wrote:
> > On 6 May 2015 at 18:44, Viacheslav Dubeyko <slava@dubeyko.com> wrote:
> > > On Wed, 2015-05-06 at 11:41 +0200, Luc Pionchon wrote:
> > >> 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.
> > >
> > > Does this partition live on HDD or SSD?
> >
> > It's a SSD
>
> Yes, I suppose that the reason of your issue is SSD drive itself. You
> have very different HFS+ error messages. It looks like that you have I/O
> errors after trying to generate the read/write requests. I assume that
> your syslog contains such error messages too. And I think that it is the
> primary reason of the issue.

for the record, this really was a kernel driver issue.

It took me some time, but now I have been using hfsplus with Sergei's
patch, and it worked flawlessly for the last few days.


Thanks you all for your time and for the fix!

      reply	other threads:[~2015-08-19  8:24 UTC|newest]

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

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='CAEYyJDwZRdED+56VOBqbv9a3Fqus5un-Dd8Omy=t3Lp-+84e5A@mail.gmail.com' \
    --to=pionchon.luc@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=slava@dubeyko.com \
    /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).