From: MikeJeezy <forums@mgaccess.net>
To: xfs@oss.sgi.com
Subject: Re: mount: Structure needs cleaning
Date: Mon, 27 Feb 2012 10:32:55 -0800 (PST) [thread overview]
Message-ID: <33401743.post@talk.nabble.com> (raw)
In-Reply-To: <4F4B2281.1070200@hardwarefreak.com>
> You want the individual drive write caches disabled. Leaving their read
caches enabled is fine.
>
>The reason is that a power drop, kernel panic, or hardware lockup
>(thermal etc) clears the drive write caches before the blocks are
>written to the platters. It is suspected that many/most of these free
>space btree corruptions, such as yours here, are caused by data in
>caches not being flushed to the platters. SAN/RAID controllers with
>BBWC usually guarantee data in the write cache gets properly flushed to
>the platters when the system comes back up.
Makes total sense. Thanks so much.
--
View this message in context: http://old.nabble.com/mount%3A-Structure-needs-cleaning-tp33393100p33401743.html
Sent from the Xfs - General mailing list archive at Nabble.com.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-27 18:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 3:15 mount: Structure needs cleaning MikeJeezy
2012-02-26 4:35 ` Stan Hoeppner
2012-02-26 7:22 ` MikeJeezy
2012-02-26 17:07 ` Stan Hoeppner
2012-02-27 0:49 ` Dave Chinner
2012-02-27 3:11 ` MikeJeezy
2012-02-27 6:28 ` Stan Hoeppner
2012-02-27 18:32 ` MikeJeezy [this message]
2012-02-28 1:48 ` Dave Chinner
2012-02-28 9:14 ` Brian Candler
2012-02-29 3:50 ` Dave Chinner
2012-02-29 7:40 ` Brian Candler
-- strict thread matches above, loose matches on Subject: below --
2014-10-12 8:43 Mount: " tommason
2014-10-12 14:20 ` Brian Foster
2014-10-12 22:39 ` tom mason
2014-10-12 22:48 ` tom mason
2014-10-12 22:51 ` tom mason
2014-10-12 23:10 ` Dave Chinner
2014-10-13 10:05 ` Tom Mason
2014-10-13 10:19 ` Emmanuel Florac
2014-10-13 10:40 ` Tom Mason
2014-10-13 9:26 ` Emmanuel Florac
2014-10-13 20:33 Tom Mason
2014-10-13 22:09 ` Dave Chinner
2014-10-13 22:25 ` Tom Mason
2014-10-13 23:44 ` Dave Chinner
2014-10-13 22:38 ` Tom Mason
2014-10-13 23:47 ` Dave Chinner
2014-10-14 10:55 ` Emmanuel Florac
2014-10-14 15:46 ` Tom Mason
2014-10-14 16:38 ` Emmanuel Florac
2014-10-14 16:43 ` Tom Mason
2014-10-21 20:44 ` Tom Mason
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=33401743.post@talk.nabble.com \
--to=forums@mgaccess.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.