On Thu, 2 Apr 2009, Kadlecsik Jozsef wrote: > If you have any idea what to do next, please write it. Spent again some time looking through the git commits and that triggered some wild guessing: - commit ddebb0c3dc7d0b87c402ba17731ad41abdd43f2d ? It is a temporary fix for 2.6.26, which is additionally based on a kludge and I'm trying 2.6.27/28. Might be not appropriate anymore for these kernels? - commit d9c3e59e90437567d063144bcfdbbc9fe6e8d615 ? (and other noatime related commits) Noatime handling and I do use noatime. Hm, I could try to start mailman without noatime and we'll see what happens. - commit ff7d89bfe60ed041d9342c8c9d91815c1f3d3bef ? gfs1-specific lock module, a huge patch. I could restore the gfs2_*lock* functions and check whether it helps. - commit 82d176ba485f2ef049fd303b9e41868667cebbdb gfs_drop_inode as .drop_inode replacing .put_inode. .put_inode was called without holding a lock, but .drop_inode is called under inode_lock held. Might it be a problem? What do you think? Best regards, Jozsef -- E-mail : kadlec@xxxxxxxxxxxx, kadlec@xxxxxxxxxxxxxxxxx PGP key: http://www.kfki.hu/~kadlec/pgp_public_key.txt Address: KFKI Research Institute for Particle and Nuclear Physics H-1525 Budapest 114, POB. 49, Hungary -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
