Yes..yes..I know. :) I wasn't going to kill my fs. I was just referring
to xfs_repair -L.
On Tue, 2003-10-28 at 15:51, Glen Overby wrote:
> On October 28, Austin Gonyou wrote:
> > On Mon, 2003-10-27 at 18:38, Glen Overby wrote:
> > > On October 27, Austin Gonyou wrote:
> > > > The issue is that I don't see any "ERROR" statements in this
> output,
> > > but
> > > > trying to replay the log or mounting -oro will oops the kernel and
> > > that
> > > > one device is then unavailable and the system must be rebooted.
> > >
> > > Can you send the exact oops message.. where it occured, etc?
> > >
> > > > I would like to extract the log so I can put this server back into
> our
> > > > beta environment. If someone could aid me in this I'd much
> appreciate
> > > > it.
> > >
> > > Here's an example:
> > >
> > > [root@HOSTNAME root]# /a23/overby/bin.l/mkfs.xfs -f -b size=4096 -l
> > > size=8192b /dev/hda6
> > Ok. missed this part, I thought it was what I'd typed. I'll do this,
> > though the system is now back into production, I can see about trying
> to
> > break a log again and then extract it.
>
> er, this was just part of my example. I started with a clean
> filesystem. You don't have to wipe your filesystem... in fact, if you
> do that your log will be very clean and you don't need to bother
> dumping it. Data loss from mkfs "100%".
>
> Glen Overby
--
Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Coremetrics, Inc.
|