search for: zfs_ioc_objset_stat

...a large zfs send | zfs receive when I decided that I wanted to terminate the the zfs send process. I killed it, but the zfs receive doesn''t want to die... In the meantime my zfs list command just hangs. Here is the tail end of the truss output from a "truss zfs list": ioctl(3, ZFS_IOC_OBJSET_STATS, 0x08043484) = 0 ioctl(3, ZFS_IOC_SNAPSHOT_LIST_NEXT, 0x08045788) Err#3 ESRCH ioctl(3, ZFS_IOC_DATASET_LIST_NEXT, 0x08046950) = 0 ioctl(3, ZFS_IOC_OBJSET_STATS, 0x0804464C) = 0 ioctl(3, ZFS_IOC_DATASET_LIST_NEXT, 0x08045788) Err#3 ESRCH ioctl(3, ZFS_IOC_SNAPSHOT_LIST_NEXT, 0x08045788) =...

...RDONLY) = 6 6074: fstat64(6, 0x08047AB0) = 0 6074: sysconfig(_CONFIG_PAGESIZE) = 4096 6074: ioctl(1, TCGETA, 0x08047B74) Err#22 EINVAL 6074: brk(0x08140000) = 0 6074: ioctl(3, ZFS_IOC_OBJSET_STATS, 0x080456E0) = 0 6074: brk(0x08150000) = 0 6074: ioctl(3, ZFS_IOC_OBJSET_STATS, 0x080461E0) = 0 6074: ioctl(3, ZFS_IOC_OBJSET_STATS, 0x08043D20) = 0 6074: ioctl(3, ZFS_IOC_SEND, 0x08044D90) (sleeping...) -- Ian

...ots. It is an active server, and generally has several users writing to the disk at any one time. Below is a snippet of output from a "truss -d zfs list": ... 0.0283 open("/dev/zfs", O_RDWR) = 3 ... 1.7142 ioctl(3, ZFS_IOC_DATASET_LIST_NEXT, 0x08045D38) = 0 2.6371 ioctl(3, ZFS_IOC_OBJSET_STATS, 0x08043E98) = 0 2.7222 ioctl(3, ZFS_IOC_DATASET_LIST_NEXT, 0x08044D88) = 0 4.6572 ioctl(3, ZFS_IOC_OBJSET_STATS, 0x08042EE8) = 0 ... As you can see, it spends quite a bit of time waiting for the return of ioctl calls on /dev/zfs. Since the command has to make many of these calls, the cumulati...

...01eb8960 [ fffffe8001eb8960 _resume_from_idle+0xf8() ] swtch+0x110() turnstile_block+0x1fb() mutex_vector_enter+0x40f() spa_open_common+0x5f() spa_open+0xb() dsl_dir_open_spa+0x22e() dsl_dataset_open_spa+0x41() dsl_dataset_open+0x16() dmu_objset_open+0x49() zfs_ioc_objset_stats+0x3d() zfsdev_ioctl+0x13e() cdev_ioctl+0x1d() spec_ioctl+0x50() fop_ioctl+0x25() ioctl+0xac() sys_syscall32+0x101() I have asked customer to provide a core dump. Still waiting for it to arrive. I would like to know if it is a known bug. -- Amer Ather TSC-KERNEL...

...okup .000 3 -------- ------ ---- sys totals: 33.556 6081241 10260 usr time: 41.354 elapsed: 386.130 Looking at exactly which ioctls get called: 5991763 MNTIOC_GETMNTENT 6782 TCGETA 6892 ZFS_IOC_DATASET_LIST_NEXT 3466 ZFS_IOC_OBJSET_STATS 2 ZFS_IOC_POOL_CONFIGS 1 ZFS_IOC_SET_PROP 1 ZFS_IOC_SHARE 8 ZFS_IOC_SNAPSHOT_LIST_NEXT Is anyone else experiencing this, or does anyone have any ideas on how to solve it? Is this solved in more recently snv releases? (And are there changelogs posted somewhere?) Thanks! -Laen -- This...

Ok, so I''m planning on wiping my test pool that seems to have problems with non-spare disks being marked as spares, but I can''t destroy it: # zpool destroy -f zmir cannot iterate filesystems: I/O error Anyone know how I can nuke this for good? Jim This message posted from opensolaris.org

I''ve recently re-installed an X4500 running Nevada b109 and have been experiencing ZFS lock ups regularly (perhaps once every 2-3 days). The machine is a backup server and receives hourly ZFS snapshots from another thumper - as such, the amount of zfs activity tends to be reasonably high. After about 48 - 72 hours, the file system seems to lock up and I''m unable to do anything