panic: NTFS VOP_STRATEGY failed

From: Doug Barton <dougb_at_FreeBSD.org>
Date: Tue, 08 Jan 2008 00:05:09 -0800
John Baldwin wrote:
> On Wednesday 26 December 2007 06:01:47 pm Doug Barton wrote:
>> I have a dual boot system, and from time to time I use mount_ntfs to read 
>> stuff from the windows partition. Doing that today I got the following 
>> with a system built on 23 December:
>>
>> #0  doadump () at pcpu.h:195
>> 195	pcpu.h: No such file or directory.
>>  	in pcpu.h
>> (kgdb) bt
>> #0  doadump () at pcpu.h:195
>> #1  0xc056a0ae in boot (howto=260)
>>      at /usr/local/src/sys/kern/kern_shutdown.c:409
>> #2  0xc056a36b in panic (fmt=Variable "fmt" is not available.
>> ) at /usr/local/src/sys/kern/kern_shutdown.c:563
>> #3  0xc05586a2 in _lockmgr (lkp=0xc90049e8, flags=8212, 
>> interlkp=0xc9004a18,
>>      td=0xc92d5220, file=0xc077c0ed "/usr/local/src/sys/kern/vfs_subr.c",
>>      line=2213) at /usr/local/src/sys/kern/kern_lock.c:319
> 
> We'd need the actual panic message I think.

Sure. I updated my -current tonight, then did the following:

mount_ntfs /dev/ad0s1 /mnt/tmp
cd /mnt/tmp
find .
IFS='
'
for file in `find . -type f`; do
cp $file /tmp
rm /tmp/${file##*/}
done

Took about 45 seconds to panic with:

ntfs_strategy: ntfs_readattr failed
panic: NTFS VOP_STRATEGY failed:
bp=0xd9369988, vp=0xc9a55880, rc=7
cpuid=1

hth,

Doug

-- 

    This .signature sanitized for your protection
Received on Tue Jan 08 2008 - 07:05:11 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:25 UTC