From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Luc Pionchon <pionchon.luc@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: hfs+: unable to access random files (after a while)
Date: Wed, 06 May 2015 09:44:37 -0700 [thread overview]
Message-ID: <1430930677.2766.2.camel@slavad-ubuntu-14.04> (raw)
In-Reply-To: <CAEYyJDwHhkNtWezsVAVaX9f2Unt5Duw10+5aVQC3hQvZgSCfrQ@mail.gmail.com>
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.
> I created it with OSX Disk Utility as HFS+, Case sensitive, Not Journaled.
>
Does this partition live on HDD or SSD? Are you sure that your SSD is
alive (if partition lives on SSD)?
If you'll move partition on another device the issue will be
reproducible?
Thanks,
Vyacheslav Dubeyko.
next prev parent reply other threads:[~2015-05-06 16:44 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 [this message]
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=1430930677.2766.2.camel@slavad-ubuntu-14.04 \
--to=slava@dubeyko.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pionchon.luc@gmail.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).