Find the answer to your Linux question:
Results 1 to 8 of 8
I have CentOS 5.5 running on a VM in a Windows box. When I tried to compile code (a large amount of code, takes ~20 minutes to compile), it spat ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Aug 2011
    Posts
    4

    Help! Removing large corrupt files


    I have CentOS 5.5 running on a VM in a Windows box. When I tried to compile code (a large amount of code, takes ~20 minutes to compile), it spat out garbage and stopped working.

    Now I have quite a few files which are each 4294967295 4294967295 4294967295 in size. They have apparently superceded all permissions, and I cannot even touch them as root.

    I have RTFF, and not found anything on this - if it exists elsewhere, I apologize, please point me to it and I will slink away.

    Help!

  2. #2
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,356
    4294967295 sounds suspiciously like the maximum file size of fat32.
    You dont happen to have the centos VMs virtual discs on fat32 on the windows side?
    You must always face the curtain with a bow.

  3. #3
    Just Joined!
    Join Date
    Aug 2011
    Posts
    4
    It is listed as "Normal (VDI)" in the VM settings. I don't recall having the option to change the formatting of the drive...

  4. #4
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,356
    Ok, just that we talk about the same:
    - The 4Gbyte files are on the windows side.
    - They are the virtual disk(s) for this centos VM
    - The virtual disk has been defined as how big? Probably more than 4GB?
    - You compiled something on CentOS
    - Then the compile went boom

    If so, I donīt get the part of: "..cannot even touch them as root."
    Do you mean windows administrator by any chance?
    That might make sense, as the VM still has the files open.


    My guess so far is:
    - the virtual disc has been defined bigger than 4gb and also as "dynamic growing"
    - your compilation needed more space
    - so VMware/virtualbox/whatever tried to grow the virtual disc files
    - but failed, due to restrictions of the underlying FAT32 filesystem.
    You must always face the curtain with a bow.

  5. #5
    Just Joined!
    Join Date
    Aug 2011
    Posts
    4
    I cannot remove/chmod/chown those files as root in the VM CentOS.

    the virtual disc is 50gb, fixed. I have compiled this same exact code in the past (I've changed only some DB access) without problem. It is the VM running out of memory or similar while compiling causing the files to go crazy, when I start up the VM again, the files are corrupt as previously described.

  6. #6
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,356
    So these files are on the linux side, I take it.
    - which filesystem are you using?
    - can you do a ls -la and lsattr on them?
    - does dmesg or /var/log/message say anything?

    Another thought:
    It might be, that the physical disk has an issue.
    Anything in eventlog or can you use a s.m.a.r.t. tool to query the disc status?
    You must always face the curtain with a bow.

  7. #7
    Just Joined!
    Join Date
    Aug 2011
    Posts
    4
    -I'm not sure what you mean by which filesystem...?

    -I can ls -la (which is how I've seen their size..), lsattr returns "Operation not supported while reading flags on ..."

    -dmesg returns many "attempt to access beyond end of device dm-0: rw=0, want=34359738369, limit=96403456", /var/log/messages reports the same.

    -Eventlog doesn't have anything critical.
    Last edited by etothepi; 08-09-2011 at 10:17 PM.

  8. #8
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,448
    Back to the question about what file system your Windows OS is using. Is it FAT-32, or is it NTFS? You REALLY need to use NTFS in order to deal with VirtualBox virtual discs properly. I use it all the time, and handle files in the VM well over 4GB without problems, but I would NOT try to do so if the host OS is using a FAT file system.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •