Sunday February 28th 2021 - Update issue with packman inode mirror
There are issues with the inode mirror, please configure an alternative mirror. See http://packman.links2linux.org/mirrors
Saturday March 3rd 2021 - Missing Packman Tumbleweed Packages
There are issues with package signing since the move last week and these packages have disappeared from the mirrors, see https://lists.links2linux.de/pipermail/packman/2021-March/016623.html for more information... ETA for fix 3/10 or 3/11.
-
Error copying file - 'Error splicing file. Input/output error.'
I am getting the following error when trying to copy a particular file:
'Error splicing file. Input/output error.'
I get this same error from File Manager and from a terminal prompt.
This is being copied to an NTFS partition so might be related to ntfs-3g. Also it is a bit of an obscure file in that the existing file shows as being 127Gb in size but it cannot actually be that big as the whole partition is only 37Gb! It was created by qemu-img converting a VM from hyper-v.
Nick
-
Re: Error copying file - 'Error splicing file. Input/output error.'
On 2012-04-27 12:56, Nick C wrote:
> Also it is a bit of an obscure file in that the existing file
> shows as being 127Gb in size but it cannot actually be that big as the
> whole partition is only 37Gb!
That can happen if it is a sparse file: a file with holes, data that has
not been filled. I did not know that ntfs could do that.
--
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 "Celadon" at Telcontar)
-
Re: Error copying file - 'Error splicing file. Input/output error.'
 Originally Posted by robin_listas
On 2012-04-27 12:56, Nick C wrote:
> Also it is a bit of an obscure file in that the existing file
> shows as being 127Gb in size but it cannot actually be that big as the
> whole partition is only 37Gb!
That can happen if it is a sparse file: a file with holes, data that has
not been filled. I did not know that ntfs could do that.
Before running qemu-img convert on the Win 7 VM I ran sdelete -z otherwise I would have ended up with a real 127Gb file, that is just how qemu-img seems to work. I didn't realize I would end up with a file that could not be copied. Is there any known way around this?
Thanks,
Nick
-
Re: Error copying file - 'Error splicing file. Input/output error.'
On 2012-04-27 21:36, Nick C wrote:
> Before running qemu-img convert on the Win 7 VM I ran sdelete -z
> otherwise I would have ended up with a real 127Gb file, that is just how
> qemu-img seems to work. I didn't realize I would end up with a file
> that could not be copied. Is there any known way around this?
I'm sorry, I'm not familiar with qemu. I only commented on how a file can
be bigger than the available space.
--
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 "Celadon" at Telcontar)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
| |