Bug #7857
zfs/zpool commands print scary errors after 7741
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
2017-02-13
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:
Description
After 7741 get_zfs_dataset() tries to guess the name of the dataset that the given path resides on. When it gets this wrong errors are printed to sterr which can be misleading.
cannot open 'storage/pool0/test': dataset does not exist
Related issues
Updated by Andrew Stormont almost 4 years ago
- Related to Bug #7741: get_zfs_dataset() takes an unreasonable amount of time added
Updated by Electric Monk almost 4 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
git commit ff524b2355c0ac08bf963297ae8e5ea2e8375852
commit ff524b2355c0ac08bf963297ae8e5ea2e8375852
Author: Andrew Stormont <astormont@racktopsystems.com>
Date: 2017-02-19T17:56:04.000Z
7857 zfs/zpool commands print scary errors after 7741
7887 get_zfs_dataset() optimised path leaks zfs handle
Reviewed by: Sam Zaydel <szaydel@racktopsystems.com>
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Approved by: Richard Lowe <richlowe@richlowe.net>
Updated by Marcel Telka over 3 years ago
- Related to Bug #7890: degradation afte 7741: 'zfs set sharesmb=name=test,guestok=true rpool/test' produce message with 'cannot open 'var/smb/cvol': dataset does not exist' added