Rob N 4fe9cc5437 man: note that zdb operates directly on pool storage ... A frequent misunderstanding is that zdb accesses the pool through the kernel or filesystem, leading to confusion particularly when it can't access something that it seems like it should be able to. I've seen this confusion recently when zdb couldn't access a pool because the user didn't have permission to read directly from the block devices, and when it couldn't show attributes of encrypted files even though the dataset was unlocked. The manpage already speaks to another symptom of this, namely that zdb may "behave erratically" on an active pool; here I'm trying to make that a little more explicit. Reviewed-by: Richard Yao <richard.yao@alumni.stonybrook.edu> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Rob Norris <robn@despairlabs.com> Closes #14539		2023-02-28 17:35:33 -08:00
..
man1	Update arc_summary and arcstat outputs	2023-01-05 09:29:13 -08:00
man4	Increase default zfs_rebuild_vdev_limit to 64MB	2023-01-27 10:02:24 -08:00
man5	Consistentify miscellaneous style on remaining manpages	2021-06-09 14:35:53 -07:00
man7	Configure zed's diagnosis engine with vdev properties	2023-01-23 13:14:25 -08:00
man8	man: note that zdb operates directly on pool storage	2023-02-28 17:35:33 -08:00
Makefile.am	Add vdevprops.7 to the Makefile	2023-02-27 16:38:09 -08:00