white space in ZFS command line

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
2
down vote

favorite












I have found that white space seems to be significant in ZFS commands, but only apparently under some conditions.. For example, both of the following commands work:



root@grandidier:~# zfs list -t snap -r tank/srv 
NAME USED AVAIL REFER MOUNTPOINT
tank/srv@initial 4.22G - 2.45T -
tank/srv@2018-01-09 106G - 3.40T -
tank/srv@2018-01-14 50.0M - 3.27T -
tank/srv@2018-01-17 48.8M - 3.16T -
tank/srv@2018-01-19 56.9M - 3.09T -
tank/srv@2018-01-30 48.6M - 2.72T -
tank/srv@2018-02-12 104M - 2.49T -
root@grandidier:~# zfs list -t snap -r tank/srv 
NAME USED AVAIL REFER MOUNTPOINT
tank/srv@initial 4.22G - 2.45T -
tank/srv@2018-01-09 106G - 3.40T -
tank/srv@2018-01-14 50.0M - 3.27T -
tank/srv@2018-01-17 48.8M - 3.16T -
tank/srv@2018-01-19 56.9M - 3.09T -
tank/srv@2018-01-30 48.6M - 2.72T -
tank/srv@2018-02-12 104M - 2.49T -
root@grandidier:~#


(Note: added space between "...snap -r") However if I put the command in a pipe and use back tick substitution to get the result of the command, I get:



root@grandidier:~# export NEW=`zfs list -t snap -r tank/srv | tail -1 | awk 'print $1'`; echo $NEW
tank/srv@2018-02-12
root@grandidier:~# export NEW=`zfs list -t snap  -r tank/srv | tail -1 | awk 'print $1'`; echo $NEW
cannot open ' -r': invalid dataset name
cannot open 'tank/srv': operation not applicable to datasets of this type

root@grandidier:~#


I find this baffling and disconcerting. I think I can sidestep the issue by crafting my scripts without any extra white space but I'd really like to know why this is happening in the first place.



This is on

Ubuntu 16.04 LTS (up to date)

bash 4.3.48

ZFS 0.6.5.11-1ubuntu3



Edit: to answer the first three comments (and retain code formatting)



root@grandidier:~/bin# printf '%qn' "$IFS"
$' tn'


It seems that the $(...) syntax is also subject to this problem (see next comment.)



I'm not sure where something that looks like a space could come from but it seems that is the issue. I have copied this string to/from a Google doc and perhaps it did some sort of translation on the spaces. If I add the extra space in the google doc and copy/paste to an xterm, the error is reported. If I edit the command (on the command line) and delete/reenter the two spaces, the command works w/out error.



