On Fri, Jun 11, 2004 at 08:35:19AM -0400, Eric Sproul wrote: > Hi, ... > > "Aha!" I say. Something's happening to tar and it's not completing the > estimate. Running the tar command from a shell produces a segfault due > to a "permission denied" error on one of the directories below /usr: > > backup@<HOST>:/usr$ /bin/tar --create --file /dev/null \ > --directory /usr \ > --one-file-system --listed-incremental \ > /var/lib/amanda/gnutar-lists/<HOST>md0_1.new --sparse \ > --ignore-failed-read --totals \ > --exclude-from /tmp/amanda/sendsize.md0.20040609041435000.exclude . > /bin/tar: ./local/yoda: Cannot savedir: Permission denied > Segmentation fault > > > Now that's weird. Shouldn't tar ignore such a permissions error, or at > least just warn on it and continue? I have an identical host using the > same version of tar (GNU 1.13.25) with the same directory structure and > permissions. It has no trouble with the estimate and AMANDA does not > indicate any strangeness with backing up that DLE. Additionally, it has > been working for over a year on <HOST> and just started failing > yesterday. The directory entry itself has not been modified in almost a > year. I cannot think of what else could cause such a change in tar's > behavior. > > Anyone have any ideas for further investigation?
Well, I feel it shouldn't segfault under any conditions. Just two considerations, is "/bin/tar" the one amanda uses? And I'm pretty sure that when run by amanda, tar is setuid root. It does most things as the amanda-user, then invokes tar with a setuid program called "runtar". You might check that perms on runtar are unchanged. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
