> Anyone else have these kinds of adventures with lin_tape?
Yes, but not recently... Had the problem with /dev/IBMtapexx permissions, and one version (above 3.0.0) refused to rpmbuild, so I used one step older... Luckily nothing more serious than that :-) Regards, -- Sasa Drnjevic www.srce.unizg.h On 2017-03-23 19:05, Zoltan Forray wrote: > Just spent the better part of 4-hours trying to patch my 6-RHEL 6 servers > with issues caused by the latest kernel (we are required to patch to the > latest, every month) and the latest lin_tape driver. > > RHEL 6 KERNEL=2.6.32-696.el6.x86_64 - lin_tape 3.0.16 would not rpmbuild > successfully. Fails with: > > *make: *** [bldtmp/lin_tape-2.6.32-696.el6.x86_64.ko] Error 2* > *error: Bad exit status from /var/tmp/rpm-tmp.PGuVC0 (%build)* > > *RPM build errors:* > * Bad exit status from /var/tmp/rpm-tmp.PGuVC0 (%build)* > > So, went out looking and found lin_tape 3.0.18. No mention of kernel > compatibility updates (as previous levels have said) and the 2-changes in > the readme didn't sound like anything I needed/wanted and was > engineering-speak, anyway. > > While lin_tape 3.0.18 rpmbuild's clean/no errors it introduces a new > problem/error. > > ANR1819E Permission denial to device /dev/IBMchanger6. > > After finding docs on the permissions error that said to chmod r+aw to the > /dev entry (which got rid of the "permissions" problem - never had to do > that before), still got all kinds of errors and TSM server "internal > failures" and it telling me the library needed auditing, etc. > > So we have backed off both the kernel level and lin_tape driver level! > > Anyone else have these kinds of adventures with lin_tape? > > > > -- > *Zoltan Forray* > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator > Xymon Monitor Administrator > VMware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > www.ucc.vcu.edu > zfor...@vcu.edu - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://infosecurity.vcu.edu/phishing.html >