Clearly Google Docs is not a good programming editor. (I'm not really using it that way but rather to take notes and save copies of commands as I work my way through something. I probably should stick to something like vim for that.)






command-line bash zfs







share|improve this question



















  • 1




    What is the value of $IFS? You can run printf '%qn' "$IFS" to find out.
    – wjandrea
    Feb 13 at 18:22










  • Try using the newer command substitution syntax $() instead of backticks.
    – wjandrea
    Feb 13 at 18:22






  • 1




    That second space in the second example is probably not an actual space but an NBSP or similar Unicode space
    – muru
    Feb 13 at 22:36






  • 1




    Yep, Google Docs would be it. Any "rich text" editor would cause problems with code, such as converting -- to en-dashes, normal spaces to NBSP, normal quotes to pretty quotes, etc. Maybe use a monospace font or something.
    – muru
    Feb 14 at 2:15






  • 1




    Looks like it's been converted into a regular space in your question. If you want to find out what Unicode character it is, you can pipe the string into uniname, like echo "  " | uniname (this is an example with two regular spaces).
    – wjandrea
    Feb 14 at 19:49















up vote
2
down vote

favorite












I have found that white space seems to be significant in ZFS commands, but only apparently under some conditions.. For example, both of the following commands work:



root@grandidier:~# zfs list -t snap -r tank/srv 
NAME USED AVAIL REFER MOUNTPOINT
tank/srv@initial 4.22G - 2.45T -
tank/srv@2018-01-09 106G - 3.40T -
tank/srv@2018-01-14 50.0M - 3.27T -
tank/srv@2018-01-17 48.8M - 3.16T -
tank/srv@2018-01-19 56.9M - 3.09T -
tank/srv@2018-01-30 48.6M - 2.72T -
tank/srv@2018-02-12 104M - 2.49T -
root@grandidier:~# zfs list -t snap -r tank/srv 
NAME USED AVAIL REFER MOUNTPOINT
tank/srv@initial 4.22G - 2.45T -
tank/srv@2018-01-09 106G - 3.40T -
tank/srv@2018-01-14 50.0M - 3.27T -
tank/srv@2018-01-17 48.8M - 3.16T -
tank/srv@2018-01-19 56.9M - 3.09T -
tank/srv@2018-01-30 48.6M - 2.72T -
tank/srv@2018-02-12 104M - 2.49T -
root@grandidier:~#


(Note: added space between "...snap -r") However if I put the command in a pipe and use back tick substitution to get the result of the command, I get:



root@grandidier:~# export NEW=`zfs list -t snap -r tank/srv | tail -1 | awk 'print $1'`; echo $NEW
tank/srv@2018-02-12
root@grandidier:~# export NEW=`zfs list -t snap  -r tank/srv | tail -1 | awk 'print $1'`; echo $NEW
cannot open ' -r': invalid dataset name
cannot open 'tank/srv': operation not applicable to datasets of this type

root@grandidier:~#


I find this baffling and disconcerting. I think I can sidestep the issue by crafting my scripts without any extra white space but I'd really like to know why this is happening in the first place.



This is on

Ubuntu 16.04 LTS (up to date)

bash 4.3.48

ZFS 0.6.5.11-1ubuntu3



Edit: to answer the first three comments (and retain code formatting)



root@grandidier:~/bin# printf '%qn' "$IFS"
$' tn'


It seems that the $(...) syntax is also subject to this problem (see next comment.)



I'm not sure where something that looks like a space could come from but it seems that is the issue. I have copied this string to/from a Google doc and perhaps it did some sort of translation on the spaces. If I add the extra space in the google doc and copy/paste to an xterm, the error is reported. If I edit the command (on the command line) and delete/reenter the two spaces, the command works w/out error.



Clearly Google Docs is not a good programming editor. (I'm not really using it that way but rather to take notes and save copies of commands as I work my way through something. I probably should stick to something like vim for that.)






command-line bash zfs







share|improve this question



















  • 1




    What is the value of $IFS? You can run printf '%qn' "$IFS" to find out.
    – wjandrea
    Feb 13 at 18:22










  • Try using the newer command substitution syntax $() instead of backticks.
    – wjandrea
    Feb 13 at 18:22






  • 1




    That second space in the second example is probably not an actual space but an NBSP or similar Unicode space
    – muru
    Feb 13 at 22:36






  • 1




    Yep, Google Docs would be it. Any "rich text" editor would cause problems with code, such as converting -- to en-dashes, normal spaces to NBSP, normal quotes to pretty quotes, etc. Maybe use a monospace font or something.
    – muru
    Feb 14 at 2:15






  • 1




    Looks like it's been converted into a regular space in your question. If you want to find out what Unicode character it is, you can pipe the string into uniname, like echo "  " | uniname (this is an example with two regular spaces).
    – wjandrea
    Feb 14 at 19:49













up vote
2
down vote

favorite









up vote
2
down vote

favorite











I have found that white space seems to be significant in ZFS commands, but only apparently under some conditions.. For example, both of the following commands work:



root@grandidier:~# zfs list -t snap -r tank/srv 
NAME USED AVAIL REFER MOUNTPOINT
tank/srv@initial 4.22G - 2.45T -
tank/srv@2018-01-09 106G - 3.40T -
tank/srv@2018-01-14 50.0M - 3.27T -
tank/srv@2018-01-17 48.8M - 3.16T -
tank/srv@2018-01-19 56.9M - 3.09T -
tank/srv@2018-01-30 48.6M - 2.72T -
tank/srv@2018-02-12 104M - 2.49T -
root@grandidier:~# zfs list -t snap -r tank/srv 
NAME USED AVAIL REFER MOUNTPOINT
tank/srv@initial 4.22G - 2.45T -
tank/srv@2018-01-09 106G - 3.40T -
tank/srv@2018-01-14 50.0M - 3.27T -
tank/srv@2018-01-17 48.8M - 3.16T -
tank/srv@2018-01-19 56.9M - 3.09T -
tank/srv@2018-01-30 48.6M - 2.72T -
tank/srv@2018-02-12 104M - 2.49T -
root@grandidier:~#


(Note: added space between "...snap -r") However if I put the command in a pipe and use back tick substitution to get the result of the command, I get:



root@grandidier:~# export NEW=`zfs list -t snap -r tank/srv | tail -1 | awk 'print $1'`; echo $NEW
tank/srv@2018-02-12
root@grandidier:~# export NEW=`zfs list -t snap  -r tank/srv | tail -1 | awk 'print $1'`; echo $NEW
cannot open ' -r': invalid dataset name
cannot open 'tank/srv': operation not applicable to datasets of this type

root@grandidier:~#


I find this baffling and disconcerting. I think I can sidestep the issue by crafting my scripts without any extra white space but I'd really like to know why this is happening in the first place.



This is on

Ubuntu 16.04 LTS (up to date)

bash 4.3.48

ZFS 0.6.5.11-1ubuntu3



Edit: to answer the first three comments (and retain code formatting)



root@grandidier:~/bin# printf '%qn' "$IFS"
$' tn'


It seems that the $(...) syntax is also subject to this problem (see next comment.)



I'm not sure where something that looks like a space could come from but it seems that is the issue. I have copied this string to/from a Google doc and perhaps it did some sort of translation on the spaces. If I add the extra space in the google doc and copy/paste to an xterm, the error is reported. If I edit the command (on the command line) and delete/reenter the two spaces, the command works w/out error.



Clearly Google Docs is not a good programming editor. (I'm not really using it that way but rather to take notes and save copies of commands as I work my way through something. I probably should stick to something like vim for that.)






command-line bash zfs







share|improve this question















I have found that white space seems to be significant in ZFS commands, but only apparently under some conditions.. For example, both of the following commands work:



root@grandidier:~# zfs list -t snap -r tank/srv 
NAME USED AVAIL REFER MOUNTPOINT
tank/srv@initial 4.22G - 2.45T -
tank/srv@2018-01-09 106G - 3.40T -
tank/srv@2018-01-14 50.0M - 3.27T -
tank/srv@2018-01-17 48.8M - 3.16T -
tank/srv@2018-01-19 56.9M - 3.09T -
tank/srv@2018-01-30 48.6M - 2.72T -
tank/srv@2018-02-12 104M - 2.49T -
root@grandidier:~# zfs list -t snap -r tank/srv 
NAME USED AVAIL REFER MOUNTPOINT
tank/srv@initial 4.22G - 2.45T -
tank/srv@2018-01-09 106G - 3.40T -
tank/srv@2018-01-14 50.0M - 3.27T -
tank/srv@2018-01-17 48.8M - 3.16T -
tank/srv@2018-01-19 56.9M - 3.09T -
tank/srv@2018-01-30 48.6M - 2.72T -
tank/srv@2018-02-12 104M - 2.49T -
root@grandidier:~#


(Note: added space between "...snap -r") However if I put the command in a pipe and use back tick substitution to get the result of the command, I get:



root@grandidier:~# export NEW=`zfs list -t snap -r tank/srv | tail -1 | awk 'print $1'`; echo $NEW
tank/srv@2018-02-12
root@grandidier:~# export NEW=`zfs list -t snap  -r tank/srv | tail -1 | awk 'print $1'`; echo $NEW
cannot open ' -r': invalid dataset name
cannot open 'tank/srv': operation not applicable to datasets of this type

root@grandidier:~#


I find this baffling and disconcerting. I think I can sidestep the issue by crafting my scripts without any extra white space but I'd really like to know why this is happening in the first place.



This is on

Ubuntu 16.04 LTS (up to date)

bash 4.3.48

ZFS 0.6.5.11-1ubuntu3



Edit: to answer the first three comments (and retain code formatting)



root@grandidier:~/bin# printf '%qn' "$IFS"
$' tn'


It seems that the $(...) syntax is also subject to this problem (see next comment.)



I'm not sure where something that looks like a space could come from but it seems that is the issue. I have copied this string to/from a Google doc and perhaps it did some sort of translation on the spaces. If I add the extra space in the google doc and copy/paste to an xterm, the error is reported. If I edit the command (on the command line) and delete/reenter the two spaces, the command works w/out error.



Clearly Google Docs is not a good programming editor. (I'm not really using it that way but rather to take notes and save copies of commands as I work my way through something. I probably should stick to something like vim for that.)






command-line bash zfs




command-line bash zfs






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 14 at 2:07

























asked Feb 13 at 15:40









HankB

214




214







  • 1




    What is the value of $IFS? You can run printf '%qn' "$IFS" to find out.
    – wjandrea
    Feb 13 at 18:22










  • Try using the newer command substitution syntax $() instead of backticks.
    – wjandrea
    Feb 13 at 18:22






  • 1




    That second space in the second example is probably not an actual space but an NBSP or similar Unicode space
    – muru
    Feb 13 at 22:36






  • 1




    Yep, Google Docs would be it. Any "rich text" editor would cause problems with code, such as converting -- to en-dashes, normal spaces to NBSP, normal quotes to pretty quotes, etc. Maybe use a monospace font or something.
    – muru
    Feb 14 at 2:15






  • 1




    Looks like it's been converted into a regular space in your question. If you want to find out what Unicode character it is, you can pipe the string into uniname, like echo "  " | uniname (this is an example with two regular spaces).
    – wjandrea
    Feb 14 at 19:49













  • 1




    What is the value of $IFS? You can run printf '%qn' "$IFS" to find out.
    – wjandrea
    Feb 13 at 18:22










  • Try using the newer command substitution syntax $() instead of backticks.
    – wjandrea
    Feb 13 at 18:22






  • 1




    That second space in the second example is probably not an actual space but an NBSP or similar Unicode space
    – muru
    Feb 13 at 22:36






  • 1




    Yep, Google Docs would be it. Any "rich text" editor would cause problems with code, such as converting -- to en-dashes, normal spaces to NBSP, normal quotes to pretty quotes, etc. Maybe use a monospace font or something.
    – muru
    Feb 14 at 2:15






  • 1




    Looks like it's been converted into a regular space in your question. If you want to find out what Unicode character it is, you can pipe the string into uniname, like echo "  " | uniname (this is an example with two regular spaces).
    – wjandrea
    Feb 14 at 19:49








1




1




What is the value of $IFS? You can run printf '%qn' "$IFS" to find out.
– wjandrea
Feb 13 at 18:22




What is the value of $IFS? You can run printf '%qn' "$IFS" to find out.
– wjandrea
Feb 13 at 18:22












Try using the newer command substitution syntax $() instead of backticks.
– wjandrea
Feb 13 at 18:22




Try using the newer command substitution syntax $() instead of backticks.
– wjandrea
Feb 13 at 18:22




1




1




That second space in the second example is probably not an actual space but an NBSP or similar Unicode space
– muru
Feb 13 at 22:36




That second space in the second example is probably not an actual space but an NBSP or similar Unicode space
– muru
Feb 13 at 22:36




1




1




Yep, Google Docs would be it. Any "rich text" editor would cause problems with code, such as converting -- to en-dashes, normal spaces to NBSP, normal quotes to pretty quotes, etc. Maybe use a monospace font or something.
– muru
Feb 14 at 2:15




Yep, Google Docs would be it. Any "rich text" editor would cause problems with code, such as converting -- to en-dashes, normal spaces to NBSP, normal quotes to pretty quotes, etc. Maybe use a monospace font or something.
– muru
Feb 14 at 2:15




1




1




Looks like it's been converted into a regular space in your question. If you want to find out what Unicode character it is, you can pipe the string into uniname, like echo "  " | uniname (this is an example with two regular spaces).
– wjandrea
Feb 14 at 19:49





Looks like it's been converted into a regular space in your question. If you want to find out what Unicode character it is, you can pipe the string into uniname, like echo "  " | uniname (this is an example with two regular spaces).
– wjandrea
Feb 14 at 19:49
















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1005849%2fwhite-space-in-zfs-command-line%23new-answer', 'question_page');

);

Post as a guest






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1005849%2fwhite-space-in-zfs-command-line%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

pylint3 and pip3 broken

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have tried sudo apt remove --purge on various packages. I get the same when I reinstall. I have also tried reinstall using aptitude. This does not work. My current workaround is to run pylint3 as root, which works, but is bad practice. pip3 $ pip3 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 33, in vendored __import__(vendored_name, globals(), locals(), level=0) ImportError: No module named 'pip._vendor.pkg_resources' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/pip3", line 9, in <module> from pip import main File "/usr/lib/python3/dist-packages/pip/__init__.py", line 13, in <module> from pip.exceptions import InstallationError, CommandError, PipError File "/usr/lib/python3/dist-packages/pip/exceptions.py", line 6, ...
Read more

Missing snmpget and snmpwalk

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried to install it with: apt-get install net-snmp-utils but I have error message: Unable to locate package. I have also check what from SNMP is preinstalled and there is: libsnmp-base libsnmp30:amd64 snmp-mibs-downloader snmpd snmptrapd snmptrapfmt How can I install snmpget and snmpwalk ? snmp zabbix share | improve this question edited Jan 29 at 10:10 Yaron 8,552 7 18 38 asked Jan 29 at 9:51 Alfista 1 apt install snmp perhaps ? If named differently - apt cache snmp – fugitive Jan 29 at 10:00 add a comment  |  up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried...
Read more

How to enroll fingerprints to Ubuntu 17.10 with VFS491

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I decided to switch from Windows to Ubuntu 17.10, I meet it like 8 years ago and I didn't decided to switch until now (haha). Well, my actual device is an HP Probook 4540s with a Validity fingerprint sensor (VFS491). The fingerprint sensor worked fine on Windows but I can't get it to work in Ubuntu. The device is recognized as 138a:003d but is not detected as a fingerprint scanner by some apps like Fingerprint GUI. I want to use the fingerprint scanner to log in into my user account in Ubuntu but it doesn't supports fingerprints without special software and the drivers of the fingerprint scanner are available for Windows but not for any Linux distribution. I found something on GitHub (https://github.com/eekpie/libfprint) about the integration of the VFS491 in libfprint and I think it can help but I don't know what to do with it, so that's why I need the help of the community to do it since I am...
Read more