I submitted some crashdumps and traces, but nothing seems to have come
out of it ATM.
On Thu, 2002-10-03 at 21:18, Stephen Lord wrote:
> On Thu, 2002-10-03 at 21:08, Austin Gonyou wrote:
> > This sounds very much like my problem from a few weeks ago.
>
> And your solution was? Or was it something which got written
> off?
>
I ended up having to do xfs_repair -L. Most of the volumes were ok
afterwards, but I'm still not sure *why* it happened. It did so happen
though, I had bad hardware which cause the original crash at that time.
The recent crash, I'm still trying to understand.
> Thanks,
>
> Steve
>
> >
> >
> >
> > On Thu, 2002-10-03 at 20:35, Eric Sandeen wrote:
> > > On Fri, 4 Oct 2002, Federico Sevilla III wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > After another reboot I did an xfs_check on the yet-unrecovered
> > > > /dev/sda10 and I did not get any messages. An attempt to mount
> it
> > > > succeeded. I unmounted /dev/sda10 and did another xfs_check and
> > > again I
> > > > did not get any messages, which from the manual page I've
> > > interpreted as
> > > > "clean". Because /dev/sda10 was finally unmounted properly the
> next
> > > > reboot worked and our server is back online.
> > >
> > > Odd. Just to make sure I read everything right - xfs itself was
> > > hanging
> > > in recovery, and your oopses came from when you tried to sync with
> > > SysRq?
> > >
> > > And then it sounds like the only thing you did before the mount
> was
> > > ultimately successful, was to run xfs_check... which should be a
> > > read-only
> > > test, and should not have changed anything about the fs, as far as
> I
> > > know.
> > >
> > > I think the most helpful thing (in retrospect) would have been to
> > > break into kdb, and see where mount was stuck during recovery.
> > >
> > > I'm not sure what to make of this problem...
> > >
> > > -Eric
> > --
> > Austin Gonyou <austin@xxxxxxxxxxxxxxx>
> > Coremetrics, Inc.
> >
--
Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Coremetrics, Inc.
|