xfs
[Top] [All Lists]

Re: xfsdump failing on sparc64

To: Alvaro Figueroa <fede2@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: xfsdump failing on sparc64
From: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 29 Apr 2002 08:41:50 +1000
Cc: XFS to linux port mailing list <linux-xfs@xxxxxxxxxxx>
In-reply-to: <1020032899.7548.51.camel@lucy>; from fede2@xxxxxxxxxxxxxxxxxxxxx on Sun, Apr 28, 2002 at 04:28:18PM -0600
References: <1020010922.7552.29.camel@lucy> <20020429082656.O83002@xxxxxxxxxxxxxxxxxxxxxxxx> <1020032899.7548.51.camel@lucy>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
hi,

On Sun, Apr 28, 2002 at 04:28:18PM -0600, Alvaro Figueroa wrote:
> > Sounds like you have an old xfsdump with a new kernel... which
> > kernel version and which xfsdump version are you using?  If your
> > kernel is >=2.4.18 (or the 1.1 release) you will need 2.0+ tools.
> 
> I'm running a 2.4.18 kernel taken from the CVS a couple of days ago.
> 
> And xfsdump --help claims its a 3.0.

Yeah, that version numbers not helpful, sorry.  We should fix that -
its leftover from IRIX.

To get the real version...
"rpm -q xfsdump", if you use rpm;
"dpkg -s xfsdump", if you use dpkg;
...or xfs_fsr -V will tell you the real package version.

> (BTW, I've just excecuted xfsdump --version, and take a look at its
> output (at the end)
> 
> (...)
>                         [ -Y <I/O buffer ring length> ]
>                         [ - (stdout) ]
>                         [ <source (mntpnt|device)> ]
> xfsdump: qlock.c:291: qlock_lock: Assertion `qlock_inited' failed.
> Aborted

Hmm... another one for the xfsdump guys to have a look at.

thanks.

-- 
Nathan


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