From: Lars Damerow <lars@pixar.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Timothy Shimmin <tes@sgi.com>, xfs@oss.sgi.com
Subject: Re: last xfs_repair time?
Date: Wed, 12 Nov 2008 17:55:04 -0800 [thread overview]
Message-ID: <20081113015503.GN18990@pixar.com> (raw)
In-Reply-To: <491B83E5.4030002@sandeen.net>
>From Eric Sandeen <sandeen@sandeen.net>, Wed, Nov 12, 2008 at 07:33:25PM -0600:
> So, for what it's worth, power loss should not necessarily require a
> repair; as long as you have barriers enabled and/or you're not losing
> log writes to a volatile write cache, power loss should never corrupt
> the filesystem metadata; that is what the log is for, after all...
Our disks are partitioned with LVM, so we don't have write barriers. We
just recently disabled write caching, though, so our future should be
brighter than it's been. :)
-lars
--
lars r. damerow :: button pusher :: pixar animation studios
<lars@pixar.com>
next prev parent reply other threads:[~2008-11-13 2:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 22:41 last xfs_repair time? Lars Damerow
2008-11-13 0:05 ` Timothy Shimmin
2008-11-13 1:11 ` Eric Sandeen
2008-11-13 1:20 ` Lars Damerow
2008-11-13 1:33 ` Eric Sandeen
2008-11-13 1:55 ` Lars Damerow [this message]
2008-11-13 9:48 ` [xfs] " Martin Steigerwald
2008-11-13 2:16 ` Barry Naujok
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=20081113015503.GN18990@pixar.com \
--to=lars@pixar.com \
--cc=sandeen@sandeen.net \
--cc=tes@sgi.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