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 13:06:05 -0700 [thread overview]
Message-ID: <1430942765.2766.23.camel@slavad-ubuntu-14.04> (raw)
In-Reply-To: <CAEYyJDwV1+7=wdcDHYHRNTAPbbJa0mHDWVYs+SrNZLvW_27zxw@mail.gmail.com>
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.
> >> I created it with OSX Disk Utility as HFS+, Case sensitive, Not Journaled.
> >>
> >
> > 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.
My last SSD drive worked well one year only. Now I can read from
partitions on device but any write operations fail. So, sometimes a SSD
drive can behave itself in very tricky way.
>
> > Are you sure that your SSD is alive (if partition lives on SSD)?
>
> I do not know what means "alive". How can I check?
>
> The whole system is on this SSD, in a MacBook 2.1:
> / and /home as ext4, linux swap, OSX partition, EFI partition,
> and the faulty partition.
>
Usually, S.M.A.R.T should provide information about SSD drive's health.
You can use smartmontools (for example, smartctl utility). But, frankly
speaking, I think that it needs to treat a file system behavior in wise
way for understanding a drive healthiness very frequently. If a file
system emits error messages in a really crazy way then the most probable
reason of an issue can be a drive itself.
>
>
> > If you'll move partition on another device the issue will be
> > reproducible?
>
> How can I move a partition?
>
You can use different specialized tools. I think you can use Gparted,
dd, rsync or cpio utilities under Linux. I think you can find the
description of using with tools for moving a partition in the Internet.
> Would it help if I create a partition of the same type on a USB drive,
> and see if I get similar errors?
>
> I just have another SSD, is it ok?
> Or should I try to get a USB HDD?
>
It is possible to use any valid device. But HDD sounds as more reliable
way for me. But, finally, it's up to you.
Thanks,
Vyacheslav Dubeyko.
next prev parent reply other threads:[~2015-05-06 20:06 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 [this message]
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=1430942765.2766.23.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).