From: Stan Hoeppner <stan@hardwarefreak.com>
To: NeilBrown <neilb@suse.de>
Cc: lists@yazzy.org, linux-raid@vger.kernel.org
Subject: Re: Recovery of failed RAID 6 and LVM
Date: Tue, 27 Sep 2011 21:50:58 -0500 [thread overview]
Message-ID: <4E828B92.40502@hardwarefreak.com> (raw)
In-Reply-To: <20110928091335.1df35f8e@notabene.brown>
On 9/27/2011 6:13 PM, NeilBrown wrote:
> On Tue, 27 Sep 2011 21:12:58 +0200 "Marcin M. Jessa"<lists@yazzy.org> wrote:
>
>> On 9/26/11 11:31 AM, NeilBrown wrote:
>>> On Mon, 26 Sep 2011 11:05:38 +0200 "Marcin M. Jessa"<lists@yazzy.org> wrote:
>>>
>>>> On 9/26/11 12:18 AM, NeilBrown wrote:
>>>>
>>>>> Do you remember what filesystem you had on 'storage'? Was it ext3 or ext4 or
>>>>> xfs or something else?
>>>>
>>>> You're giving me some hope here and then silence :)
>>>> Why did you ask about the file system? Should I run fsck on the LV ?
>>>>
>>>>
>>>>
>>>
>>> You already did run fsck on the LV. It basically said that it didn't
>>> recognise the filesystem at all.
>>> I asked in case maybe it was XFS in which case a different tool would be
>>> required.
>>
>> Looks like I didn't remember correctly. I ran testdisk and it reported
>> the file system to be XFS. What would you suggest now Neil?
>>
>>
>
> Presumably
> xfs_check /dev/fridge/storage
>
> and then maybe
> xfs_repair /dev/fridge/storage
>
> but I have no experience with XFS - I'm just reading man pages.
>
> NeilBrown
Reading the thread, and the many like it over the past months/years, may
yield a clue as to why you wish to move on to something other than Linux
RAID...
--
Stan
next prev parent reply other threads:[~2011-09-28 2:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 7:55 Recovery of failed RAID 6 and LVM Marcin M. Jessa
2011-09-25 8:39 ` Stan Hoeppner
2011-09-25 10:07 ` Marcin M. Jessa
2011-09-25 13:15 ` Phil Turmel
2011-09-25 14:16 ` Marcin M. Jessa
2011-09-25 16:43 ` Phil Turmel
2011-09-25 14:41 ` Marcin M. Jessa
2011-09-25 16:19 ` Phil Turmel
2011-09-25 21:40 ` NeilBrown
2011-09-25 21:58 ` Marcin M. Jessa
2011-09-25 22:18 ` NeilBrown
2011-09-25 22:21 ` Marcin M. Jessa
[not found] ` <4E804062.3020700@yazzy.org>
2011-09-26 9:31 ` NeilBrown
2011-09-26 10:53 ` Marcin M. Jessa
2011-09-26 11:10 ` NeilBrown
2011-09-27 19:12 ` Marcin M. Jessa
2011-09-27 23:13 ` NeilBrown
2011-09-28 2:50 ` Stan Hoeppner [this message]
2011-09-28 7:10 ` Marcin M. Jessa
2011-09-28 7:51 ` David Brown
2011-09-28 16:12 ` Stan Hoeppner
2011-09-28 16:30 ` Marcin M. Jessa
2011-09-28 18:56 ` Thomas Fjellstrom
2011-09-28 19:26 ` Marcin M. Jessa
2011-09-28 19:42 ` Thomas Fjellstrom
2011-09-28 23:49 ` NeilBrown
2011-09-29 9:03 ` David Brown
2011-09-29 15:21 ` Stan Hoeppner
2011-09-29 17:14 ` David Brown
2011-09-29 18:28 ` Dan Williams
2011-09-29 23:07 ` NeilBrown
2011-09-30 0:18 ` Williams, Dan J
2011-10-05 2:15 ` NeilBrown
2011-09-28 10:38 ` Michal Soltys
2011-09-28 13:20 ` Brad Campbell
2011-09-28 19:02 ` Thomas Fjellstrom
2011-09-28 16:31 ` Stan Hoeppner
2011-09-28 16:37 ` Marcin M. Jessa
2011-09-28 19:03 ` Thomas Fjellstrom
2011-09-28 19:29 ` Marcin M. Jessa
2011-09-28 19:43 ` Thomas Fjellstrom
2011-09-30 20:01 ` Marcin M. Jessa
2011-09-30 21:47 ` Thomas Fjellstrom
2011-09-30 22:30 ` Marcin M. Jessa
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=4E828B92.40502@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=lists@yazzy.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).