From: Emmanuel Florac <eflorac@intellique.com>
To: Eli Morris <ermorris@ucsc.edu>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair of critical volume
Date: Mon, 1 Nov 2010 11:07:34 +0100 [thread overview]
Message-ID: <20101101110734.3ce15556@galadriel.home> (raw)
In-Reply-To: <1A57C61E-463F-4CB4-967C-DD6B66857E28@ucsc.edu>
Le Sun, 31 Oct 2010 20:40:20 -0700 vous écriviez:
> Thanks for your help. The RAID is a SCSI connected direct attached
> storage 16 bay unit made by Maxtronic. It is a Janus 6640, is case
> that helps anything.
Alas, never heard of it... Looks like a quite low end hardware, without
redundant controllers. Probably similar to Infortrend. The possibility
of an unreliable firmware cannot be excluded with these :)
> At the time of its problem, it was mounted
> read-only as I was trying to be careful of the data, since the main
> volume failed and this was our only copy. So maybe the cache isn't a
> big deal.
Indeed, nothing to lose in RO mode.
> I'll try the "dead" drives tomorrow with a WD utility. I'll
> give Spinrite a try, if the WD utility doesn't revive them.
Good luck.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-01 10:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 19:56 xfs_repair of critical volume Eli Morris
2010-10-31 20:40 ` Emmanuel Florac
2010-11-01 3:40 ` Eli Morris
2010-11-01 10:07 ` Emmanuel Florac [this message]
2010-10-31 21:10 ` Steve Costaras
2010-11-01 15:03 ` Stan Hoeppner
-- strict thread matches above, loose matches on Subject: below --
2010-10-31 7:54 Eli Morris
2010-10-31 9:54 ` Stan Hoeppner
2010-11-12 8:48 ` Eli Morris
2010-11-12 13:22 ` Michael Monnerie
2010-11-12 22:14 ` Stan Hoeppner
2010-11-13 8:19 ` Emmanuel Florac
2010-11-13 9:28 ` Stan Hoeppner
2010-11-13 15:35 ` Michael Monnerie
2010-11-14 3:31 ` Stan Hoeppner
2010-12-04 10:30 ` Martin Steigerwald
2010-12-05 4:49 ` Stan Hoeppner
2010-12-05 9:44 ` Roger Willcocks
2010-11-12 23:01 ` Eli Morris
2010-11-13 15:25 ` Michael Monnerie
2010-11-14 11:05 ` Dave Chinner
2010-11-15 4:09 ` Eli Morris
2010-11-16 0:04 ` Dave Chinner
2010-11-17 7:29 ` Eli Morris
2010-11-17 7:47 ` Dave Chinner
2010-11-30 7:22 ` Eli Morris
2010-12-02 11:33 ` Michael Monnerie
2010-12-03 0:58 ` Stan Hoeppner
2010-12-04 0:43 ` Eli Morris
2010-10-31 14:10 ` Emmanuel Florac
2010-10-31 14:41 ` Steve Costaras
2010-10-31 16:52 ` Roger Willcocks
2010-11-01 22:21 ` Eric Sandeen
2010-11-01 23:32 ` Eli Morris
2010-11-02 0:14 ` Eric Sandeen
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=20101101110734.3ce15556@galadriel.home \
--to=eflorac@intellique.com \
--cc=ermorris@ucsc.edu \
--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 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.