xfs
[Top] [All Lists]

Re: xfs module insert fails with "xfs: Unknown symbol exportfs_decode_fh

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: xfs module insert fails with "xfs: Unknown symbol exportfs_decode_fh (err 0)"
From: Chandra Seetharaman <sekharan@xxxxxxxxxx>
Date: Fri, 26 Apr 2013 13:29:14 -0500
Cc: XFS mailing list <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <517AC13D.9000802@xxxxxxxxxxx>
Organization: IBM
References: <1366997050.4098.14.camel@xxxxxxxxxxxxxxxxxx> <517AC13D.9000802@xxxxxxxxxxx>
Reply-to: sekharan@xxxxxxxxxx
On Fri, 2013-04-26 at 13:02 -0500, Eric Sandeen wrote:
> On 4/26/13 12:24 PM, Chandra Seetharaman wrote:
> > Hello,
> > 
> > When I tried to insert xfs module in my test machine it failed with 
> > 
> >     xfs: Unknown symbol exportfs_decode_fh (err 0).
> 
> so don't use insmod, use modprobe :)
> 

yup. It is the problem. Config seems to be fine.

false alarm.
> > Found out that I did not have CONFIG_EXPORTFS enabled in my kernel
> > config. 
> 
> Oh, hum. But fs/xfs/Kconfig:
> 
> config XFS_FS
>         tristate "XFS filesystem support"
>         depends on BLOCK
>         select EXPORTFS
> 
> it should be turned on automatically.  That seems to be the problem,
> why wasn't it for your case?
> 
> > All .*by_handle code in XFS is open coded. Wondering if they should be
> > under #ifdef CONFIG_EXPORTFS ?
> 
> CONFIG_EXPORTFS is supposed to be on if xfs is selected, unless something
> changed recently.
> 
> -Eric
> 
> > I can create a patch, but wanted to find out if it is indeed needed :)
> > 
> > Regards,
> > 
> > Chandra
> > 
> > 
> > 
> > 
> > _______________________________________________
> > xfs mailing list
> > xfs@xxxxxxxxxxx
> > http://oss.sgi.com/mailman/listinfo/xfs
> > 
> 
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs
> 


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