Damage causes and repair methods of Linux file system

The main content of this article is "Linux file system damage causes and repair methods", interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Now let the editor to take you to learn "Linux file system damage causes and repair methods" it!

Sometimes you will face such an error when maintaining a Linux server, that is, showing that the file system becomes (Read Only System), that is, the file system becomes read-only. There may be two reasons for this problem, one is that there is a problem with the synchronization mechanism when writing to multiple machines, and the other is that the server is powered off when writing to a stand-alone machine.

When this problem occurs, it will make application users very nervous. If they are lucky, they can read the data only. If they are unlucky, the system will not be able to start at all.

Here is a solution:

(1) modify / etc/fstab, comment out the damaged file system first, and use mount-o remount rw if you can't read or write the file, / change the file system to read-write mode.

(2) execute fsck commands, such as fsck / dev/sda1, for damaged file systems.

Note:

(1) it is best to back up the data before execution to prevent data loss after repair failure.

At this point, I believe that everyone on the "Linux file system damage causes and repair methods" have a deeper understanding, might as well to the actual operation of it! Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!