Bug 169317 - zfs umount refers to umount(1M) but should to umount(8)
Summary: zfs umount refers to umount(1M) but should to umount(8)
Status: Closed FIXED
Alias: None
Product: Documentation
Classification: Unclassified
Component: Books & Articles (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-doc (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-22 08:10 UTC by Slawomir Wojciech Wojtczak
Modified: 2017-03-10 01:58 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Slawomir Wojciech Wojtczak 2012-06-22 08:10:01 UTC 
Hi,

when trying to umount pool/some/dataset and zfs(8)
fails because pool/some/dataset/inside is also
mounted, then it fails with error message that
refers to umount(1M) instead of umount(8).

  # zfs umount pool/some/dataset
  cannot unmount 'pool/some/dataset': legacy mountpoint
  use umount(1M) to unmount this filesystem

There are actually LOTS of such references, just type:

  # grep -r -E " [a-z]+\(1M\) " /usr/src

Regards,
vermaden

Fix: 

1. Find all 'foreign' references with:
   # grep -r -E " [a-z]+\(1M\) " /usr/src

2. Update/change them to our local ones, for example:
   umount(1M) --> umount(8)
How-To-Repeat: # zfs umount pool/some/dataset
cannot unmount 'pool/some/dataset': legacy mountpoint
use umount(1M) to unmount this filesystem

# grep -r -E " [a-z]+\(1M\) " /usr/src
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2012-06-25 09:22:08 UTC 
Responsible Changed
From-To: freebsd-amd64->freebsd-doc

reclassify
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2012-07-01 16:48:48 UTC 
Responsible Changed
From-To: freebsd-doc->eadler

I'll take it.
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2012-09-02 17:52:53 UTC 
Responsible Changed
From-To: eadler->freebsd-doc

I won't be looking at this PR for a while and I need to clear some out 
of my queue
Comment 4 Benedict Reuschling freebsd_committer freebsd_triage 2017-03-10 01:58:29 UTC 
The issue has been fixed, the message now refers to umount(8). PR closed.