<br><br><div class="gmail_quote">On Wed, Jan 28, 2009 at 10:32 PM, Erez Zadok <span dir="ltr"><<a href="mailto:ezk@cs.sunysb.edu" target="_blank">ezk@cs.sunysb.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>In message <<a href="mailto:1233134703.3005.47.camel@zeus.themaw.net" target="_blank">1233134703.3005.47.camel@zeus.themaw.net</a>>, Ian Kent writes:<br>
> On Tue, 2009-01-27 at 18:34 +0530, Nitin Bhardwaj wrote:<br>
<br>
</div>[..]<br>
<div>> > The dmesg output is as follows:<br>
> ><br>
> > unionfs: Unknown symbol vfs_splice_from<br>
> > unionfs: Unknown symbol krealloc<br>
> > unionfs: Unknown symbol lookup_one_len_nd<br>
> > unionfs: Unknown symbol vfs_splice_to<br>
> > unionfs: Unknown symbol vfs_path_lookup<br>
><br>
> It looks like you haven't built the kernel rpms and updated the kernel<br>
> on the machine you want to use the module on.<br>
><br>
> I think these are changes to the VFS proper made by the patch. They<br>
> won't be available if you try and install the module on a system with a<br>
> stock kernel.<br>
<br>
</div>Ian is correct. The best way to add such a patch to an RPM is to edit the<br>
rpmspec file and add it there, then rpmbuild the RPM.<br>
<font color="#888888"><br>
Erez.</font></blockquote><div><br>Erez/Ian,<br><br>I'm still getting the errors inspite of rebuilding the new kernel;<br>Following are the steps I followed:<br><br>1. Unpacked the kernel-2.6.18-92.el5.src.rpm ( as non-root user)<br>
2. Applied the patch 'unionfs-2.4_for_2.6.18-RHEL5.diff' to the kernel successfully.<br>3. make menuconfig and gave option 'M' for Unionfs under "Layered FileSystems".<br>4. Build the new kernel using rpmbuild command, which built two RPMs successfully:<br>
kernel-2.6.18-92.el5.unionfs.rpm<br> kernel-devel-2.6.18-92.el5.unionfs.rpm<br>5. (as root) Installed the new rpm<br> rpm -ivh kernel-2.6.18-92.el5.unionfs.rpm<br> which gave warnings:<br>WARNING: /lib/modules/2.6.18-92.el5.unionfs/kernel/fs/unionfs/unionfs.ko needs unknown symbol vfs_splice_from<br>
WARNING: /lib/modules/2.6.18-92.el5.unionfs/kernel/fs/unionfs/unionfs.ko needs unknown symbol krealloc<br>WARNING: /lib/modules/2.6.18-92.el5.unionfs/kernel/fs/unionfs/unionfs.ko needs unknown symbol lookup_one_len_nd<br>
WARNING: /lib/modules/2.6.18-92.el5.unionfs/kernel/fs/unionfs/unionfs.ko needs unknown symbol vfs_splice_to<br>WARNING: /lib/modules/2.6.18-92.el5.unionfs/kernel/fs/unionfs/unionfs.ko needs unknown symbol vfs_path_lookup<br>
<br>6. Rebooted the system into the new kernel<br><br>Tried modprobe unionfs, which gave the same errors in dmesg, which I mentioned in my earlier mail.<br><br><br>Here's what Dave suggested when I inquired about his progress on RHEL+unionfs:<br>
<br>[...]<br><br>
>I haven't been working on it since then actually, and haven't had a<br>
>chance to get back to it. Traditionally, RHEL likes to backport patches<br>
>from newer upstream kernels. This tends to break the unionfs patches<br>
>because they're typically designed to match up to specific kernels, and<br>
>the RHEL kernels essentially become a hybrid somewhere in between<br>
>different versions.<br>
><br>
>Usually every time Red Hat releases a new kernel for RHEL, someone has<br>
>to unpack the kernel SRPM and tarball the build directory and ship it<br>
>off to Erez and let him backport to it specifically. I know for sure<br>
>there's been new RHEL kernels since the last RHEL patch was made, so<br>
>it's probably time to do that again.<br>
><br>><font color="#888888">--<br>
</font>><font color="#888888">Dave Miller <a href="http://www.justdave.net/" target="_blank">http://www.justdave.net/</a><br>
</font>><font color="#888888">System Administrator, Mozilla Corporation <a href="http://www.mozilla.com/" target="_blank">http://www.mozilla.com/</a><br>
</font>><font color="#888888">Project Leader, Bugzilla Bug Tracking System <a href="http://www.bugzilla.org/" target="_blank">http://www.bugzilla.org/</a></font> <br><br><br>Am i doing some step incorrectly or missing something here ? Or ( as
Dave Miller suggested) , we need a new patch release for RHEL 5.2 (
2.6.18-92.el5 ) , as Dave was sure Redhat has released a new kernel
after Erez gave that last patch for RHEL (unionfs-2.4_for_2.6.18-RHEL5.<div>diff) ?<br>
<br></div><br><br>Thanks,<br>Nitin.<br><br></div></div><br>