search for: bdev_strategi

I''m running OpenSolaris 2008.05 in VirtualBox on a Windows XP host. Playing around with various probes, I found that trying to load any probe associated with bdev_strategy dumps core. I can think of one or two likely and reasonable causes for this, but am assuming it''s undesirable behavior. Anyone know what''s happening here? -- This message posted from

I''ve been looking into the performance impact of NCQ. Here''s what i found out: http://blogs.sun.com/erickustarz/entry/ncq_performance_analysis Curiously, there''s not too much performance data on NCQ available via a google search ... enjoy, eric

Hello, I can see that there is an implementation/emulation of ddi_pathname in DTrace, but I''m a bit confused about the capabilities and invocation of this function. I would like to diplay the path to the block device from bdev_strategy and other io:genunix::start probes. If someone is familiar with ddi_pathname, could you please provide an example invocation? Thanks, Michael This

Hi, I''m working on some performance analysis with our database and it seems that when the file system (UFS) is mounted with forcedirectio, the IO probe are not triggered when an I/O event occurs. Could you confirm that ? If so, why ? Seb -- This message posted from opensolaris.org

Hi. Just migrated to zfs on opensolaris. I copied data to the server using rsync and got this message: Oct 10 17:24:04 zetta ^Mpanic[cpu1]/thread=ffffff0007f1bc80: Oct 10 17:24:04 zetta genunix: [ID 683410 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ffffff0007f1b640 addr=fffffffecd873000 Oct 10 17:24:04 zetta unix: [ID 100000 kern.notice] Oct 10 17:24:04 zetta unix: [ID 839527 kern.notice]

Hi, I know how to trace the number of bytes read/written by a program by summing the argument of that read/write syscall. However, the way the OS services read/write calls is in blocks. I wonder if it''s possible to trace the actual number of blocks read/written caused by the syscalls? -- This message posted from opensolaris.org

I?d like to report the ZFS related crash/bug described below. How do I go about reporting the crash and what additional information is needed? I?m using my own very simple test app that creates numerous directories and files of randomly generated data. I have run the test app on two machines, both 64 bit. OpenSolaris crashes a few minutes after starting my test app. The crash has occurred on

Now at 36 hours since zdb process start and: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 827 root 4936M 4931M sleep 59 0 0:50:47 0.2% zdb/209 Idling at 0.2% processor for nearly the past 24 hours... feels very stuck. Thoughts on how to determine where and why? -- This message posted from opensolaris.org