[gmx-users] Failed to lock: md.log. No locks available.
Mark.Abraham at anu.edu.au
Fri Jan 13 09:57:55 CET 2012
On 13/01/2012 7:08 PM, lina wrote:
> Failed to lock: md.log. No locks available.
mdrun locks various files at various points. If it can't then GROMACS
won't continue, but the problem lies with the file system, and not with
GROMACS. Possibly some phantom process still thinks it owns the file.
> still the same problem I met before,
> once I terminated, resume not work, there is a md.log file.
> $ mount
> /dev/sda1 on / type ext3 (rw)
> none on /proc type proc (rw)
> none on /sys type sysfs (rw)
> none on /dev/pts type devpts (rw,gid=5,mode=620)
> usbfs on /proc/bus/usb type usbfs (rw)
> none on /dev/shm type tmpfs (rw)
> none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
> sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
> honeydewlocal:/vol/hpc_vol/HomeHPC on /home type nfs
> The /home is mounting on the last one.
> CPU: 8 Intel(R) Xeon(R) Dual-Core 3.33 Ghz
> Memory: 114GB RAM
> HDD Size: 744GB
> OS: CentOS 4 (64-bits)
> Thanks for any suggestions,
> any additional info you need please let me know,
> Best regards,
More information about the gromacs.org_gmx-users