From: Eric Sandeen <sandeen@sandeen.net>
To: stress_buster <leo1783@yahoo.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: xfsprogs
Date: Thu, 07 Apr 2011 10:22:19 -0700 [thread overview]
Message-ID: <4D9DF2CB.1020503@sandeen.net> (raw)
In-Reply-To: <31342497.post@talk.nabble.com>
On 4/7/11 9:04 AM, stress_buster wrote:
>
> Hi,
>
> My xfs_repair is bit old- 2.9. version.
> I'm considering installing latest available. But just worried because this
> is my production server and has some custom apps built into my OS.
>
> Is upgrading xfs_repair a high risk?
No.
> Also do I need to install latest xfsprogs or anyway only to upgrade
> xfs_repair from the package?
> I'm only would need xfs_repair mostly, so doesnt matter to me leaving
> others-mkfs.xfs etc in xfsprogs at the old version if that minimises the
> risk...
if you really want to try newer xfs_repair only, just build an xfsprogs tree and run from inside the tree.
> Any thoughts?
Just upgrade. ;)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-04-07 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 16:04 xfsprogs stress_buster
2011-04-07 17:22 ` Eric Sandeen [this message]
2011-04-12 9:26 ` xfsprogs Leo Davis
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=4D9DF2CB.1020503@sandeen.net \
--to=sandeen@sandeen.net \
--cc=leo1783@yahoo.com \
--cc=linux-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