search for: metaslab_group_alloc

...egvn_fault+0x438 genunix`as_fault+0x4c8 unix`pagefault+0x68 unix`trap+0xd4c unix`utl0+0x4c 71 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_objse...

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

...Stack Backtrace ----------------- vpanic() assfail3+0xb9(fffffffff7dde5f0, 6, fffffffff7dde840, 0, fffffffff7dde820, 153) space_map_load+0x2ef(ffffff008f1290b8, ffffffffc00fc5b0, 1, ffffff008f128d88, ffffff008dd58ab0) metaslab_activate+0x66(ffffff008f128d80, 8000000000000000) metaslab_group_alloc+0x24e(ffffff008f46bcc0, 400, 3fd0f1, 32dc18000, ffffff008fbeaa80, 0) metaslab_alloc_dva+0x192(ffffff008f2d1a80, ffffff008f235730, 200, ffffff008fbeaa80, 0, 0) metaslab_alloc+0x82(ffffff008f2d1a80, ffffff008f235730, 200, ffffff008fbeaa80, 2 , 3fd0f1) zio_dva_allocate+0x68(ffffff008f722790) zio_next_...

...unix:assfail3+b9 () May 22 02:18:57 ultra20 genunix: [ID 655072 kern.notice] ffffff0003d068e0 zfs:space_map_load+2c2 () May 22 02:18:57 ultra20 genunix: [ID 655072 kern.notice] ffffff0003d06920 zfs:metaslab_activate+66 () May 22 02:18:57 ultra20 genunix: [ID 655072 kern.notice] ffffff0003d069e0 zfs:metaslab_group_alloc+24e () May 22 02:18:57 ultra20 genunix: [ID 655072 kern.notice] ffffff0003d06ab0 zfs:metaslab_alloc_dva+1da () May 22 02:18:57 ultra20 genunix: [ID 655072 kern.notice] ffffff0003d06b50 zfs:metaslab_alloc+82 () May 22 02:18:57 ultra20 genunix: [ID 655072 kern.notice] ffffff0003d06ba0 zfs:zio_dva_all...

...7808 size=66560) 87a6185c genunix:vcmn_err+16 (3, f4571654, 87a618) 87a61874 zfs:zfs_panic_recover+28 (f4571654, 2842f400,) 87a618e4 zfs:space_map_add+13f (8cbc1e78, 2842f400,) 87a6196c zfs:space_map_load+27a (8cbc1e78, 8613b5b0,) 87a6199c zfs:metaslab_activate+44 (8cbc1c40, 0, 800000) 87a619f4 zfs:metaslab_group_alloc+22a (8c8e4d80, 400, 0, 2) 87a61a80 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...

...9;{@[stack()]=count();}'' dtrace: description ''fbt::space_map_seg_compare:entry'' matched 1 probe ^C genunix`avl_find+0x38 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_objse...

...ter panic: assertion failed: ss != NULL, file: ../../common/fs/zfs/space_map.c, line: 125 The server saved a core file, and the resulting backtrace is listed below: $ mdb unix.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+...

...pu0]/thread=ffffff0004469c80: assertion failed: sm->sm_space == space (0x20000000 == 0x1ff8a000), file: ../../common/fs/zfs/space_map.c, line: 359 ffffff00044697f0 genunix:assfail3+b9 () ffffff00044698a0 zfs:space_map_load+3a6 () ffffff00044698f0 zfs:metaslab_activate+93 () ffffff00044699b0 zfs:metaslab_group_alloc+24e () ffffff0004469a70 zfs:metaslab_alloc_dva+200 () ffffff0004469b30 zfs:metaslab_alloc+156 () ffffff0004469b90 zfs:zio_dva_allocate+10d () ffffff0004469bd0 zfs:zio_execute+bb () ffffff0004469c60 genunix:taskq_thread+1cb () ffffff0004469c70 unix:thread_start+8 () panic: entering debugger (contin...

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

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

...b_err_msi_intr+d2 () ffffff000f7c2c20 unix:av_dispatch_autovect+78 () ffffff000f7c2c60 unix:dispatch_hardint+2f () ffffff000fd09fd0 unix:switch_sp_and_call+13 () ffffff000fd0a020 unix:do_interrupt+a0 () ffffff000fd0a030 unix:cmnint+ba () ffffff000fd0a130 genunix:avl_first+1e () ffffff000fd0a1f0 zfs:metaslab_group_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_wr...