Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
I recently notice error on the filesystem; after fsck (and after fixing several errors) I notice that some files were gone.
It's possible that errors on the file system make file disappear?
Thankyou
Yes, files whose structure cannot be repaired (they are corrupted) have their inode removed, deleting the file. Using a journaling filesystem, like EXT4 can help prevent this from occurring. Regular filesystem checks, which are the default, will also help prevent errors from accumulating, which can cause this to happen.
Last edited by macemoneta; 09-20-2011 at 01:45 PM.
Yes, files whose structure cannot be repaired (they are corrupted) have their inode removed, deleting the file. Using a journaling filesystem, like EXT4 can help prevent this from occurring. Regular filesystem checks, which are the default, will also help prevent errors from accumulating, which can cause this to happen.
Thankyou macemoneta.
So ext3 isn't good enough (it was my case)?
Each partition has a directory called lost+found. When fsck finds file fragments which it is unable to identify it places them in that partitions lost+found directory and gives them a meaningless name. If you have files in lost+found you might be able to identify them from the contents of the file.
Be sure that you are looking in the correct lost+found directory. There is one for every partition.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.