linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: wilsonjonathan <piercing_male@hotmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: linear raid, is partial recovery possible?
Date: Mon, 28 Nov 2011 16:00:57 -0600	[thread overview]
Message-ID: <4ED40499.3060903@hardwarefreak.com> (raw)
In-Reply-To: <BLU0-SMTP248DE7134BCABFEB83181BD98B20@phx.gbl>

On 11/28/2011 2:06 PM, wilsonjonathan wrote:

> Or perhaps it is dependent on the file system on the array, 

It is.

> eg. ext
> works by trying to place files distant to each other to help reduce the
> possibility of fragmentation?

That's not relevant.  What is relevant is where the filesystem metadata
is stored, if any of it was lost when the disk died, and if the
filesystem can recover itself with a repair operation.

I know of one such recovery of a 60TB XFS filesystem residing on a combo
mdraid linear array over 5 hardware RAID6 arrays, after 1 of the 5
constituent arrays suffered complete failure.  xfs_repair deleted the
entries from directory structure whose files were missing, allowing
normal access to all other files.  This was an extremely lucky outcome
in this case and was only possible due to the specific on disk metadata
layout of this individual filesystem. XFS would likely not be able to
recover from such a failure in all cases.

You're using EXT of some flavor.  I suggest you read everything you can
about the EXT version involved here, ask on the respective mailing list.

Good luck.

-- 
Stan

      parent reply	other threads:[~2011-11-28 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 20:06 linear raid, is partial recovery possible? wilsonjonathan
2011-11-28 20:46 ` NeilBrown
2011-11-28 20:51 ` Robin Hill
2011-11-28 22:08   ` Stan Hoeppner
2011-11-28 22:00 ` Stan Hoeppner [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=4ED40499.3060903@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=piercing_male@hotmail.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;
as well as URLs for NNTP newsgroup(s).