From: Christoph Hellwig <hch@infradead.org>
To: Adam Nielsen <a.nielsen@shikadi.net>
Cc: Christoph Hellwig <hch@infradead.org>,
LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: XFS internal error xfs_da_do_buf(1) at line 2015 of file fs/xfs/xfs_da_btree.c
Date: Sun, 4 Jan 2009 04:23:49 -0500 [thread overview]
Message-ID: <20090104092349.GA26194@infradead.org> (raw)
In-Reply-To: <49607B5B.3070707@shikadi.net>
On Sun, Jan 04, 2009 at 07:03:23PM +1000, Adam Nielsen wrote:
> No, I didn't realise I had to do that...in fact I didn't even realise
> SATA disks *had* write caches, I thought the cache was for reading
> only...
Which would be the better default (it's what high-end disks generally
do by default). I've been wondering for a while how we can make default
setups in the presence of lvm/dm more secure, but there hasn't been
any progress yet.
>> Run xfs_repair over it to fix up the directory, and make sure to
>> configure your disks properly so that it doesn't happen again..
>
> Will do, thanks for the advice! Is there any standard way to disable
> write caching on a SATA disk? hdparm -W seems to do the trick, but then
> I can't run that until the system is up and running, leaving a small
> window of opportunity for something to go wrong.
On Debian based systems you can add -W0 to /etc/default/hdparm and
it gets executed before the root filesystem is remounted read-write,
I'm not sure how other distributions handle it.
next prev parent reply other threads:[~2009-01-04 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 1:16 XFS internal error xfs_da_do_buf(1) at line 2015 of file fs/xfs/xfs_da_btree.c Adam Nielsen
2009-01-04 7:46 ` Christoph Hellwig
2009-01-04 9:03 ` Adam Nielsen
2009-01-04 9:23 ` Christoph Hellwig [this message]
2009-01-04 11:44 ` Alan Cox
2009-01-04 15:34 ` Christoph Hellwig
2009-01-04 15:50 ` Andi Kleen
2009-01-05 5:12 ` markus reichelt
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=20090104092349.GA26194@infradead.org \
--to=hch@infradead.org \
--cc=a.nielsen@shikadi.net \
--cc=linux-kernel@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