Date: Thu, 25 Mar 2004 19:19:08 +0000 From: Momtchil Momtchev <momtchil.momtchev@netasq.com> To: freebsd-fs@freebsd.org Subject: Problem (potential bug) in the vnode disk driver, stable branch Message-ID: <200403251919.08564.momtchil.momtchev@netasq.com>
index | next in thread | raw e-mail
Hello, We've stumbled on what appears to be a bug in the vnode disk driver. It happens rarely and we aren't able to reproduce it atm, but we've seen it already a few times on different kernels, compiled with different options. If you can read russian, there's also a brief description of what appears to be exactly the same problem at http://www.j2.ru/frozenfido/ru.unix.bsd/89061df31001.html. Theirs is on FreeBSD 4.3, we are running FreeBSD 4.9. What happens is that after mounting a file as a filesystem through the vn driver, everything will run fine, then eventually (after a few days, weeks or even months) the filesystem is going to get "disconnected" in a strange way with every attempt to access it returning an I/O error. vnconfig will report "device not configured": #/usr/sbin/vnconfig -c /dev/vn0c /somefile vnconfig: /dev/vn0c: Device not configured #vnconfig -u /dev/vn0c vnconfig: /dev/vn0c: Device not configured umount/mount will fail too. We are still trying to find a way to reliably reproduce the problem in order to fill a standard bug report. ATM we don't have any idea what could trigger it. The main problem is that it happens very rarely and we can't really afford to run a kernel with all the debugging enabled on thousands of hosts (to catch the few which will crash). Anyone seen this before? Any comments will be appreciated. -- Momtchil Momtchev, R&D Engineer <momtchil.momtchev@netasq.com> Netasq - Secure Internet Connectivity http://www.netasq.com Tél : +33 320 619 630 Fax : +33 320 619 639home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403251919.08564.momtchil.momtchev>