From: Christoph Hellwig <hch@infradead.org>
To: naveen yadav <yad.naveen@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS repair utils
Date: Mon, 29 Nov 2010 09:55:23 -0500 [thread overview]
Message-ID: <20101129145523.GA22839@infradead.org> (raw)
In-Reply-To: <AANLkTikUOZJeSnSHO+pAM5d6DjWEPBdUSiua1dcv0pxt@mail.gmail.com>
On Mon, Nov 29, 2010 at 07:30:50PM +0530, naveen yadav wrote:
> Hi All,
>
> I am using XFS 2.6.34 kernel on my target, and I have
> #xfs_repair -V
> xfs_repair version 3.0.5
>
> So is there any issue of compatibility with latest XFS_repair utils.
> or it will work fine with my latest kernel(2.6.34).
It works just fine, but the 3.1.x series of xfsprogs brings large
repair memory savings.
> Since some time mount fails.
What mount messages, what platform?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-29 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 14:00 XFS repair utils naveen yadav
2010-11-29 14:55 ` Christoph Hellwig [this message]
2010-11-29 15:55 ` naveen yadav
2010-11-30 4:13 ` naveen yadav
-- strict thread matches above, loose matches on Subject: below --
2010-11-29 15:29 naveen yadav
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=20101129145523.GA22839@infradead.org \
--to=hch@infradead.org \
--cc=xfs@oss.sgi.com \
--cc=yad.naveen@gmail.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