panic when umounting a msdosfs mount: "VOP_STDCLOSE: BAD WRITECOUNT 0xf2629e68 0"

Matthew Dillon dillon at
Tue May 20 11:26:59 PDT 2008

:After playing with my mobile phone (mounted it's memory card with mount -t
:msdosfs), a umount triggered the panic (well, I did run sync a second or 2
:before doing a umount). The memory dump is at leaf:~rumko/crash/19.05.2008/
:and the backtrace (including the kernel message buffer that kgdb prints) is
:Unread portion of the kernel message buffer:
:panic: VOP_STDCLOSE: BAD WRITECOUNT 0xf2629e68 0
:mp_lock = 00000001; cpuid = 1
:boot() called on cpu#1
:syncing disks... 3 ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue
:timeout - completing request directly
:ad8: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=12361855

    Did you mount it normally or use options like -o ro (read-only), or
    -u (update) at any point ?

    And, is the panic reproducable?

					Matthew Dillon 
					<dillon at>

More information about the Bugs mailing list