xfs
[Top] [All Lists]

Re: error in xfs_logprint?

To: Tang Lingbo <tanglb@xxxxxxxx>
Subject: Re: error in xfs_logprint?
From: Nathan Scott <nathans@xxxxxxx>
Date: Sun, 19 Aug 2001 18:31:43 +1000
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20010815150653.25401.qmail@sina.com>; from tanglb@sina.com on Wed, Aug 15, 2001 at 11:06:52PM +0800
References: <20010815150653.25401.qmail@sina.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
hi there,

On Wed, Aug 15, 2001 at 11:06:52PM +0800, Tang Lingbo wrote:
> Hi,
> 
> There was a core dump in xfs_logprint when I did as follows:
> 

I didn't see a core dump when I ran this, but I did see
the error message you describe below...

> 1)$ dd if=/dev/zero of=/tmp/xfs bs=1024 count=50000
> 2)$ mkfs.xfs /tmp/xfs
> 3)$ mount -t xfs -o loop /tmp/xfs /xfs
> 4)$ touch /xfs/test
> 5)$ for((i=0;i<1024;i++));do echo -n 1 >> /tmp/dummy;done
> 6)$ value=`cat /tmp/dummy`;attr -s test -V $value /xfs/test
> 7)$ xfs_logprint /tmp/xfs
> 
> output:
> 
> ...
> xlog_print_trans_inode: illegal inode type
> 
> And I think the patch will be as follows:
> ...[snip]...
> Any comments?
> 

This patch looks good - I'll apply it shortly if that hasn't
happened already.

Thanks!

-- 
Nathan


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