From: Brian Behlendorf <behlendorf1@llnl.gov>
Date: Mon, 7 Mar 2011 18:10:20 +0000 (-0800)
Subject: Print mount/umount errors
X-Git-Url: https://git.camperquake.de/gitweb.cgi?a=commitdiff_plain;h=9ac97c2a939aef0f9899244920007c605387949a;hp=9ac97c2a939aef0f9899244920007c605387949a;p=zfs.git

Print mount/umount errors

Because we are dependent of the system mount/umount utilities to
ensure correct mtab locking, we should not suppress their error
output.  During a successful mount/umount they will be silent,
but during a failure the error message they print is the only sure
way to know why a mount failed.  This is because the (u)mount(8)
return code does not contain the result of the system call issued.
The only way to clearly idenify why thing failed is to rely on
the error message printed by the tool.

Longer term once libmount is available we can issue the mount/umount
system calls within the tool and still be ensured correct mtab locking.

Closed #107
---