| GNU tar won't configure on the Samba share: | ||
|---|---|---|
 | Compile grade Samba settings |  |
| GNU tar won't configure on the Samba share: | ||
|---|---|---|
| | Compile grade Samba settings | |
user@client:~$ wget http://ftp.gnu.org/gnu/tar/tar-1.23.tar.gz
user@client:~$ tar zxpf tar-1.23.tar.gz
user@client:~$ cd tar-1.23.tar.gz
user@client:~$ ./configure --prefix /home/p217811/tartest
<snip>
checking whether __fpending is declared... yes
checking for fseeko... yes
checking whether getcwd handles long file names properly...
at that point, configure stops.
Backgrounding or interrupting the process doesn't work, but after several hours, we can background the process, and kill it with SIGKILL (only).
We restart the client, just to make sure the process that created the problem isn't a factor any more.
Then we probe the deep directory structure that has been created:
user@client:~$ cd tar-1.23
user@client:~/tar-1.23$ DEEP=.
user@client:~/tar-1.23$ while test -d "${DEEP}/confdir3" ; do DEEP="${DEEP}/confdir3" ; echo . ; done
......................................................................................................................................................................................................................................................................................................................................................................................................................................................................user@client:~/tar-1.23
p217811@cit-zb-39-116:~/tar-1.23$ ls -l ${DEEP}
total 0
p217811@cit-zb-39-116:~/tar-1.23$ ls -l ${DEEP}/..
ls: cannot access ./confdir3/confdir3/<snip a lot of confdir3s>/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/../confdir3: File name too long
total 0
d????????? ? ? ? ? ? confdir3
user@client:~/tar-1.23$ rmdir ${DEEP}
user@client:~/tar-1.23$ rm -rf confdir3
user@client:~/tar-1.23$
... we can then remove the parent tar-1.23 directory as well, but not unpack the tar bundle unless we restart the client PC.
From docs and experiments, we are not hitting a path length or directory nesting depth limit on XFS: from a shell script on the server, we can easily create directory structures with longer path lengths and deeper nesting.
But we do run into a nearby limit in bash: path lengths of 4096 characters give file name too long errors, even in bash on the server.
This problem is a known bug (can't find the bug report right now), and goes away if we upgrade to a newer version, as we shall see in the next section.
| |  | |
| The original settings of the Samba daemon |  | Installing a test client |