#65 lock file misbehavior

open
nobody
5
2005-11-04
2005-11-04
Devin Bayer
No

When I startup UML for the second or subsequent time,
for each ubd device I get this message:

F_SETLK failed, file already locked by pid 5175
Failed to lock '/tmp/configfs_cow0', err = 11
Failed to open '/tmp/configfs_cow0', errno = 11

Everytime the pid is imaginary, so it could not
possibly be holding a lock. Delete the file and
recreating it solves the problem. I am using version
2.6.14.

If you need any more information, let me know. Thanks.

Discussion


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks