Thanks …

# procstat -kk 64529
  PID    TID COMM             TDNAME           KSTACK                       
64529 100963 du               -                mi_switch+0x186 sleepq_wait+0x42 
__lockmgr_args+0x5cb nfs_lock1+0x4a VOP_LOCK1_APV+0x46 _vn_lock+0x47 vget+0x70 
cache_lookup_times+0x54f nfs_lookup+0x17e lookup+0x42f namei+0x4ac 
vn_open_cred+0x3bd kern_openat+0x20a amd64_syscall+0x540 Xfast_syscall+0xf7

On 2013-02-09, at 9:58 PM, Jeremy Chadwick <j...@koitsu.org> wrote:

> Off-list:
> 
> Marc,
> 
> You may want to also provide output from "procstat -kk 64529", as this
> will give a full thread calling stack.
> 
> The -kk (double-kay) is not a typo.  :-)
> 
> -- 
> | Jeremy Chadwick                                   j...@koitsu.org |
> | UNIX Systems Administrator                http://jdc.koitsu.org/ |
> | Mountain View, CA, US                                            |
> | Making life hard for others since 1977.             PGP 4BD6C0CB |
> 
> On Sat, Feb 09, 2013 at 09:29:30PM -0800, Marc Fournier wrote:
>> 
>> Hi John ?
>> 
>>   Does this help?
>> 
>> root@io:~ # ps auxl | grep du
>> root     1054   0.0  0.1  16176  6600 ??  D     3:15AM     0:05.38 du -skx 
>> /vm/2799     0 81426   0  20  0 newnfs
>> root    12353   0.0  0.1  16176  5104 ??  D    Sat03AM     0:05.41 du -skx 
>> /vm/2799     0 91597   0  20  0 newnfs
>> root    64529   0.0  0.1  16176  5164 ??  D    Fri03AM     0:05.40 du -skx 
>> /vm/2799     0 43227   0  20  0 newnfs
>> root    12855   0.0  0.0  16308  1988  0  S+    5:26AM     0:00.00 grep du   
>>            0 12847   0  20  0 piperd
>> root@io:~ # grep vm /etc/fstab
>> 192.168.1.254:/vol/basic /vm            nfs     rw,nolockd,intr 0       0
>> 
>> Haven't rebooted yet ? if there is anything I can do / try before ? ?
>> 
>> The kernel is from Jan 21st ?
>> 
>> 
>> On 2013-01-19, at 4:57 AM, John Baldwin <j...@freebsd.org> wrote:
>> 
>>> On Tuesday, December 18, 2012 11:58:36 PM Hub- Marketing wrote:
>>>> I'm running a few servers sitting on top of a NetAPP file server ?
>>>> everything runs great, but periodically I'm getting:
>>>> 
>>>> nfs_getpages: error 13
>>>> vm_fault: pager read error, pid 11355 (https)
>>> 
>>> Are you using interruptible mounts ("intr" mount option)?
>>> 
>>> Also, can you get ps output that includes the 'l' flag to show what
>>> the processes are stuck on?
>>> 
>>> -- 
>>> John Baldwin
>> 
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Reply via email to