From: Stan Hoeppner <stan@hardwarefreak.com>
To: Gary Artim <gartim@gmail.com>, xfs@oss.sgi.com
Subject: Re: xfs fs on lvm, failed drive.
Date: Wed, 29 Oct 2014 13:18:10 -0500 [thread overview]
Message-ID: <54512F62.2080303@hardwarefreak.com> (raw)
In-Reply-To: <CA+r9EUGbxdXxP7uA1ufw=bSKE035VVHcK-Tyatr=fr-t_U=ZAw@mail.gmail.com>
On 10/29/2014 12:19 PM, Gary Artim wrote:
> Hi...wondering if there is anyway I can salvage a directory on the lvm
> volume that is xfs? thanks of any help, assembled:
>
> parted /dev/sdx
> mklabel gpt
> mkpart primary xfs 1 -1 (sometime xfs doesnt work until the xfsprogs are
> installed and reboot)
> set 1 lvm on
>
> do this for each drive.
> pvcreate /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
> vgcreate backup /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
> lvcreate -L 9T -n backuplv backup
> mkfs.xfs -L backuplv /dev/mapper/backup-backuplv
> /dev/mapper/backup-backuplv /xfs xfs (in fstab)
>
> failed drive:
> /dev/sdc1
You've created an XFS filesystem atop a concatenation of non-redundant
drives so this condition should not be unexpected. It's not a directory
you want to salvage, but the files within it. If they reside on sdc1
you're out of luck without using data recovery tools. If they reside on
sdb1, sdd1, or sde1, then running xfs_repair might make the FS mountable
and get you access to them again.
That's assuming LVM is still running with one drive gone, or will still
assemble the concatenation with one drive missing. I don't use LVM.
Cheers,
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-29 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 17:19 xfs fs on lvm, failed drive Gary Artim
2014-10-29 18:18 ` Stan Hoeppner [this message]
2014-10-29 18:54 ` Gary Artim
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=54512F62.2080303@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=gartim@gmail.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