From: Christoph Hellwig <hch@infradead.org>
To: Kiran.Chandapu@emc.com
Cc: hch@infradead.org, xfs@oss.sgi.com
Subject: Re: xfs_repair takes long time
Date: Thu, 2 Feb 2012 05:48:25 -0500 [thread overview]
Message-ID: <20120202104825.GA7670@infradead.org> (raw)
In-Reply-To: <D6BB8A3C30275C45A0A5CA53D5CC37F80242C12A10@MX03A.corp.emc.com>
On Thu, Feb 02, 2012 at 04:29:00AM -0500, Kiran.Chandapu@emc.com wrote:
> Hello Christoph,
>
> Thanks, I would try to upgrade it. Could you please tell me whether we can recover the data, actually we have all our data about 12 TB resides on that volume which has the issue.
Given your description of missing LV metadata I suspect that you
actually have lost part if not all of the filesystem. Running
xfs_repair -nv will give you more information about, but if you have
indeed destroyed the lvm block mapping it won't be able to do much.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-02 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 8:19 xfs_repair takes long time Kiran.Chandapu
2012-02-02 9:17 ` Christoph Hellwig
2012-02-02 9:29 ` Kiran.Chandapu
2012-02-02 10:48 ` Christoph Hellwig [this message]
2012-02-02 10:58 ` Kiran.Chandapu
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=20120202104825.GA7670@infradead.org \
--to=hch@infradead.org \
--cc=Kiran.Chandapu@emc.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