Made a dupe of bug 75574, but then thought better of it.
The crash itself is a result of the problem described by bug 75574, but
the reality is that cp would have failed anyway (just without a core-
dump), as it was trying to copy a file that was too large for the
destination filesystem. Regardless of cp's failure mode, for portability
reasons we should not be trying to copy giant files as part of any
upgrade or installation.
jonas: please include the following information:
- the contents of /var/log/dist-upgrade
- the filesystem type of the device which holds the directory
/media/Elements/backup/quetzal/20070426/backup/
- the sizes of the files apache.tar.gz jonas.tar.gz mysql.tar.gz, if you cna
get them.
I'm going to reassign this to the update-manager package, as cp's core
dump (a kernel issue, whose bug-hood actually has grounds for debate) is
already being handled by bug 75574.
** Changed in: update-manager (Ubuntu)
Sourcepackagename: coreutils => update-manager
** Changed in: update-manager (Ubuntu)
Status: Unconfirmed => Needs Info
--
[apport] cp crashed with signal 25 in __kernel_vsyscall()
https://bugs.launchpad.net/bugs/110640
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
