Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Feb 2019 10:10:45 +0000
From:      bugzilla-noreply@freebsd.org
To:        fs@FreeBSD.org
Subject:   [Bug 229694] [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data
Message-ID:  <bug-229694-3630-dVU0NWl67j@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-229694-3630@https.bugs.freebsd.org/bugzilla/>
References:  <bug-229694-3630@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229694

--- Comment #5 from Andriy Gapon <avg@FreeBSD.org> ---
(In reply to Eugene Grosbein from comment #3)
    5 101937 zfskern             txg_thread_enter    mi_switch+0xc5
sleepq_wait+0x2c _cv_wait+0x160 zio_resume_wait+0x4b spa_sync+0xd46
txg_sync_thread+0x25e fork_exit+0x75 fork_trampoline+0xe=20

 3249 101681 zpool               -                   mi_switch+0xc5
sleepq_wait+0x2c _cv_wait+0x160 txg_wait_synced+0xa5 dsl_sync_task_common+0=
x219
dsl_sync_task+0x14 dsl_scan+0x9e zfs_ioc_pool_scan+0x5a zfsdev_ioctl+0x6c2
devfs_ioctl_f+0x12d kern_ioctl+0x212 sys_ioctl+0x15c amd64_syscall+0x25c
fast_syscall_common+0x101

So, unfortunately, this is how ZFS works now.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229694-3630-dVU0NWl67j>