From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: James Courtier-Dutton <james.dutton@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: ext4 recovery
Date: Tue, 14 Jan 2020 16:25:51 -0500 [thread overview]
Message-ID: <20200114212551.GE140865@mit.edu> (raw)
In-Reply-To: <CAAMvbhFjLCLiLKhu5s7QtLdUY29h8eZ2pHd120o94gDduo+BLw@mail.gmail.com>
On Tue, Jan 14, 2020 at 04:03:53PM +0000, James Courtier-Dutton wrote:
>
> Say I started with 1 disk using LVM with an ext4 partition.
> I then added another disk. Added it to the LVM group, expanded the
> ext4 partition to then fill 2 disks.
> I then added another disk. Added it to the LVM group, expanded the
> ext4 partition to then fill 3 disks.
Where you using RAID 0, or some more advanced RAID level?
> One of the disk has now failed.
How has it failed? It is dead dead dead? Or are there a large number
of sector errors?
> Are there any tools available for ext4 that could help recover this?
> Note, I am a single user, not a company, so there is no money to give
> to a data recovery company, so I wish to try myself.
How valuable is your data? The first thing I would recommend, if your
data is worth it (and only you can make that decision) is to create a
new RAID set (using larger disks if that helps reduce the price) so
you can make an block-level image backup using the dd_rescue program.
If you can, then run e2fsck on the backup copy, and then see what you
can recover from that image set. This will save time (how much is
your time worth?) and perhaps increase the amount of data you can
recover (how much is your data worth?).
- Ted
next prev parent reply other threads:[~2020-01-14 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 16:03 ext4 recovery James Courtier-Dutton
2020-01-14 20:35 ` Andreas Dilger
2020-01-14 21:25 ` Theodore Y. Ts'o [this message]
2020-01-20 22:06 ` James Courtier-Dutton
2020-01-21 2:20 ` Andreas Dilger
2020-04-05 16:10 ` James Courtier-Dutton
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=20200114212551.GE140865@mit.edu \
--to=tytso@mit.edu \
--cc=james.dutton@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/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).