search for: zio_nowait

...+0x6e(ffffff008f722790) zio_next_stage+0xb3(ffffff008f722790) zio_write_compress+0x239(ffffff008f722790) zio_next_stage+0xb3(ffffff008f722790) zio_wait_for_children+0x5d(ffffff008f722790, 1, ffffff008f7229e0) zio_wait_children_ready+0x20(ffffff008f722790) zio_next_stage_async+0xbb(ffffff008f722790) zio_nowait+0x11(ffffff008f722790) dmu_objset_sync+0x196(ffffff008e4e5000, ffffff008f722a10, ffffff008f260a80) dsl_dataset_sync+0x5d(ffffff008df47e00, ffffff008f722a10, ffffff008f260a80) dsl_pool_sync+0xb5(ffffff00882fb800, 3fd0f1) spa_sync+0x1c5(ffffff008f2d1a80, 3fd0f1) txg_sync_thread+0x19a(ffffff00882fb800...

...61b84 zfs:zio_next_stage+aa (88e56dc0) 87a61bd0 zfs:zio_write_compress+2c8 (88e56dc0) 87a61bec zfs:zio_next_stage+aa (88e56dc0) 87a61c0c zfs:zio_wait_for_children+46 (88e56dc0, 1, 88e56f) 87a61c20 zfs:zio_wait_children_ready+18 (88e56dc0) 87a61c34 zfs:zio_next_stage_async+ac (88e56dc0) 87a61c48 zfs:zio_nowait+e (88e56dc0) 87a61c94 zfs:dmu_objset_sync+184 (85fe96c0, 88757ae0,) 87a61cbc zfs:dsl_dataset_sync+40 (813ad000, 88757ae0,) 87a61d0c zfs:dsl_pool_sync+a3 (8291c0c0, 286de2, 0) 87a61d6c zfs:spa_sync+1fc (82a7b900, 286de2, 0) 87a61dc8 zfs:txg_sync_thread+1df (8291c0c0, 0) 87a61dd8 unix:thread_start+8...

...o_start+1d () Sep 13 14:13:22 cypress genunix: [ID 655072 kern.notice] ffffff000840d300 zfs:zio_vdev_io_start+123 () Sep 13 14:13:22 cypress genunix: [ID 655072 kern.notice] ffffff000840d320 zfs:zio_next_stage_async+bb () Sep 13 14:13:22 cypress genunix: [ID 655072 kern.notice] ffffff000840d340 zfs:zio_nowait+11 () Sep 13 14:13:22 cypress genunix: [ID 655072 kern.notice] ffffff000840d380 zfs:vdev_mirror_io_start+18f () Sep 13 14:13:22 cypress genunix: [ID 655072 kern.notice] ffffff000840d3c0 zfs:zio_vdev_io_start+131 () Sep 13 14:13:22 cypress genunix: [ID 655072 kern.notice] ffffff000840d3e0 zfs:zio_ne...

...vdev_io_start+1d () Oct 10 17:24:04 zetta genunix: [ID 655072 kern.notice] ffffff0007f1bab0 zfs:zio_vdev_io_start+123 () Oct 10 17:24:04 zetta genunix: [ID 655072 kern.notice] ffffff0007f1bad0 zfs:zio_next_stage_async+bb () Oct 10 17:24:04 zetta genunix: [ID 655072 kern.notice] ffffff0007f1baf0 zfs:zio_nowait+11 () Oct 10 17:24:04 zetta genunix: [ID 655072 kern.notice] ffffff0007f1bb50 zfs:vdev_queue_io_done+a5 () Oct 10 17:24:04 zetta genunix: [ID 655072 kern.notice] ffffff0007f1bb90 zfs:vdev_disk_io_done+29 () Oct 10 17:24:04 zetta genunix: [ID 655072 kern.notice] ffffff0007f1bbb0 zfs:vdev_io_done+1d...

Hello zfs-discuss, http://sunsolve.sun.com/search/document.do?assetkey=1-1-6604198-1 Is there a patch for S10? I thought it''s been fixed. -- Best regards, Robert mailto:rmilkowski at task.gda.pl http://milek.blogspot.com

I''m observing the following behavior in our environment (Sol10U2, E2900, 24x96, 2x2Gbps, ...) - I''ve a compressed ZFS filesystem where I''m creating a large tar file. I notice that the tar process is running fine (accumulating CPU, truss shows writes, ...) but for whatever reason the timestamp on the file doesn''t change nor does the file size change. The same is

..._next_stage+66 (e4385ac0) d2c8a800 zfs:zio_checksum_generate+5e (e4385ac0) d2c8a81c zfs:zio_next_stage+66 (e4385ac0) d2c8a83c zfs:zio_wait_for_children+46 (e4385ac0, 1, e4385c) d2c8a850 zfs:zio_wait_children_ready+18 (e4385ac0) d2c8a864 zfs:zio_next_stage_async+ac (e4385ac0, f8def9d0,) d2c8a874 zfs:zio_nowait+e (e4385ac0) d2c8a8d4 zfs:zio_write_allocate_gang_members+341 (e120e0c0) d2c8a8f0 zfs:zio_dva_allocate+81 (e120e0c0) d2c8a908 zfs:zio_next_stage+66 (e120e0c0) d2c8a920 zfs:zio_checksum_generate+5e (e120e0c0) d2c8a93c zfs:zio_next_stage+66 (e120e0c0) d2c8a95c zfs:zio_wait_for_children+46 (e120e0c0,...

I just had a quick play with gzip compression on a filesystem and the result was the machine grinding to a halt while copying some large (.wav) files to it from another filesystem in the same pool. The system became very unresponsive, taking several seconds to echo keystrokes. The box is a maxed out AMD QuadFX, so it should have plenty of grunt for this. Comments? Ian

Currently I''m trying to figure out the best zfs layout for a thumper wrt. to read AND write performance. I did some simple mkfile 512G tests and found out, that per average ~ 500 MB/s seems to be the maximum on can reach (tried initial default setup, all 46 HDDs as R0, etc.). According to http://www.amd.com/us-en/assets/content_type/DownloadableAssets/ArchitectureWP_062806.pdf I would

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

...ffffff000fd0a420 zfs:zio_next_stage+b3 () ffffff000fd0a490 zfs:zio_write_compress+239 () ffffff000fd0a4b0 zfs:zio_next_stage+b3 () ffffff000fd0a500 zfs:zio_wait_for_children+5d () ffffff000fd0a520 zfs:zio_wait_children_ready+20 () ffffff000fd0a540 zfs:zio_next_stage_async+bb () ffffff000fd0a560 zfs:zio_nowait+11 () ffffff000fd0a870 zfs:dbuf_sync_leaf+1ac () ffffff000fd0a8b0 zfs:dbuf_sync_list+51 () ffffff000fd0a900 zfs:dbuf_sync_indirect+cd () ffffff000fd0a940 zfs:dbuf_sync_list+5e () ffffff000fd0a9b0 zfs:dnode_sync+23b () ffffff000fd0a9f0 zfs:dmu_objset_sync_dnodes+55 () ffffff000fd0aa70 zfs:dmu_objset...