#542199 coreutils: mv segfaults when moving files out of /tmp

Package:
coreutils
Source:
coreutils
Description:
GNU core utilities
Submitter:
Stephen Dann
Date:
2011-10-23 03:18:03 UTC
Severity:
normal
#542199#5
Date:
2009-08-18 12:11:45 UTC
From:
To:
When I try to move a file from /tmp, the command segfaults:

stephen@sdlaptop:~$ mv /tmp/foo bar
Segmentation fault (core dumped)

The file has been copied to the destination, but the source is still
there.

When I try it in gdb, I get the following output:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f7e312cc760 (LWP 15818)]
0x00007f7e30ab13d6 in attr_copy_fd () from /lib/libattr.so.1
(gdb) bt
#0  0x00007f7e30ab13d6 in attr_copy_fd () from /lib/libattr.so.1
#1  0x0000000000409759 in ?? ()
#2  0x0000000000409bff in ?? ()
#3  0x0000000000402ccd in ?? ()
#4  0x0000000000403787 in ?? ()
#5  0x00007f7e3077c5c6 in __libc_start_main () from /lib/libc.so.6
#6  0x0000000000402bd9 in ?? ()
#7  0x00007ffffeacf878 in ?? ()
#8  0x000000000000001c in ?? ()
#9  0x0000000000000003 in ?? ()
#10 0x00007ffffead15f6 in ?? ()
#11 0x00007ffffead15fe in ?? ()
#12 0x00007ffffead1607 in ?? ()
#13 0x0000000000000000 in ?? ()

I hope this is useful.
#542199#10
Date:
2009-08-18 13:27:14 UTC
From:
To:
I'd love reports from anyone else who can duplicate this.

Mike Stone
#542199#17
Date:
2011-10-23 02:59:32 UTC
From:
To:
Comment from the peanut gallery here, in the interest of getting this bug
closed...


Is this problem continuing to manifest?

If so, then:

Could your `mv` executable or libattr.so.1 library have been corrupted?
(gamma ray from the Sun?)

Looking at the `gdb` output, it looks pretty likely this bug belongs to
the libattr1 package, not coreutils.

What type of filesystem is /tmp? What mount options are in use for /tmp?

What type of filesystem is the destination? What mount options are in use
for the destination?

If you've tried changing any of those, what did you try and what effect
did it have?