Jos Vos wrote:
On Fri, Oct 26, 2007 at 07:57:18PM -0400, Wendy Cheng wrote:

2. The gfs_scand issue is more to do with the number of glock count. One way to tune this is via purge_glock tunable. There is an old write-up in: http://people.redhat.com/wcheng/Patches/GFS/readme.gfs_glock_trimming.R4 . It is for RHEL4 but should work the same way for RHEL5.

Unfortunately, no.  The patch applies fine (only with some offsets),
but building results in an error:
The patch on my people's page is a *RHEL4* patch.

Just did a quick check, RHEL5.1 gfs-kmod-0.1.19 should have this patch and will be released *very soon*. Mind to wait for a little bit longer to get an "official" version ? Or go to our cvs (which is open to everyone) to extract the source yourself ?

-- Wendy
  CC [M]  /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/acl.o
  CC [M]  /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/bits.o
  CC [M]  /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/bmap.o
  CC [M]  /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/daemon.o
  CC [M]  /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/dio.o
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/dio.c: In function 
'stuck_releasepage':
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/dio.c:85: warning: 
format '%lu' expects type 'long unsigned int', but argument 3 has type 
'sector_t'
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/dio.c:96: warning: 
format '%lu' expects type 'long unsigned int', but argument 4 has type 'u64'
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/dio.c:122: warning: 
format '%lu' expects type 'long unsigned int', but argument 3 has type 
'uint64_t'
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/dio.c:122: warning: 
format '%lu' expects type 'long unsigned int', but argument 4 has type 
'uint64_t'
  CC [M]  /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/dir.o
  CC [M]  /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/eaops.o
  CC [M]  /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/eattr.o
  CC [M]  /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/file.o
  CC [M]  /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.o
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.c: In function 
'try_purge_iopen':
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.c:2563: error: 
implicit declaration of function 'gl2gl'
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.c:2563: 
warning: assignment makes pointer from integer without a cast
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.c: In function 
'dump_inode':
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.c:2844: 
warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 
'uint64_t'
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.c:2844: 
warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 
'uint64_t'
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.c:2844: 
warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 
'uint64_t'
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.c:2844: 
warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 
'uint64_t'
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.c: In function 
'dump_glock':
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.c:2882: 
warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 
'u64'
/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.c:2882: 
warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 
'u64'
make[4]: *** 
[/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/glock.o] Error 1
make[3]: *** 
[_module_/builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs] Error 2

Regards,


--
Linux-cluster mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-cluster

Reply via email to