Server disk read-only repair process

Server disk also do not monitor, in fact, I do not know how to monitor the status of the disk, and suddenly see the new data, go up and look at the disk situation, found that the disk is read-only situation, unable to write data, if everyone who knows how to monitor the disk read-only method, you can tell me, to a high up some.

First, the processing process

1, disk bad track check

After the problem occurs, the business is first stopped, and then the disk is unloaded for repair, this problem may be the disk track has a bad area, I first check the disk bad path situation.

Badblocks-sv/dev/sdb

Almost checked for some time and found no bad way.

2. Repair Disk File system

Repair the file system when found unable to repair, prompting superblock invalid.

[[email protected] ~]# fsck -t ext4 /dev/ sdbfsck from util-linux-ng 2.17.2e2fsck 1.41.12  (17-may-2010) fsck.ext4:  Superblock invalid, trying backup blocks...fsck.ext4: bad magic number  in super-block while trying to open /dev/sdbthe superblock could  not be read or does not describe a correct ext2filesystem.   if the device is valid and it really contains an  ext2filesystem  (And not swap or ufs or something else),  Then the superblockis corrupt, and you might try running e2fsck  with an alternate superblock:    e2fsck -b 8193 < Device> 

3. View File system backup Superblock

[[email protected] ~]# mke2fs -n /dev/sdb          mke2fs 1.41.12  (17-may-2010)/dev/sdb is entire device, not just  one partition! proceed anyway?  (y,n)  yFilesystem label=OS type: LinuxBlock size=4096  (log=2) fragment size=4096  (log=2) stride=1 blocks, stripe width=0 blocks122093568  inodes, 488364854 blocks24418242 blocks  (5.00%)  reserved for the super  userFirst data block=0Maximum filesystem blocks=429496729614904 block  Groups32768 blocks per group, 32768 fragments per group8192 inodes  per groupSuperblock backups stored on blocks:          32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,         4096000, 7962624,  11239424, 20480000, 23887872, 71663616, 78675968,          102400000, 214990848

4. Repair File System

E2fsck-b 214990848-y/dev/sdb

There's a lot of fixes that have been fixed for a while

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7A/73/wKiom1apjujAPrm0AAFZSUwUmjk850.png "title=" Qq20160128114507.png "alt=" Wkiom1apjujaprm0aafzsuwumjk850.png "/>

After the repair, mount the directory to view the following

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/7A/73/wKioL1apj3SS_9GTAAFsBQmz7nU638.png "title=" Qq20160128114638.png "alt=" Wkiol1apj3ss_9gtaafsbqmz7nu638.png "/>

Somehow it just loses the name of the folder, and the rest of the reply is left to the DBA for action.

This article is from the "Little Water Drop" blog, please make sure to keep this source http://wangzan18.blog.51cto.com/8021085/1739473

Server disk read-only repair process