public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Lars Damerow <lars@pixar.com>
Cc: Timothy Shimmin <tes@sgi.com>, xfs@oss.sgi.com
Subject: Re: last xfs_repair time?
Date: Wed, 12 Nov 2008 19:33:25 -0600	[thread overview]
Message-ID: <491B83E5.4030002@sandeen.net> (raw)
In-Reply-To: <20081113012045.GL18990@pixar.com>

Lars Damerow wrote:
> From Eric Sandeen <sandeen@sandeen.net>, Wed, Nov 12, 2008 at 07:11:21PM -0600:
>> Timothy Shimmin wrote:
>>> Lars Damerow wrote:
>>>> Hi folks,
>>>>
>>>> Is it possible to query XFS for the last time xfs_repair fixed a
>>>> filesystem? I've been searching the man pages and haven't found anything
>>>> useful.
>>>>
>>> Not that I know of.
>>> Barry is the repair maintainer/expert though.
>>>
>>> --Tim
>>>
>>>
>> AFAIK it doesn't, but that'd be a neat feature - adding space for that,
>> and maybe date of mkfs (or mkfs version) etc might be nice too.
> 
> Thanks for the responses! It's handy to have that information
> available, especially when you're maintaining hundreds of workstations
> whose power cables occasionally get yanked out by their users. :/

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...

-Eric

  reply	other threads:[~2008-11-13  2:06 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 [this message]
2008-11-13  1:55         ` Lars Damerow
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=491B83E5.4030002@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=lars@pixar.com \
    --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