From: keld@keldix.com
To: Michel Dubois <michel.dubois.mtl@gmail.com>
Cc: linux-raid@vger.kernel.org,
Lars Ellenberg <lars.ellenberg@linbit.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Keith Busch <keith.busch@intel.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Kosina <jkosina@suse.cz>, Ming Lei <ming.lei@canonical.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
NeilBrown <neilb@suse.com>,
linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
linux-bcache@vger.kernel.org, Zheng Liu <gnehzuil.liu@gmail.com>,
Kent Overstreet <kent.overstreet@gmail.com>,
dm-devel@redhat.com, Shaohua Li <shli@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Alasdair Kergon <agk@redhat.com>,
Roland Kammerer <roland.kammerer@linbit.com>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: Recover filenames from failed RAID0
Date: Mon, 18 Jul 2016 11:37:41 +0200 [thread overview]
Message-ID: <20160718093740.GB24856@www5.open-std.org> (raw)
In-Reply-To: <CAAVC+N78o675MpkJN=VO_zZhh7ePer1zU-ePLJi4eNH04ih3mw@mail.gmail.com>
Hi
Which file system did you use?
I once wrote some code to get files out of an ext3 filesystem,
http://www.open-std.org/keld/readme-salvage.html
Maybe you can make some corrections for it to work
as I remember the code, then if you hit a directory, it will salvage the file names and the files
of that directory.
Best regards
keld
On Sun, Jul 17, 2016 at 03:10:03PM -0400, Michel Dubois wrote:
> Dear linux-raid mailing list,
>
> I have a RAID0 array of four 3TB disks that failed on the "third" disk.
>
> I am aware of the non-redundancy of RAID0 but I would like to recover
> the filenames from that RAID0. If I could recover some data it would
> be a bonus.
>
> Below you'll find the outputs of the following commands
> mdadm --examine /dev/sd[abcd]1
> fdisk -l
>
> where sda1, sdb1, sdc1 and sdd1 should be the 4 RAID devices.
>
> What could be my next step?
>
> I thank you for your time
>
> Michel Dubois
>
> ======================
> mdadm --examine /dev/sd[abcd]1
> /dev/sda1:
> Magic : a92b4efc
> Version : 00.90.00
> UUID : 7d247a6e:7b5d46c8:f52d9c89:db304b21
> Creation Time : Mon Apr 23 19:55:36 2012
> Raid Level : raid1
> Used Dev Size : 20980800 (20.01 GiB 21.48 GB)
> Array Size : 20980800 (20.01 GiB 21.48 GB)
> Raid Devices : 4
> Total Devices : 3
> Preferred Minor : 0
>
> Update Time : Mon Jun 27 21:12:23 2016
> State : clean
> Active Devices : 3
> Working Devices : 3
> Failed Devices : 1
> Spare Devices : 0
> Checksum : 1a57db60 - correct
> Events : 164275
>
>
> Number Major Minor RaidDevice State
> this 0 8 1 0 active sync /dev/sda1
>
> 0 0 8 1 0 active sync /dev/sda1
> 1 1 8 17 1 active sync /dev/sdb1
> 2 2 0 0 2 faulty removed
> 3 3 8 33 3 active sync /dev/sdc1
> /dev/sdb1:
> Magic : a92b4efc
> Version : 00.90.00
> UUID : 7d247a6e:7b5d46c8:f52d9c89:db304b21
> Creation Time : Mon Apr 23 19:55:36 2012
> Raid Level : raid1
> Used Dev Size : 20980800 (20.01 GiB 21.48 GB)
> Array Size : 20980800 (20.01 GiB 21.48 GB)
> Raid Devices : 4
> Total Devices : 3
> Preferred Minor : 0
>
> Update Time : Mon Jun 27 21:12:23 2016
> State : clean
> Active Devices : 3
> Working Devices : 3
> Failed Devices : 1
> Spare Devices : 0
> Checksum : 1a57db72 - correct
> Events : 164275
>
>
> Number Major Minor RaidDevice State
> this 1 8 17 1 active sync /dev/sdb1
>
> 0 0 8 1 0 active sync /dev/sda1
> 1 1 8 17 1 active sync /dev/sdb1
> 2 2 0 0 2 faulty removed
> 3 3 8 33 3 active sync /dev/sdc1
> /dev/sdc1:
> Magic : a92b4efc
> Version : 00.90.00
> UUID : 7d247a6e:7b5d46c8:f52d9c89:db304b21
> Creation Time : Mon Apr 23 19:55:36 2012
> Raid Level : raid1
> Used Dev Size : 20980800 (20.01 GiB 21.48 GB)
> Array Size : 20980800 (20.01 GiB 21.48 GB)
> Raid Devices : 4
> Total Devices : 3
> Preferred Minor : 0
>
> Update Time : Mon Jun 27 21:12:23 2016
> State : clean
> Active Devices : 3
> Working Devices : 3
> Failed Devices : 1
> Spare Devices : 0
> Checksum : 1a57db86 - correct
> Events : 164275
>
>
> Number Major Minor RaidDevice State
> this 3 8 33 3 active sync /dev/sdc1
>
> 0 0 8 1 0 active sync /dev/sda1
> 1 1 8 17 1 active sync /dev/sdb1
> 2 2 0 0 2 faulty removed
> 3 3 8 33 3 active sync /dev/sdc1
>
> ======================
> fdisk -l
>
> WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util
> fdisk doesn't support GPT. Use GNU Parted.
>
>
> Disk /dev/sda: 3000.5 GB, 3000592982016 bytes
> 255 heads, 63 sectors/track, 364801 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x03afffbe
>
> Device Boot Start End Blocks Id System
> /dev/sda1 1 267350 2147483647+ ee EFI GPT
>
> WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util
> fdisk doesn't support GPT. Use GNU Parted.
>
>
> Disk /dev/sdb: 3000.5 GB, 3000592982016 bytes
> 255 heads, 63 sectors/track, 364801 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x142a889c
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 1 267350 2147483647+ ee EFI GPT
>
> WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util
> fdisk doesn't support GPT. Use GNU Parted.
>
>
> Disk /dev/sdc: 3000.5 GB, 3000592982016 bytes
> 255 heads, 63 sectors/track, 364801 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x3daebd50
>
> Device Boot Start End Blocks Id System
> /dev/sdc1 1 267350 2147483647+ ee EFI GPT
>
> Disk /dev/md0: 21.4 GB, 21484339200 bytes
> 2 heads, 4 sectors/track, 5245200 cylinders
> Units = cylinders of 8 * 512 = 4096 bytes
> Disk identifier: 0x00000000
>
> Disk /dev/md0 doesn't contain a valid partition table
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-07-18 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 23:03 Recover filenames from failed RAID0 Michel Dubois
2016-07-17 19:10 ` Michel Dubois
2016-07-17 22:56 ` Stewart Ives
2016-07-18 9:37 ` keld [this message]
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=20160718093740.GB24856@www5.open-std.org \
--to=keld@keldix.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=gnehzuil.liu@gmail.com \
--cc=jkosina@suse.cz \
--cc=keith.busch@intel.com \
--cc=kent.overstreet@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michel.dubois.mtl@gmail.com \
--cc=ming.lei@canonical.com \
--cc=mingo@redhat.com \
--cc=neilb@suse.com \
--cc=peterz@infradead.org \
--cc=roland.kammerer@linbit.com \
--cc=shli@kernel.org \
--cc=snitzer@redhat.com \
--cc=tiwai@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).