From: Dave Chinner <david@fromorbit.com>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: every week new xfs errors
Date: Fri, 4 Sep 2015 08:20:23 +1000 [thread overview]
Message-ID: <20150903222023.GX3902@dastard> (raw)
In-Reply-To: <CAAA5faEq0quyfE4zFp1G_r+igZ_vufCN9yFM-5Lr1wzN9r16Lw@mail.gmail.com>
On Thu, Sep 03, 2015 at 02:55:56PM -0600, Reinoud Koornstra wrote:
> Hi Everyone,
>
> I am running xfs on a SSD.
> smartd reports this:
>
> Device: /dev/sdb [SAT], Crucial_CT256M550SSD3, S/N:15020ED48DF8,
> WWN:5-00a075-10ed48df8, FW:MU02, 256 GB
>
> I am running a compiled linux 4.1.6 kernel (before 4.1.2 and before
> that 3.18.x) on ubuntu 14.04
> xfs_repair had issues mostly every week to report.
> Now xfs_repair says it's finally clean.
> However:
>
> reinoud@Mipam:/$ sudo xfs_db -r /dev/sdb1
> xfs_db> frag
> Metadata CRC error detected at block 0x773cac0/0x1000
> Metadata CRC error detected at block 0xee79570/0x1000
> Metadata CRC error detected at block 0x165b6020/0x1000
> actual 2891336, ideal 2888294, fragmentation factor 0.11%
You're running on a mounted filesystem? (the "-r" is only
necessary if the fs is mounted) If so, this is expected.
> There are still issue.
> Are there problems with running xfs on a SSD in general?
> It's fast and stable (seems like), but mostly i start noticing
> problems when i'm running git operations that fail, after that
> xfs_repair reports issues indeed.
Perhaps you'd like to start by reporting these issues, as solving
them is far more important that what the (useless) frag command
reports. Start here:
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-09-03 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 20:55 every week new xfs errors Reinoud Koornstra
2015-09-03 22:20 ` Dave Chinner [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=20150903222023.GX3902@dastard \
--to=david@fromorbit.com \
--cc=reinoudkoornstra@gmail.com \
--cc=xfs@oss.sgi.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