Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve "Unable to automount" error message #8959

Merged
merged 1 commit into from
Jul 3, 2019

Conversation

PaulZ-98
Copy link
Contributor

@PaulZ-98 PaulZ-98 commented Jun 26, 2019

Having the mountpoint and dataset name both in the message made it
confusing to read.

Signed-off-by: Paul Zuchowski [email protected]

Motivation and Context

This message shows up frequently in our logs at Datto and we wanted to clean up the message a bit.

Description

Reformatted the error message to just include the mount point.

How Has This Been Tested?

Ran snapshot portion of zfstest. To see the message:

umount /tank/fs1/.zfs/snapshot/snap1 &
zfs destroy tank/fs1@snap1
cd /tank/fs1/.zfs/snapshot/snap1 &

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Performance enhancement (non-breaking change which improves efficiency)
  • Code cleanup (non-breaking change which makes code smaller or more readable)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation (a change to man pages or other documentation)

Checklist:

@PaulZ-98 PaulZ-98 force-pushed the automount-message branch from 84677e4 to ce38249 Compare June 26, 2019 15:13
@behlendorf behlendorf added the Status: Code Review Needed Ready for review and testing label Jun 27, 2019
Copy link
Contributor

@behlendorf behlendorf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we perhaps instead convert this to a zfs_dbgmsg()? Is there utility in continuing to log the failed mount to the console?

mountpoint and dataset name both in the message made it
confusing to read.

Signed-off-by: Paul Zuchowski <[email protected]>
@PaulZ-98 PaulZ-98 force-pushed the automount-message branch from ce38249 to b523978 Compare July 2, 2019 18:18
@PaulZ-98
Copy link
Contributor Author

PaulZ-98 commented Jul 2, 2019

Converted it to a zfs_dbgmsg.

@behlendorf behlendorf requested a review from tcaputi July 2, 2019 18:56
Copy link
Contributor

@tcaputi tcaputi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, other than the style issue.

@behlendorf behlendorf added Status: Accepted Ready to integrate (reviewed, tested) and removed Status: Code Review Needed Ready for review and testing labels Jul 3, 2019
@codecov
Copy link

codecov bot commented Jul 3, 2019

Codecov Report

Merging #8959 into master will decrease coverage by 0.15%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #8959      +/-   ##
==========================================
- Coverage   78.66%   78.51%   -0.16%     
==========================================
  Files         388      388              
  Lines      119958   119899      -59     
==========================================
- Hits        94369    94137     -232     
- Misses      25589    25762     +173
Flag Coverage Δ
#kernel 79.39% <100%> (+0.02%) ⬆️
#user 66% <ø> (-0.65%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update df358db...b523978. Read the comment docs.

@behlendorf behlendorf merged commit 6dbca94 into openzfs:master Jul 3, 2019
TulsiJain pushed a commit to TulsiJain/zfs that referenced this pull request Jul 20, 2019
Having the mountpoint and dataset name both in the message made it
confusing to read.  Additionally, convert this to a zfs_dbgmsg rather than
sending it to the console.

Reviewed-by: Tom Caputi <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Paul Zuchowski <[email protected]>
Closes openzfs#8959
TulsiJain pushed a commit to TulsiJain/zfs that referenced this pull request Jul 20, 2019
Having the mountpoint and dataset name both in the message made it
confusing to read.  Additionally, convert this to a zfs_dbgmsg rather than
sending it to the console.

Reviewed-by: Tom Caputi <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Paul Zuchowski <[email protected]>
Closes openzfs#8959
tonyhutter pushed a commit to tonyhutter/zfs that referenced this pull request Aug 13, 2019
Having the mountpoint and dataset name both in the message made it
confusing to read.  Additionally, convert this to a zfs_dbgmsg rather than
sending it to the console.

Reviewed-by: Tom Caputi <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Paul Zuchowski <[email protected]>
Closes openzfs#8959
tonyhutter pushed a commit to tonyhutter/zfs that referenced this pull request Aug 22, 2019
Having the mountpoint and dataset name both in the message made it
confusing to read.  Additionally, convert this to a zfs_dbgmsg rather than
sending it to the console.

Reviewed-by: Tom Caputi <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Paul Zuchowski <[email protected]>
Closes openzfs#8959
tonyhutter pushed a commit to tonyhutter/zfs that referenced this pull request Aug 23, 2019
Having the mountpoint and dataset name both in the message made it
confusing to read.  Additionally, convert this to a zfs_dbgmsg rather than
sending it to the console.

Reviewed-by: Tom Caputi <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Paul Zuchowski <[email protected]>
Closes openzfs#8959
tonyhutter pushed a commit to tonyhutter/zfs that referenced this pull request Sep 17, 2019
Having the mountpoint and dataset name both in the message made it
confusing to read.  Additionally, convert this to a zfs_dbgmsg rather than
sending it to the console.

Reviewed-by: Tom Caputi <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Paul Zuchowski <[email protected]>
Closes openzfs#8959
tonyhutter pushed a commit to tonyhutter/zfs that referenced this pull request Sep 18, 2019
Having the mountpoint and dataset name both in the message made it
confusing to read.  Additionally, convert this to a zfs_dbgmsg rather than
sending it to the console.

Reviewed-by: Tom Caputi <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Paul Zuchowski <[email protected]>
Closes openzfs#8959
tonyhutter pushed a commit that referenced this pull request Sep 26, 2019
Having the mountpoint and dataset name both in the message made it
confusing to read.  Additionally, convert this to a zfs_dbgmsg rather than
sending it to the console.

Reviewed-by: Tom Caputi <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Paul Zuchowski <[email protected]>
Closes #8959
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Accepted Ready to integrate (reviewed, tested)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants