[Unionfs] modprobe error on CentOS 5.2 (RHEL 5.2)

Nitin Bhardwaj mcabhardwaj at gmail.com
Fri Jan 30 00:44:52 EST 2009


On Fri, Jan 30, 2009 at 9:11 AM, Dave Miller <justdave at mozilla.com> wrote:
>
> Nitin Bhardwaj wrote on 1/29/09 1:57 AM:
[....]
> > 4. Build the new kernel using rpmbuild command, which built two RPMs
> > successfully:
> >      kernel-2.6.18-92.el5.unionfs.rpm
> >      kernel-devel-2.6.18-92.el5.unionfs.rpm
>
> Step 4 probably wiped out your patch.
>

Yeah I suppose thats what was happening, I was not realizing it earlier.

So, following the instructions here:
http://wiki.centos.org/HowTos/Custom_Kernel,  I did the following:

1. Added the patch ( unionfs-2.4_for_2.6.18-RHEL5.diff ) to
~/rpmbuild/SOURCES, and referenced it in ~/rpmbuild/SPECS/kernel-2.6.spec .

2.Turned off the KABI check and provided a new buildid in the
kernel-2.6.spec in ~/rpmbuild/SPECS

3. Build using rpmbuild -bb --target=`uname -m` --with baseonly
kernel-2.6.spec

And bam ! I hit the same build error that Dave mentioned earlier last year
here:
http://www.fsl.cs.sunysb.edu/pipermail/unionfs/2008-July/005893.html

-----------------------------------------------------------
+ make ARCH=i386 nonint_oldconfig
CONFIG_UNION_FS
make[1]: *** [nonint_oldconfig] Error 5
-----------------------------------------------------------

I used the same workaround Dave gave at that time, in the spec file:

for configfile in *.config
do
    echo "CONFIG_UNION_FS=m" >> $configfile
    echo "CONFIG_UNION_FS_XATTR=y">> $configfile
    echo "CONFIG_UNION_FS_DEBUG=y" >> $configfile
done

and the build went fine. I haven't yet tried the new kernel and module, but
Erez mentioned in one of the messages about XATTR support in unionfs thus:

http://www.fsl.cs.sunysb.edu/pipermail/unionfs/2008-May/005849.html

>Andy, there's no xattr support in unionfs for 2.6.18 (the VFS was lacking
>some vital support, I don't recommend it).  So plz turn off
>CONFIG_UNION_FS_XATTR.

However, Without the CONFIG_UNION_FS_XATTR=y insertion into spec file, the
build fails !!

Hence I'm wondering whether will this workaround work ? And do we have a
solution to this issue already, which I may have missed ?


Thanks,
Nitin.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.fsl.cs.sunysb.edu/pipermail/unionfs/attachments/20090130/5f854521/attachment.htm


More information about the unionfs mailing list