Fedora13 showed 128 TB /proc/kcore on 2GB RAM

[Peter Larsen]

Chen,
You NEVER EVER want to include /proc, /sys, /tmp, /media, /dev in your
backup/iso. They're not really files but points to other systems data,
or your kernel's internal structures.

If you're on a 64bit machines, then yes - the "virtual" size of these
files can be quite large. That's normal. They're not meant to be
written/read by normal processes. So simply exclude the non persistent
mount points, temporary and "cd/usb" mount points when you do a system
dump like that.

-- 
Best Regards
  Peter Larsen

Wise words of the day:
 Stupid nick highlighting
 Whenever someone starts with "stupid" it highlights the nick.  Hmm.
	-- #Debian

On Mon, 2010-07-12 at 12:24 -0600, Chen, Helen Y wrote:
> Hi,
>  
> I am running Fedora 13 with the 2.6.33.5-112-2.2 kernel, and am trying
> to make an ISO image of my hard disk for other use.  Unfortunately
> “mkisofs” failed because /proc/kcore exceeded its 4GB file size limit.
> In fact, the size of the kcore on my  system is shown to be 128TB, and
> the machine itself only contains 2GB of RAM.  Has anyone experienced
> the same problem?  BTW, the kcore files on my redhat machines reflect
> the actual RAM size as it should be.   Also, does anyone know why
> “mkisofs” even tries to copy a virtual file into the ISO image it is
> creating?  
>  
> Thanks,
> H Chen
>  
>  
>  


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20100712/a87271b1/attachment.bin