we have tried with more recent client/server but at the end the problem was connected to wrong ACL to the directory where iso images where placed so that the loop device could not work properly.

Giovanni

On 13/07/17 15:02, Giovanni Bracco wrote:
On 13/07/17 13:42, Stephan Wiesand wrote:

On 13. Jul 2017, at 12:54, Giovanni Bracco <[email protected]> wrote:

The error is related to accessing archive files that are contained in image ISO files that are physically located in AFS.

The typical and repeated error is:
   Errors extracting '/mnt/iso2/common/LINX64.GZ'
'"/opt/ansys_inc/extract.sh"' terminated after 1 attempts with the following error(s):
       Unknown error
   Exit Code: 2
      tar: This does not look like a tar archive

The ISO is mounted locally to the server with
mount -o loop -t iso9660 file_in_afs.iso /mnt/iso2

When the iso file is moved on the server local file-system the error disappears.

The client:
AFS version:  OpenAFS 1.6.7 built  2014-04-05
CentOS 6.7 kernel 2.6.32-358.23.2.el6.x86_64

Any suggestion?

Obviously, try a recent client - 1.6.7 is rather ancient.
OK, I agree that we should upgrade our client/server but for the moment I was curious if other have experienced the same problem.


And what's the fileserver version?
1.6.5


What are the sizes of the image and the client cache (and which cache type are you using)?

# cat /usr/vice/etc/cacheinfo
/afs:/afscache:400000

/dev/ram0               495844    271833    198411  58% /afscache

the iso size was 3.5 GB

In  other similar cases we had not problem in the past.
We have also tried on different clients (which exact the same configuration but with the same kind of errors)

Giovanni


--
Giovanni Bracco
DTE-ICT-HPC
ENEA
Via E. Fermi 45
I-00044 Frascati (Roma) Italy
phone +39-06-9400-5597  mobile +39-3351992144
FAX   +39-06-9400-5735
E-mail  [email protected]
WWW http://www.afs.enea.it/bracco
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info

Reply via email to