Bug 233799 - fwbackups: errantly follows symbolic links until all system resources are consumed
fwbackups: errantly follows symbolic links until all system resources are con...
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: fwbackups (Show other bugs)
6
All Linux
medium Severity high
: ---
: ---
Assigned To: Stewart Adam
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-25 01:22 EDT by Bernard Johnson
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-03-28 17:09:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bernard Johnson 2007-03-25 01:22:23 EDT
Description of problem:
It seems that fwbackups errantly follows symbolic links recursively until all
system resources are consumed.

I started a fwbackups job and let it run.  It ran for about 14 hours and when I
returned home, it had consumed enormous space on the destination, all available
memory (2G), and was still churning away.  I did a strace on the process and
found this:

open("/net/terastation/mnt/array1/backup/server/Backups/Backup-2007-03-24/home/bjohnson/.wine/dosdevices/c:/windows/profiles/bjohnson/My
Music/.wine/dosdevices/c:/windows/profiles/bjohnson/My
Music/.wine/dosdevices/c:/windows/profiles/bjohnson/My
Music/svn/LinuxTools/linux/kernel2-6-15/include/config/arch/.svn/text-base/shark.h.svn-base",
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0666

It seems that there is a symbolic link in
~/.wine/dosdevices/c:/windows/profiles/bjohnson/My Music that points back to ~.
 fwbackups seems to be recursively following this.  This is one of many links.

Version-Release number of selected component (if applicable):
fwbackups-1.42.3a-1.fc6
Comment 1 Stewart Adam 2007-03-25 15:54:06 EDT
The new engines in 1.43.0 fix this, as you suggested in 233772 perhaps you test
and can confirm this?

Note You need to log in before you can comment on or make changes to this bug.