Re: cp: I do not understand ...

On 2007-12-28, Charles Lavin <x@xxx> wrote:

[copying (most likely) sparse files fails]
I originally tried backup/restore.

Yes, but did you try using backup/restore with the source filesystem
*unmounted*?

You could (as an alternative) try to find the sparse files on the source
filesystem. Look for (very) large files, and then use "du" to see how much
space they take on disk. Or try to script something. If there are maybe one or
two files causing your problems, you might be able to just recreate them
on the new filesystem instead of copying them over.

--
Jurjen Oskam

Savage's Law of Expediency:
You want it bad, you'll get it bad.
.

Relevant Pages

  • Re: cp: I do not understand ...
    ... but did you try using backup/restore with the source filesystem ... You could try to find the sparse files on the source ... on the new filesystem instead of copying them over. ...
    (comp.unix.aix)
  • Re: /usr/bin/cp preserving holes ?
    ... >> supports sparse files, but I don't see that it has anything to do with NFS ... >> some differences in the block count (due to differences in filesystem ... Absent a decent interface to determine hole location, ...
    (comp.unix.solaris)
  • Re: O_DIRECT question
    ... there _is_ a problem, because they don't care. ... I don't regard it as a system failing that I am allowed to shoot myself ... Suppose you have a filesystem, not at all related to databases and stuff. ... "hope that sparse files are handled right" is a high hope. ...
    (Linux-Kernel)
  • Removal of sparse file settings
    ... Does any of You how to remove the 'Sparse file' settings on a jfs2 filesystem? ... We've got a jfs2 filesystem, the sap adm user, and the oracle adm user got 'unlimited' settings, like this: ... I can see that the filesystem is using 'sparse files', but how it got that setting, I don't know.. ...
    (comp.unix.aix)
  • Re: Incorrect file size?
    ... Filesystem Size Used Avail Capacity Mounted on ... /dev/ar0s1a on / (ufs, local) ... This is most likely due to the use of 'sparse files': ...
    (freebsd-stable)