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:20:45 -0800 [thread overview]
Message-ID: <20081113012045.GL18990@pixar.com> (raw)
In-Reply-To: <491B7EB9.1050207@sandeen.net>
>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. :/
Here's what we can get from ext3:
% sudo dumpe2fs -h /dev/sda1 | grep 2008
dumpe2fs 1.40.8 (13-Mar-2008)
Inodes per group: 2008
Filesystem created: Thu May 29 11:11:12 2008
Last mount time: Tue Sep 30 18:01:18 2008
Last write time: Tue Sep 30 18:01:18 2008
Last checked: Thu May 29 11:11:12 2008
cheers,
-lars
--
lars r. damerow :: button pusher :: pixar animation studios
<lars@pixar.com>
next prev parent reply other threads:[~2008-11-13 1:22 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 [this message]
2008-11-13 1:33 ` Eric Sandeen
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=20081113012045.GL18990@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