NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: iscsi initiator troubles



Manuel: 

Using the 5.1-generic kernel, i reproduced the hang. 'top' stayed running and 
is posted below. The free mem started at about 7500MB before the first file 
copy, and remained at about 6500- 6900MB as seen below: 

load averages: 0.01, 0.04, 0.01; up 0+00:18:52 17:47:49 
24 processes: 22 sleeping, 2 on CPU 
CPU0 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle 
CPU1 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle 
CPU2 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle 
CPU3 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle 
Memory: 755M Act, 1124K Wired, 6328K Exec, 737M File, 6849M Free 
Swap: 129M Total, 129M Free 

PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 
0 root 0 0 0K 29M CPU/3 0:01 0.00% 0.00% [system] 
478 root 43 0 7620K 1376K CPU/0 0:00 0.00% 0.00% top 
464 root 85 0 35M 4404K select/0 0:00 0.00% 0.00% sshd 
473 root 85 0 35M 4404K select/0 0:00 0.00% 0.00% sshd 
443 root 85 0 35M 4336K select/0 0:00 0.00% 0.00% sshd 
396 root 85 0 25M 3548K netio/3 0:00 0.00% 0.00% iscsi-initia 
376 postfix 85 0 12M 2384K kqueue/1 0:00 0.00% 0.00% qmgr 
399 postfix 85 0 12M 2348K kqueue/2 0:00 0.00% 0.00% pickup 
359 root 85 0 12M 2320K kqueue/2 0:00 0.00% 0.00% master 
282 root 85 0 24M 2064K select/0 0:00 0.00% 0.00% sshd 
458 root 85 0 14M 1548K pager_/0 0:00 0.00% 0.00% iscsi-target 
444 root 85 0 6668K 1420K wait/3 0:00 0.00% 0.00% sh 
484 root 85 0 6668K 1364K wait/0 0:00 0.00% 0.00% sh 
469 root 85 0 6668K 1364K wait/0 0:00 0.00% 0.00% sh 
146 root 85 0 6528K 1280K select/1 0:00 0.00% 0.00% rpcbind 
125 root 85 0 6540K 1112K kqueue/1 0:00 0.00% 0.00% syslogd 
209 root 85 0 6536K 1104K select/1 0:00 0.00% 0.00% rpc.statd 
438 root 85 0 6496K 1104K ttyraw/3 0:00 0.00% 0.00% getty 
211 root 85 0 6556K 1048K select/0 0:00 0.00% 0.00% rpc.lockd 
1 root 85 0 6516K 1040K wait/3 0:00 0.00% 0.00% init 
404 root 85 0 5464K 1040K nanosl/0 0:00 0.00% 0.00% cron 
427 root 85 0 7608K 1024K kqueue/0 0:00 0.00% 0.00% inetd 
613 root 85 0 4396K 924K pager_/3 0:00 0.00% 0.00% cp 
483 root 85 0 4332K 776K kqueue/1 0:00 0.00% 0.00% tail 



----- Original Message -----

From: "Manuel Bouyer" <bouyer%antioche.eu.org@localhost> 
To: "John Jaser" <john%jaser.net@localhost> 
Cc: netbsd-users%NetBSD.org@localhost 
Sent: Wednesday, September 28, 2011 5:12:23 PM 
Subject: Re: iscsi initiator troubles 

On Mon, Sep 26, 2011 at 06:34:13PM -0400, John Jaser wrote: 
> Hi, 
> 
> 
> 
> I've been struggling for a few days getting iscsi_initiator talking to a 
> netbsd 5.1 iscsi-target. The iscsi-target has been performing well for about 
> a 
> solid week as a back-end for a debian 6.0 xen server using open-iscsi. 
> Getting 
> a netbsd 5.1 xen server to do the same has been the challenge. All systems 
> are 
> amd64 with 8G RAM, using amd64 kernels. 
> 
> 
> 
> The symptom is not apparent until file creation, but happens rather quickly. 
> The file copy or dd empty-file creation will just hang, or sometimes barely 
> get started. The system becomes unresponsive. The 'top' process list in 
> another terminal continues to run, and shows almost no load (too low) even on 
> the iscsi-initiator process and the dd or cp process. New terminal logins 
> work, but any command other than an 'ls' hangs also, and the situation 
> deteriorates until a dirty restart is required. I also tried using 
> iscsi_initiator on the iscsi-target system with similar results. Lastly, I 
> tried enabling iscsi-target on the iscsi_initiator host itself, and got the 
> same result. That session is below. Of interest may be the two errors in the 
> syslog followed by the successful login. I tried the 5.1-XEN kernel(with 
> puffs), the generic 5.1 kernel, and a current kernel from last week; all gave 
> same result. Seems almost like some kind of deadlock, since the load is so 
> low. Any tips would be greatly appreciated. 

When doing this, did you watch if the free memory becomes too low 
(top should tell you that) 

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost> 
NetBSD: 26 ans d'experience feront toujours la difference 
-- 


Home | Main Index | Thread Index | Old Index