linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Chant <pete@petezilla.co.uk>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: Hardware failure or btrfs issue?
Date: Tue, 02 Jul 2013 18:36:48 +0100	[thread overview]
Message-ID: <51D30FB0.5000304@petezilla.co.uk> (raw)
In-Reply-To: <20130702072915.GA8170@carfax.org.uk>

On 07/02/2013 08:29 AM, Hugo Mills wrote:
> This is usually an indication that you have bad hardware -- I'd 
> suggest testing RAM, PSU, CPU in that order. I'm not sure what, if 
> anything, can be done to fix the error on the disk right now. 

Thanks, appreciated.

Hmm.  I've got one stick of ram out of the machine due to testing as I 
had some freezes last week.
If it were one of the RAM, PSU and CPU then I'm unsure why this IO issue 
only surfaces on the HDD and not the SSD.  I ordered a new HDD last 
night, before reading your post.  If its not the disk I'll go raid1.  If 
it is the disk then I'll probally find out.

>> Not that I've done anything other than a cursory check but it looks
>> like the read only data is fine.
>     Might be a good idea to use that to refresh your backups, just in
> case my prediction about the fixability is correct.

Well, first option is to drop in the new disk, freshly format it and 
copy the data across (not add it as a second disk).  If that fails last 
backup was wednesday.  I've not done much of note since then apart from 
try to fix the disk issues.



  reply	other threads:[~2013-07-02 17:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 22:56 Hardware failure or btrfs issue? Peter Chant
2013-07-02  7:29 ` Hugo Mills
2013-07-02 17:36   ` Peter Chant [this message]
2013-07-02 17:48     ` Hugo Mills
2013-07-02 21:37       ` Peter Chant

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=51D30FB0.5000304@petezilla.co.uk \
    --to=pete@petezilla.co.uk \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@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).