From: pg_xf2@xf2.for.sabi.co.UK (Peter Grandi)
To: Linux XFS <xfs@oss.sgi.com>
Subject: Re: Question/Problem: Mounting of XFS filesystem takes a lot of time
Date: Thu, 21 Oct 2010 01:19:26 +0100 [thread overview]
Message-ID: <19647.34574.786118.56593@tree.ty.sabi.co.uk> (raw)
In-Reply-To: <1287593846.2338.5.camel@nukebox>
>> Check your disks. I've seen harddisks dying in that way.
>> Suddenly access times are horrible. Test random access I/O and
>> compare times, not sequential - those might still look good.
> [ ... ] When messing around with the BIOS settings (switching
> SATA mode from RAID to IDE) I get quite an obvious message
> stating that the S.M.A.R.T. status of one of the disks is
> BAD. Removing that disk solved the problem. [ ... ]
The suggestion about checking disk error status was good, and
relates to an important but little known detail about SATA vs. SAS
disk drives.
Usually SATA drives are pogrammed to do a large number of firmware
driven retries in case of data errors, hanging the IO subsystem,
while SAS drives, which are expected to be used in RAID sets,
don't, and report errors immediately. So called "Raid Edition"
SATA drives often behave like SAS drives in this respect.
It is often possible but usually quite awkward to change that
setting for ordinary SATA drives.
Disabling extended fw retries is usually a good idea with Linux
anyhow, as it does sw retries anyhow, and very good for drives
used in RAID sets with redundancy, to reduce latency in the case
of errors.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-10-21 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 16:57 Question/Problem: Mounting of XFS filesystem takes a lot of time Andreas Hasenkopf
2010-10-21 0:19 ` Peter Grandi [this message]
2010-10-21 17:05 ` Emmanuel Florac
-- strict thread matches above, loose matches on Subject: below --
2010-10-19 20:44 Andreas Hasenkopf
2010-10-19 21:33 ` Martin Steigerwald
2010-10-19 23:08 ` Dave Chinner
2010-10-20 6:05 ` Michael Monnerie
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=19647.34574.786118.56593@tree.ty.sabi.co.uk \
--to=pg_xf2@xf2.for.sabi.co.uk \
--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