Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iNode9982843
- Thread starter saberahul
- Start date
- Sort by reaction score
Should be able to, but may have to try from a terminal session. If it was something important that you needed, you'd have probably known by now
Should be able to, but may have to try from a terminal session. If it was something important that you needed, you'd have probably known by now
OK, thanks. I just double clicked it to see what it was it's "Mac OS X Install ESD". Why it's called iNode I fail to understand.
It could be orphaned for many reasons. Power failure while the file was being accessed (read from or written to), or hard shutdown (holding power button to power off an unresponsive system, etc.
Can be an early sign of hard drive failure, too.
Those are just a couple possibilities. I wouldn't worry about it too much, unless you start finding files in there more often.
OK thanks. I just deleted the entire folder though it'll come back if anything needs to go in there.
It's telling you that the file was tied to inode 9982843 but the reference to that inode is gone (Orphaned inode/file), an inode contains metadata about files. The filenames you see are actually just references to inodes and the inode contains info about the actual file data/contents.
Each file or directory takes up one inode, so if you have a filesystem with enough files then you can run it out of inodes before you run out of storage space.
Anyway, since you found out what the file is then you can do whatever you feel is necessary with it. Just thought I would explain a little about inodes.
Each file or directory takes up one inode, so if you have a filesystem with enough files then you can run it out of inodes before you run out of storage space.
Anyway, since you found out what the file is then you can do whatever you feel is necessary with it. Just thought I would explain a little about inodes.
This isn't uncommon and probably doesn't indicate hardware failure. I had the same thing - I don't recall if the filename was the exact same, but it was the OS X 10.8 installer. When I put the filename into Google then a few threads came up with many other people reporting something similar. It's suspected that Apple botched the cleanup of the OS installer after performing the installation, but nobody really knew for certain.
Either way, you can save it and/or burn it to a disc if you want a copy of the installer. Otherwise, it's safe to delete it.
Either way, you can save it and/or burn it to a disc if you want a copy of the installer. Otherwise, it's safe to delete it.