From: Dave Chinner <david@fromorbit.com>
To: Eli Morris <ermorris@ucsc.edu>
Cc: xfs@oss.sgi.com
Subject: Re: filesystem shrinks after using xfs_repair
Date: Sat, 24 Jul 2010 10:54:26 +1000 [thread overview]
Message-ID: <20100724005426.GN32635@dastard> (raw)
In-Reply-To: <274A8D0C-4C31-4FB9-AB2D-BA3C31D497E0@ucsc.edu>
On Fri, Jul 23, 2010 at 01:30:40AM -0700, Eli Morris wrote:
> On Jul 12, 2010, at 4:47 AM, Emmanuel Florac wrote:
>
> > Le Sun, 11 Jul 2010 18:10:41 -0700
> > Eli Morris <ermorris@ucsc.edu> écrivait:
> >
> >> Here are some of the log files from my XFS problem. Yes, I think this
> >> all started with a hardware failure of some sort. My storage is RAID
> >> 6, a an Astra SecureStor ES.
> >>
> >
> > There are IO errors on sdc, sdd and sdg. Aren't these jbods connected
> > through the same cable, for instance? You must correct the hardware
> > problems before attempting any repair or it will do more harm than good.
> >
> > --
> > ------------------------------------------------------------------------
> > Emmanuel Florac | Direction technique
> > | Intellique
> > | <eflorac@intellique.com>
> > | +33 1 78 94 84 02
> > ------------------------------------------------------------------------
>
> Hi Emmanuel,
>
> I think the raid tech support and me found and corrected the
> hardware problems associated with the RAID. I'm still having the
> same problem though. I expanded the filesystem to use the space of
> the now corrected RAID and that seems to work OK. I can write
> files to the new space OK. But then, if I run xfs_repair on the
> volume, the newly added space disappears and there are tons of
> error messages from xfs_repair (listed below).
Can you post the full output of the xfs_repair? The superblock is
the first thing that is checked and repaired, so if it is being
"repaired" to reduce the size of the volume then all the other errors
are just a result of that. e.g. the grow could be leaving stale
secndary superblocks around and repair is seeing a primary/secondary
mismatch and restoring the secondary which has the size parameter
prior to the grow....
Also, the output of 'cat /proc/partitions' would be interesting
from before the grow, after the grow (when everything is working),
and again after the xfs_repair when everything goes bad....
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:[~2010-07-24 0:51 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 1:10 filesystem shrinks after using xfs_repair Eli Morris
2010-07-12 2:24 ` Stan Hoeppner
2010-07-12 11:47 ` Emmanuel Florac
2010-07-23 8:30 ` Eli Morris
2010-07-23 10:23 ` Emmanuel Florac
2010-07-23 16:36 ` Eli Morris
2010-07-24 0:54 ` Dave Chinner [this message]
2010-07-24 1:08 ` Eli Morris
2010-07-24 2:39 ` Dave Chinner
2010-07-26 3:20 ` Eli Morris
2010-07-26 3:45 ` Dave Chinner
2010-07-26 4:04 ` Eli Morris
2010-07-26 5:57 ` Michael Monnerie
2010-07-26 6:06 ` Dave Chinner
2010-07-26 6:46 ` Eli Morris
2010-07-26 8:40 ` Michael Monnerie
2010-07-26 9:49 ` Emmanuel Florac
2010-07-26 17:22 ` Eli Morris
2010-07-26 18:33 ` Stuart Rowan
2010-07-26 21:06 ` Emmanuel Florac
2010-07-27 5:02 ` Eli Morris
2010-07-27 6:48 ` Stan Hoeppner
2010-07-27 8:21 ` Michael Monnerie
2010-07-26 10:20 ` Dave Chinner
2010-07-28 5:12 ` Eli Morris
2010-07-29 19:22 ` Eli Morris
2010-07-29 22:09 ` Emmanuel Florac
2010-07-29 22:48 ` Eli Morris
2010-07-29 23:01 ` Dave Chinner
2010-07-29 23:15 ` Eli Morris
2010-07-30 0:39 ` Michael Monnerie
2010-07-30 1:49 ` Eli Morris
2010-07-30 7:15 ` Emmanuel Florac
2010-07-30 7:57 ` Christoph Hellwig
2010-07-30 10:23 ` Michael Monnerie
2010-07-30 10:29 ` Christoph Hellwig
2010-07-30 12:40 ` Michael Monnerie
2010-07-30 13:17 ` Emmanuel Florac
-- strict thread matches above, loose matches on Subject: below --
2010-07-12 6:39 Eli Morris
2010-07-11 6:32 Eli Morris
2010-07-11 10:56 ` Stan Hoeppner
2010-07-11 16:29 ` Emmanuel Florac
2010-07-09 23:07 Eli Morris
2010-07-10 8:16 ` Stan Hoeppner
2010-07-24 21:09 ` 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=20100724005426.GN32635@dastard \
--to=david@fromorbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox