Previous 1 2 Next 26 Replies Latest reply: Apr 15, 2015 9:32 AM by amyseqmedia
ReverendFitty Level 1 Level 1 (0 points)

I recently went through a difficult install of Lion (Fried my RAM). I basically wiped my Hard Drive, installed clean from a thumb drive, created a new user profile, then used migration assistant to move my time machiene files and old user profile over. The only thing that went wrong with this was that my old migrated profile would crash upon start-up, but this went away once I let the system index with my new profile.

 

Cleaning up after this mess, I saw a lost+found folder was created, and an iNode was in there (iNode290815 to be precise). Read what this meant online, and ran disk repair. It seemed to fix whatever problems may have been left over from the install, but the iNode file is still there, and it's 3.6 gigs large. Since Disk Repair checked out, and everything has been running well, is this file ok to delete? I'd like the space back, if possible, or at least move it so its out of sight.

 

Thanks


MacBook Pro, Mac OS X (10.7)
  • gooober Level 1 Level 1 (25 points)

    Hello ReverendFitty,

     

    I too have a very large 3.5G iNode file in lost+found and would like to delete it if it saves space.

     

    But all of the advice that I have read so far has pointed to just ignoring the files in this folder. I do have a time machine backup of it, but will leave it alone until I hear otherwise.

     

    Regards

  • gooober Level 1 Level 1 (25 points)

    Ok. I did some research through the forum postings and found that you can go to the terminal, cd to the folder where the lost+found files are kept and find out more information about the file using the 'file' command.

     

    $ file iNodexxxxx

     

    Once I ran that command I found that the file was an archive. I used the archiving program to list it's contents and found that it was the Lion installer.app!

     

    Since I had already made a copy of this file on an Airdisc connected to the airport extreame, I went ahead and deleted it. Now I'm +3.5G more space.

     

    I would certainly not recommend that removing the file in lost+found for all circumstances, but in my case I thought it would be ok.

     

    Regards,

     

    Mark

  • macjack Level 9 Level 9 (50,625 points)

    You made a good guess. The wrong guess on an iNode file could bring down your Mac. These are low level folders and should not be touched.

    http://en.wikipedia.org/wiki/Inode

    A file system relies on data structures that contain information about the files, beside the file content. The former is called metadata—data which describes data. Each file is associated with an inode, which is identified by an integer number, often referred to as an i-number or inode number.

    Inodes store information about files and folders, such as file ownership, access mode (read, write, execute permissions), and file type. On many types of file system implementations, the maximum number of inodes is fixed at file system creation, limiting the maximum number of files the file system can hold. A typical allocation heuristic for inodes in a file system is one percent of total size.

  • gooober Level 1 Level 1 (25 points)

    Great advice! Thank you. I will never do that again! :|

     

    Regards,

     

    Mark

  • siliguri Level 1 Level 1 (0 points)

    I have found a large 3.67GB iNode file in the lost+found folder in MacintoshHD which after opening turns out to be the installer for OSX Lion. Now my OSX Lion had been installed a month back and has been up and running for a month with intermittent blank screen and Kernel Panic regularly. I wonder whether something had happened with the installation of Lion.

  • Pascal Balthrop Level 1 Level 1 (0 points)

    I have a 3.74gb iNode file in lost+found as well. 'file' in terminal tells me it's an xar archive, same as gooober's. But I wonder: could this file be related to Lion's Recovery Mode?

  • macjack Level 9 Level 9 (50,625 points)

    xar files are Excel auto-recover.

  • jaruzek Level 1 Level 1 (0 points)

    I have a file named "iNode13934595" that is 3.74GB, same as the poster above. I right-clicked and opened it with DiskImageMounter.app, and sure enough it was the Lion install image file.

     

    I assume that deleting it is OK. Gooober did it and still lived.

  • macjack Level 9 Level 9 (50,625 points)

    Once it is in Lost + Found, then it's not a low-level folder anymore.

    Put it in the trash but don't flush.

    Then, restart and see how your Mac behaves. After you're sure things are OK, then delete it.

  • jaruzek Level 1 Level 1 (0 points)

    Did just that, everything is okay. Thanks.

  • bigswarm Level 1 Level 1 (0 points)

    First off, I'm an idiot. I was cleaning up my macbook, and also ran a disk utility. Ended up deleting a desktop folder that held all my work from 2012. It is 100% gone! I tried a few recovery tools, no luck. the only thing I spotted was this lost+found folder that I hadn't noticed before. it has a 3.7 gig file called iNode in it, and that is all. Is there any chance this contains my files?... from earlier strings, it looks like this might just be a lion install backup or something, but I am desperate. Any help is hugely appreciated.

  • gtpinc Level 1 Level 1 (0 points)

    The iNode file when unpacked was the Lion Installer.  I am told by tech support that it should have been deleted at install.....but wasn't.  So I went ahead and trashed it saving me 4+ Gigs of space.


    GT

  • itwasgood Level 1 Level 1 (0 points)

    I have just noticed this Same folder today. However, mine contains 2 Inode files one weighing in @ 4.35 gb and the other @ 3.75 gb. Mounted them both and they are the install files for lion and mountain lion respectively. From what I read in this post it was supposed to be deleted but was not? And happened twice with each new install ? Seems weird to me. So I can go ahead and delete it and free up the 8gb! ?

     

    No I'll effects experienced by u guys?

  • hadzee Level 1 Level 1 (0 points)

    Ditto..except moved the installer to my backup drive and then trashed the iNode file...rebooted..works without a problem

Previous 1 2 Next