Obsolete Releases > SME 8.x Contribs
affa makes no hardlinks
Stefano:
Charlie, there's no evidence that Gary Douglas is storing his data on a mint nfs storage, AFAICT
in any case, he said:
--- Quote ---Using the same NFS storage server, when moving from AFFA ver2 on SME8 to AFFA ver3 on SME9, the archives began using the full GB per archive.
--- End quote ---
that means, IIUC, that affa3 changed its behaviour, giving unexpected results
janet:
Stefano
--- Quote ---Charlie, there's no evidence that Gary Douglas is storing his data on a mint nfs storage....
--- End quote ---
I would say that Charlie got confused with the OP adlaw, who was using Linux Mint
Gary Douglas:
Stefano, I filed a bug with the following detail, per your request, but it is not a bug.
This thread seemed to have gone unanswered, thought this may help others using AFFA to NFS storage.
I have completed my cutover today, final gotcha was excluding directories with spaces. Seems it requires a * instead of a space.
i.e; Exclude=/home/e-smith/files/users/rob/home/My*Documents/My*Music
-------------------------------------------------------------------------------------------
Bug 9186
Changing from SME8 AFFAv2 to SME9 AFFAv3 using the same NFS storage and taking over the AFFAv2 archives, caused all new archives to become the full archive size. i.e. hardlinks were not working.
I have run AFFAv2 on SME7/8 to NFS shared storage for many years without issues, originally from a SME7/8 server to FreeNAS. Since a few years ago my NFS Server is now a Proxmox/Debian with additional HP410/RAID5 storage shared using debian nfs-kernel-server. SME8/AFFAv2 and SME9/AFFAv3 are virtual on another proxmox box.
By default SME8 attaches to the NFS share using nfsvers=3 and hardlinks have never been a problem. SME9 by default connects to the same NFS share using nfsvers=4. The issue of hardlinks failing appears to be when using nfsvers=4. By setting SME9 to use nfsvers=3, hardlinks are maintained on the AFFA archives.
There is no bug with SME or AFFA (nor using NFS if configured correctly), bug only raised on request of Stefano.
janet:
Gary Douglas
I think this would have worked
Exclude="/home/e-smith/files/users/rob/home/My Documents/My Music"
(or with single inverted commas)
Exclude='/home/e-smith/files/users/rob/home/My Documents/My Music'
Stefano:
--- Quote from: Gary Douglas on January 14, 2016, 12:34:07 PM ---Stefano, I filed a bug with the following detail, per your request, but it is not a bug.
-------------------------------------------------------------------------------------------
Bug 9186
Changing from SME8 AFFAv2 to SME9 AFFAv3 using the same NFS storage and taking over the AFFAv2 archives, caused all new archives to become the full archive size. i.e. hardlinks were not working.
I have run AFFAv2 on SME7/8 to NFS shared storage for many years without issues, originally from a SME7/8 server to FreeNAS. Since a few years ago my NFS Server is now a Proxmox/Debian with additional HP410/RAID5 storage shared using debian nfs-kernel-server. SME8/AFFAv2 and SME9/AFFAv3 are virtual on another proxmox box.
By default SME8 attaches to the NFS share using nfsvers=3 and hardlinks have never been a problem. SME9 by default connects to the same NFS share using nfsvers=4. The issue of hardlinks failing appears to be when using nfsvers=4. By setting SME9 to use nfsvers=3, hardlinks are maintained on the AFFA archives.
There is no bug with SME or AFFA (nor using NFS if configured correctly), bug only raised on request of Stefano.
--- End quote ---
one of the main feature of Affa is the use of hardlinks.. maybe is not a "real" bug but just a documentation one
anyway, since the main rule here is "if something doesn't work as expected out of the box is likely a bug", a bug in bugzilla is needed
than you for your time
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version