xfs
[Top] [All Lists]

Re: Errors using amanda/xfsdump

To: Steve Lord <lord@xxxxxxx>
Subject: Re: Errors using amanda/xfsdump
From: Justin Tripp <justin@xxxxxxxxx>
Date: Wed, 25 Apr 2001 14:46:17 -0600 (MDT)
Cc: <linux-xfs@xxxxxxxxxxx>
In-reply-to: <200104252039.f3PKdKK30250@jen.americas.sgi.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
I meant to say that the process 803 was xfsdump.  Sorry.  I had a brain
cramp there ...

                                .justin.



------------------------------------------------------------------------
Justin Leonard Tripp                                   justin@xxxxxxxxxx
Configurable Computing Laboratory Research Assistant      CB 461 x8-7206
Electrical and Computer Engineering Department  Brigham Young University

On Wed, 25 Apr 2001, Steve Lord wrote:

> >
> > I have been trying to backup xfs partitions using amanda, and there seems
> > to be a problem with xfsdump.  Amanda suprisingly recognized xfsdump and
> > seems to tried to do the backup correctly.  On the other hand, whenever we
> > attempted to backup the machine would belly-up hard.
> >
> > The problem is vexing, because sometimes it will fail consistently and
> > quickly, yet other times it seems to take all day to fail.  I am doing to
> > following to replicate the amanda backup:
> >
> > ssh xfs_machine -l root "/usr/sbin/xfsdump -F -l 0 - /dev/sda1" | gzip -6
> > - > file.gz
> >
> > At the same time the xfs_machine is serving up a partition nfs and the
> > partition is being read and written, by two independant news spools.
> > Doing a usenet news spool over nfs onto xfs, may not be the best
> > performance-wise, but I think most may agree that a news server can hit
> > disks pretty hard when it comes to file ops.
> >
> > After xfsdump caused the machine to fail, got the following error message
> > on the console:
> >
> > xfs_iget_core: ambiguous vns: vp/0xc3a543c8 invp/0xcf89d948
> >
> > Unable to handle kernel NULL pointer dereference at virtual address
> > 00000008
> >
> > printing eip:
> >   d08f90bf
> > *pdc=00000000
> >
> > Entering kdb (current=0xc96dc00, pid 803) on processor 1
> > Oops: Oops
> >   due to oops @ 0xd08490bf ...
> >
> > The process listing showed that xfs was pid 803.
>
>
> Hmm, the xfs process is the x font server, nothing directly to do with
> xfs itself. However, obviously xfs is at the back of your problem. Can
> you provide a backtrace from kdb after it drops into the debugger,
> just type bt at this point. I really want to see the rest of the stack
> here.
>
> When the folks in Australia who have been doing dump restore on xfs linux
> get in, perhaps they can look into testing with amanda, I suspect hitting
> your problem is going to take a little work internally though.
>
> Thanks
>
>    Steve
>
>
>
> >
> > I have been unable to reliable recreate the failure.  Sometimes it fails,
> > and some times it does not.  (It does seem to fail more reliably in the
> > morning :) )  I am backing up about 2G of files produced by the news
> > servers.  Any ideas?
> >
> > The machine is a Dual 500 MHz PIII, and the filesystems run on top of the
> > 3ware IDE raid card with 4 46G disks running in RAID level 5.  (138G
> > filesystem available...)  The XFS is the 2.4.3 version from April 5th.
> >
> >
> >
> >                             .justin.
> >
> > ------------------------------------------------------------------------
> > Justin Leonard Tripp                                   justin@xxxxxxxxxx
> > Configurable Computing Laboratory Research Assistant      CB 461 x8-7206
> > Electrical and Computer Engineering Department  Brigham Young University
> >
> >
>
>
>


<Prev in Thread] Current Thread [Next in Thread>