xfs
[Top] [All Lists]

Re: kernel patch fail with LVM

To: Rocky Lee <rocky_lee@xxxxxxxxxxxxxx>
Subject: Re: kernel patch fail with LVM
From: Nathan Scott <nathans@xxxxxxx>
Date: Thu, 27 Mar 2003 17:18:15 +1100
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <002401c2f418$163e4f90$c70aa8c0@xxxxxxxxxxxxxxxxx>
References: <002401c2f418$163e4f90$c70aa8c0@xxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.3i
On Thu, Mar 27, 2003 at 12:19:40PM +0800, Rocky Lee wrote:
> hi all
> 
> I patch the LVM 1.0.7 (1.0.6) patch file and XFS patch file for kernel
> 2.4.19
> , but fail when I ddid "make bzImage"
> 
> Error Message------------------------------------------------------------
> 
> fs/fs.o: In function `fsync_dev_lockfs':
> fs/fs.o(.text+0x32cd): undefined reference to `DQUOT_SYNC'
> make[1]: *** [kallsyms] Error 1
> make[1]: Leaving directory `/usr/src/linux-2.4.19'
> 
> ----------------------------------------------------------------------------
> --
> 
> if I only "make bzImage" with LVM patch, OK
> if I only "make bzImage" with XFS patch, OK
> if I make with LVM and XFS patch..... fail...
> 
> does anyone know this condition?
> 

We have Jan Kara's 32 bit quota patches in our tree, because
we make use of some quota extensions they provide.  The LVM
patch most likely is just for a stock-standard 2.4.20, which
does not have these patches.

So, Jan's patches contain a change which removes DQUOT_SYNC
and instead splits the functionality into a DQUOT_SYNC_DEV
and a DQUOT_SYNC_SB - you'll need to change the code (looks
like fsync_dev_lockfs needs this change) to make use of one
of these new macros.

cheers.

-- 
Nathan


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