From: Dave Chinner <david@fromorbit.com>
To: Rafael Weingartner <rafaelweingartner@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS_REPAIR on LVM partition
Date: Mon, 16 Dec 2013 23:54:02 +1100 [thread overview]
Message-ID: <20131216125402.GB10988@dastard> (raw)
In-Reply-To: <CAG97racd-UhUqhVLcsbjqZt51iTEaHKaQNMkvQFnznH8X8wOUQ@mail.gmail.com>
On Mon, Dec 16, 2013 at 06:52:23AM -0200, Rafael Weingartner wrote:
> What's a "RAID NAS controller"? Details, please, or we can't help
> > you.
>
>
> Maybe I am not expressing my self clearly. That is what I meant:
> http://www.starline.de/produkte/raid-systeme/infortrend-raid-systeme/eonstor/es-a08u-g2421/
>
> It is a piece of hardware that we use to apply RAIDx (normally 1 or 5) over
> physical disks instead of plugging them on the storage server and applying
> RAID via software or something else. It exports the volumes using an SCSI
> channel. The devices are seen on the server as normal sd*, as if they were
> normal physical devices.
>
> So, hardware RAID5, lost a drive, rebuild on replace, filesystem in
> > a bad way after rebuild?
>
>
> That is exactly what happened, the RAID5 array lost a drive, and after we
> replaced and rebuild it, the filesystem was not mounting anymore.
> Teorically, this should not affect the filesystem since the RAID5 would
> have recovered any lost information.
In theory, yes. But we hear about "successful" hardware raid
rebuilds ifrom situations like yours that result in corrupt
filesystems. i.e. the hardware RAID rebuild didn't actually recover
properly...
So, what's the contents of the primary XFS superblock on that
device? What does this give:
# dd if=<dev> bs=512 count=1 | hexdump -C
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-16 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 22:47 XFS_REPAIR on LVM partition Rafael Weingartner
2013-12-16 0:01 ` Dave Chinner
2013-12-16 0:34 ` Rafael Weingartner
2013-12-16 3:05 ` Dave Chinner
2013-12-16 8:52 ` Rafael Weingartner
2013-12-16 12:54 ` Dave Chinner [this message]
[not found] ` <CAG97raeP-0QEhhYjDX_DDxzS3TN_brRSU6G+j-+V3KEuJ7Ym6Q@mail.gmail.com>
[not found] ` <CAG97raf7Na5UwzREJ_C9nYJ64r7PPwkhp_qcPiGVnKqu+ujAgw@mail.gmail.com>
2013-12-18 21:34 ` Dave Chinner
2013-12-18 23:29 ` Rafael Weingartner
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=20131216125402.GB10988@dastard \
--to=david@fromorbit.com \
--cc=rafaelweingartner@gmail.com \
--cc=xfs@oss.sgi.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