search for: zio_write_compress

...genunix`avl_walk+0x20 zfs`metaslab_ff_alloc+0x9c zfs`space_map_alloc+0x10 zfs`metaslab_group_alloc+0x1e0 zfs`metaslab_alloc_dva+0x114 zfs`metaslab_alloc+0x2c zfs`zio_dva_allocate+0x4c zfs`zio_write_compress+0x1ec zfs`arc_write+0xe4 zfs`dbuf_sync+0x6c0 zfs`dnode_sync+0x35c zfs`dmu_objset_sync_dnodes+0x6c zfs`dmu_objset_sync+0x54 zfs`dsl_dataset_sync+0xc zfs`dsl_pool_sync+0x64 zfs`spa_sync+0x1...

Hi. System is snv_56 sun4u sparc SUNW,Sun-Fire-V440, zil_disable=1 We see many operation on nfs clients to that server really slow (like 90 seconds for unlink()). It''s not a problem with network, there''s also plenty oc CPU available. Storage isn''t saturated either. First strange thing - normally on that server nfsd has about 1500-2500 number of threads. I did

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

...ffffff008f235730, 200, ffffff008fbeaa80, 0, 0) metaslab_alloc+0x82(ffffff008f2d1a80, ffffff008f235730, 200, ffffff008fbeaa80, 2 , 3fd0f1) zio_dva_allocate+0x68(ffffff008f722790) zio_next_stage+0xb3(ffffff008f722790) zio_checksum_generate+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, ffffff...

...7a61a80 zfs:metaslab_alloc_dva+170 (82a7b900, 86057bc0,) 87a61af0 zfs:metaslab_alloc+80 (82a7b900, 86057bc0,) 87a61b40 zfs:zio_dva_allocate+6b (88e56dc0) 87a61b58 zfs:zio_next_stage+aa (88e56dc0) 87a61b70 zfs:zio_checksum_generate+5e (88e56dc0) 87a61b84 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, 88...

...zfs`space_map_add+0x12c zfs`space_map_load+0x214 zfs`metaslab_activate+0x3c zfs`metaslab_group_alloc+0x1b0 zfs`metaslab_alloc_dva+0x10c zfs`metaslab_alloc+0x2c zfs`zio_dva_allocate+0x50 zfs`zio_write_compress+0x1e4 zfs`arc_write+0xbc zfs`dbuf_sync+0x6b0 zfs`dnode_sync+0x300 zfs`dmu_objset_sync_dnodes+0x68 zfs`dmu_objset_sync+0x50 zfs`dsl_dataset_sync+0xc zfs`dsl_pool_sync+0x60 zfs`spa_sync+0xe...

...nix.0 vmcore.0 > $c vpanic() 0xfffffffffb9b49f3() space_map_remove+0x239() space_map_load+0x17d() metaslab_activate+0x6f() metaslab_group_alloc+0x187() metaslab_alloc_dva+0xab() metaslab_alloc+0x51() zio_dva_allocate+0x3f() zio_next_stage+0x72() zio_checksum_generate+0x5f() zio_next_stage+0x72() zio_write_compress+0x136() zio_next_stage+0x72() zio_wait_for_children+0x49() zio_wait_children_ready+0x15() zio_next_stage_async+0xae() zio_wait+0x2d() arc_write+0xcc() dmu_objset_sync+0x141() dsl_dataset_sync+0x23() dsl_pool_sync+0x7b() spa_sync+0x116() txg_sync_thread+0x115() thread_start+8() It appears ZFS is st...

...next_stage+b3 () Sep 13 14:13:22 cypress genunix: [ID 655072 kern.notice] ffffff000840d4c0 zfs:zio_checksum_generate+6e () Sep 13 14:13:22 cypress genunix: [ID 655072 kern.notice] ffffff000840d4e0 zfs:zio_next_stage+b3 () Sep 13 14:13:22 cypress genunix: [ID 655072 kern.notice] ffffff000840d550 zfs:zio_write_compress+239 () Sep 13 14:13:22 cypress genunix: [ID 655072 kern.notice] ffffff000840d570 zfs:zio_next_stage+b3 () Sep 13 14:13:22 cypress genunix: [ID 655072 kern.notice] ffffff000840d5c0 zfs:zio_wait_for_children+5d () Sep 13 14:13:22 cypress genunix: [ID 655072 kern.notice] ffffff000840d5e0 zfs:zio_wait_...

We are using MySQL, and love the idea of using zfs for this. We are used to using Direct I/O to bypass file system caching (let the DB do this). Does this exist for zfs? This message posted from opensolaris.org

..., f8def9d0,) d2c8a994 zfs:zio_nowait+e (e120e0c0) d2c8a9f4 zfs:zio_write_allocate_gang_members+341 (e3c0a580) d2c8aa10 zfs:zio_dva_allocate+81 (e3c0a580) d2c8aa28 zfs:zio_next_stage+66 (e3c0a580) d2c8aa40 zfs:zio_checksum_generate+5e (e3c0a580) d2c8aa54 zfs:zio_next_stage+66 (e3c0a580) d2c8aaa0 zfs:zio_write_compress+236 (e3c0a580) d2c8aabc zfs:zio_next_stage+66 (e3c0a580) d2c8aadc zfs:zio_wait_for_children+46 (e3c0a580, 1, e3c0a7) d2c8aaf0 zfs:zio_wait_children_ready+18 (e3c0a580) d2c8ab04 zfs:zio_next_stage_async+ac (e3c0a580, 0, f8dbfe) d2c8ab1c zfs:zio_nowait+e (e3c0a580) d2c8ab3c zfs:arc_write+7b (e44c9780...

Hi Folks, I''ve got a 3.9 Tb zpool, and it is casing kernel panics on my Solaris 10 280r (SPARC) server. The message I get on panic is this: panic[cpu1]/thread=2a100a95cc0: zfs: freeing free segment (offset=423713792 size=1024) This seems to come about when the zpool is being used or being scrubbed - about twice a day at the moment. After the reboot, the scrub seems to have

..._alloc+d1 () ffffff000fd0a2c0 zfs:metaslab_alloc_dva+1b7 () ffffff000fd0a360 zfs:metaslab_alloc+82 () ffffff000fd0a3b0 zfs:zio_dva_allocate+8a () ffffff000fd0a3d0 zfs:zio_next_stage+b3 () ffffff000fd0a400 zfs:zio_checksum_generate+6e () 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:...