All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan /*St0fF*/ Hübner" <stefan.huebner@stud.tu-ilmenau.de>
To: linux-raid@vger.kernel.org
Subject: Re: recovery problems, might be driver-related
Date: Mon, 08 Feb 2010 07:49:03 +0100	[thread overview]
Message-ID: <4B6FB3DF.9090208@stud.tu-ilmenau.de> (raw)
In-Reply-To: <20100208165200.3758520a@notabene.brown>

Neil Brown schrieb:
> On Sun, 07 Feb 2010 14:38:18 +0100
> [...]
> mdadm only checks the superblock at the start of the device to see if it
> looks like an ext3 filesystem.  So if an md array has a valid filesystem,
> then it is very likely that at least one of the devices in the array will
> appear to have a valid filesystem to mdadm.

Indeed that makes perfect sense.
> 
>[...]
> 
> Maybe there was meant to be another layer between the md array and the
> filesystem - maybe LVM ??  If there should have been an LVM and wasn't the
> filesystem would definitely look very corrupt even though the superblock
> might appear to be in the right place.
> 

Well, there's no need to tell me - the guys in taiwan just don't do it
on their NAS Devices.  But thanks for the hint.  I recall that the
successful data-recoveries were on a Thecus N5200, which does indeed use
lvm (to separate iSCSI-space, userspace, config-space, etc.)

> 
> NeilBrown
> 
Bottom-line: the customer's RAIDs were just f**ked, they should have had
taken drive-health more seriously... And the Vendor's code should get
"normalized" so that FS-checking in regular intervals takes place...

Thanks for the help,
Stefan Hübner
--
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

      reply	other threads:[~2010-02-08  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-07 13:38 recovery problems, might be driver-related Stefan Hübner
2010-02-08  5:52 ` Neil Brown
2010-02-08  6:49   ` Stefan /*St0fF*/ Hübner [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=4B6FB3DF.9090208@stud.tu-ilmenau.de \
    --to=stefan.huebner@stud.tu-ilmenau.de \
    --cc=linux-raid@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.