From: Robert <robert@miraclelinux.com>
To: xfs@oss.sgi.com
Cc: Robert <robert@miraclelinux.com>
Subject: Re: Unresolved generic_file_write_nolock
Date: Thu, 27 Jul 2006 16:37:04 +0900 [thread overview]
Message-ID: <44C86D20.2040908@miraclelinux.com> (raw)
In-Reply-To: <44C7508A.5010500@miraclelinux.com>
Hi
I had solved this problem. I will describe in this email.
At frist, the error message for this issue is as below:
Loading xfs.o module
/lib/xfs.o : unresolved symbol generic_file_write_nolock
ERROR : /bin/insmod exited abnormally
creating block devices
mounting root filesystem
mount : error 19 mounting xfs
.........
I changed all
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2.4.22) || defined\
(KERNEL_HAS_NEW_O_DIRECT)
in fs/xfs/linux/xfs_lrw.c to
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2.4.21) || defined\
(KERNEL_HAS_NEW_O_DIRECT)
and rebuild, install kernel. Everything goes well now.
Please comment.
Thank you
Robert
Robert wrote:
> Hi XFS guys
>
> I like to use XFS but I have a compile question for
>
> xfs-modules-fs-modules-1.3.3-2.4.21-27.0.2.EL.sgi9.src.rpm
>
> which is download from ftp://oss.sgi/com/projects/xfs/testing/RHEL3/
>
>
> I compiled it with kernel-2.4.21-37.EL with normal steps. Everything
> is ok and then I run the command installkernel but got below error
> message like this:
>
> depmod ..... xfs.o
> Unresolved symble : generic_file_write_nolock
>
> Then I had tried to find this function in 2.4.21-37EL and mainstream
> kernel-2.4.32, but it does not exist in them. I refer to SPEC file
> and found this generic_file_write_nolock() already deleted at
> linux-2.4.21-odirect.patch, no more exist. Even in the old kernel
> 2.4.21-20.EL, I can not find it.
>
> This generic_file_write_nolock() is used in xfs/linux/xfs_lrw.c line 745
>
> #if LINUX_VERSION_CODE >= KERNEL_VERSION(2.4.22) || defined\
> (KERNEL_HAS_NEW_O_DIRECT)
> :
> :
> :
> #else
> retry :
> if (ioflags & IO_ISDIRECT) {
> xfs_inval_cached_pages(vp, io, *offset, 1, 1);
> }
> ret = generic_file_write_nolock(file, buf, size, offset);
> #endif
>
> Logically, the #if KERNEL_VERSION_CODE is smaller than 2.4.22.
> The generic_file_write_nolock should be included by C preprocessor.
> So, could you guys tell me why the uploaded RPM:
>
> xfs-modules-smp-1.3.3-2.4.21_27.0.2.EL.sgi9_sgi2.i686.rpm
>
> does not included this function, generic_file_write_nolock?
>
> and Did you compile the xfs-modules with the same kernel
> 2.4.21-27.0.2.EL.sgi9_sgi2?
>
> I can not find generic_file_write_nolock in the System.map of the
> its uploaded RPM :
>
> kernel-smp-2.4.21-27.0.2.EL.sgi9.i686.rpm
>
> This issue take my time for about 1 week and still not solved.
> Any comment is thankfully.
>
> Best Regards
> Robert
>
prev parent reply other threads:[~2006-07-27 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 11:22 Unresolved generic_file_write_nolock Robert
2006-07-27 7:37 ` Robert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44C86D20.2040908@miraclelinux.com \
--to=robert@miraclelinux.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.