Re: Image Catalog over NFS

Hello Diego,

Am 16.12.2020 um 16:25 schrieb Diego E. KESSELMAN <diegokesselman@xxxxxxxxx>:

Read this document:

Thanks a lot, this clarified things. The missing link for me was that the virtual device has to be created with a remote specification. The „intelligence“ is there within.

I wonder if one can save time and unnecessary network traffic by not writing a file full of zeros, but create a sparse file. Instead of

dd if=/dev/zero of=IMAGE01.ISO bs=1M count=10000

do a

dd if=/dev/zero of=IMAGE01.ISO bs=1M seek=10000 count=0

See https://en.wikipedia.org/wiki/Sparse_file for details.

I did not test if IBM i can cope with sparse files, but I don’t see any reason why it shouldn’t.

For me, I stick to the already established ftp workflow. The backup server uses jumbo frames, while the E4A isn’t configured for them. So, UDP (NFS) answer packets will be lost in transit and NFS doesn’t work. Mount and un mount work, though. I did not try if NFS can be forced over TCP in IBM i.

:wq! PoC