search for: dmu_buf_hold_array

...get the below: # dtrace -n profile-997''{@[stack()]=count();}'' [...] unix`default_lock_delay+0x48 unix`mutex_vector_enter+0x99 zfs`dmu_zfetch_find+0x1f9 zfs`dmu_zfetch+0xc9 zfs`dbuf_read+0x27a zfs`dmu_buf_hold_array_by_dnode+0x287 zfs`dmu_buf_hold_array+0x81 zfs`dmu_read_uio+0x49 zfs`zfs_read+0x15e zfs`zfs_shim_read+0xc genunix`fop_read+0x31 genunix`read+0x188 unix`sys_syscall+0x17b 1861...

...nt errors have been detected: DATASET OBJECT RANGE mos 15 0-524288 I am trying to backup the pool, but when I tar some of the filesystems, the kernel panics with the following message: Apr 3 16:37:56 columbia genunix: [ID 403854 kern.notice] assertion failed: 0 == dmu_buf_hold_array(os, object, offset, size, FALSE, FTAG, &numbufs, &dbp), file: ../../common/fs/zfs/dmu.c, line: 386 Apr 3 16:37:56 columbia unix: [ID 100000 kern.notice] Apr 3 16:37:56 columbia genunix: [ID 353471 kern.notice] d4042ba0 genunix:assfail+5c (f975dfac, f975df90,) Apr 3 16:37:56 columbia gen...

I have just recently (physically) moved a system with 16 hard drives (for the array) and 1 OS drive; and in doing so, I needed to pull out the 16 drives so that it would be light enough for me to lift. When I plugged the drives back in, initially, it went into a panic-reboot loop. After doing some digging, I deleted the file /etc/zfs/zpool.cache. When I try to import the pool using the zpool

...in /etc/system and restarted again and then proceeded with: Any attempt to import my pool "tank", including: zpool import -fFX tank zpool import -fFX -o readonly=on tank causes the same kernel panic message: ----- PANIC ---- panic[cpu2]/thread=ffffff00f8578c40: assertion failed: 0 == dmu_buf_hold_array(os, object, offset, size, FALSE, FTAG, &numbufs, &dbp), file: ../../common/fs/zfs/dmu.c, line: 796 ffffff00f8578880 genunix:assfail+7e () ffffff00f8578930 zfs:dmu_write+17f () ffffff00f85789e0 zfs:space_map_sync+295 () ffffff00f8578a70 zfs:metaslab_sync+2de () ffffff00f8578ad0 zfs:vdev_...

Hi list, since we activated 10gbe on ixgbe cards + jumbo frames(9k) on 9.0 and now on 9.1 we recognize that after a random period of time, sometimes a week, sometimes only a day, the system doesn't send any packets out. The phenomenon is that you can't login via ssh, nfs and istgt is not operative. Yet you can login on the console and execute commands. A clean shutdown isn't possible

Hello everybody, just to let you know what happened in the meantime: I was able to open a Service Request at Oracle. The issue is a known bug (Bug 6742788 : assertion panic at: zfs:zap_deref_leaf) The bug has bin fixed (according to Oracle support) since build 164, but there is no fix for Solaris 11 available so far (will be fixed in S11U7?). There is a workaround available that works