https://bugzilla.novell.com/show_bug.cgi?id=415640 Summary: kblockd locks file and won't let go Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jimc@math.ucla.edu QAContact: kernel-maintainers@forge.provo.novell.com Found By: Customer This is with kernel 2.6.22.18-0.2-default, no hacks, online updates are up to date, but no other recent (or ancient) changes to the system. My application uses a write (exclusive) fcntl lock on a file, updates it, and releases the lock. Other programs get a read fcntl lock, read the file, then release the lock. The file is on the local host (ext3, RAID). We've been using these apps with no changes since the previous millenium. 4 days ago it hung; the sysop on duty could not break the lock and "cured" it by rebooting the server. The write lock was acquired successfully on subsequent days, maybe 5 times. Today it happened again. The relevant items from /proc/locks are: 33: POSIX ADVISORY READ 39 08:11:456969 0 EOF 33: -> POSIX ADVISORY WRITE 19027 08:11:456969 0 EOF 456969 is the inode of my file. 19027 is my application. 39 is [kblockd/2]. We thought about killing the kernel thread to see what would happen, but in the end decided to play it safe and reboot again. (I don't actually know if the previous event involved kblockd.) /usr/src/linux/block/ll_rw_blk.c is the source for kblockd. I can't see any code relevant to locking the file itself. A web search reveals a few complaints about kblockd but none involving locking. Does anyone recognize anything sane about this scenario? What I will be doing in the meantime: If it happens again I'll make sure our people find out for sure what processes hold the lock. I will put together a test program, simulating our usage, and see if I can get it to fail consistently. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.