Date: Sat, 05 Oct 2019 18:12:09 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 241083] zfs: zpool import seems to probe all snapshots Message-ID: <bug-241083-3630-OENojoii72@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241083-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-241083-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=3D241083 --- Comment #2 from Martin Birgmeier <d8zNeCFG@aon.at> --- The settings are ("hal.5" is the second pool): [0]# zpool get cachefile hal.5 NAME PROPERTY VALUE SOURCE hal.5 cachefile - default [0]#=20 But I guess since I usually have it exported when unused any traces of it a= re cleared from the cache, leading to a re-scan of all devices on the next imp= ort? [0]# sysctl vfs.zfs.vol.recursive vfs.zfs.vol.recursive: 0 [0]#=20 [0]# sysctl vfs.zfs.vol.mode vfs.zfs.vol.mode: 1 [0]#=20 I did not know about this setting at all. Where can I read about it? 3 won't work since I am exporting most of them as iSCSI block devices via ctld. Do = you think setting it to 2 would stop scanning them during zpool import? If it is "dev" as you say, and the import looks at all devs, this would not help I assume? Thanks for assisting with this. -- Martin --=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-241083-3630-OENojoii72>