修复XFS文件系统方法

1、查看NAS挂载点

root@StorOS ~# mount

/dev/hda1 on / type ext3 (rw,acl)

proc on /proc type proc (rw)

devpts on /dev/pts type devpts (rw,gid=5,mode=620)

tmpfs on /dev/shm type tmpfs (rw)

sysfs on /sys type sysfs (rw)

/dev/hda2 on /var type ext3 (rw,acl)

/dev/hda3 on /b_iscsi type ext3 (rw,acl)

/dev/mapper/st-nd on /nas/nas1 type xfs (rw) 备：XFS

/dev/mapper/st-backup on /mnt/backup type ext3 (rw)

2、停止nas服务

root@StorOS ~# service smb stop

Shutting down SMB services: [ OK ]

Shutting down NMB services: [ OK ]

3、卸载文件挂载点

root@StorOS ~# umount /nas/nas1

备注：/nas/nas1是NAS的挂载目录。

4、确认/nas/nas1目录已没有挂载

root@StorOS ~#mount

5、修复NAS，注意输出结果。

备注：/dev/mapper/st-nd是nas目录的设备名， 按照第一步骤mount查看结果更改

root@StorOS ~# xfs_repair /dev/mapper/st-nd

Phase 1 - find and

Phase 2 - using internal log

-

- scan filesystem freespace and

- found root inode chunk

Phase 3 - for

- scan and clear agi

- process known inodes and perform

- agno = 0

data fork in ino 36099 claims free block 1077701646

data fork in regular inode 36116 claims used block 1077701647

bad data fork in inode 36116

cleared inode 36116

- agno = 1

- agno = 2

- agno = 3

data fork in regular inode 3221253640 claims used block 1145585285

bad data fork in inode 3221253640

cleared inode 3221253640

- agno = 4

- agno = 5

- agno = 6

- agno = 7

- agno = 8

- agno = 9

- agno = 10

- agno = 11

- agno = 12

- agno = 13

- agno = 14

- agno = 15

- agno = 16

- agno = 17

- agno = 18

- agno = 19

- agno = 20

- agno = 21

- agno = 22

- agno = 23

- agno = 24

- agno = 25

- agno = 26

- agno = 27

- agno = 28

- agno = 29

- agno = 30

- agno = 31

- process newly

Phase 4 - check for

- setting up duplicate

- clear lost+found (if it exists) ...

- check for inodes claiming

- agno = 0

entry "耿__护牙_" at block 5 offset 1864 in directory inode 140 references free inode

36116

clearing inode number in entry at

data fork in ino 34363 claims dup extent, off - 0, start - 1145585285, cnt 33

bad data fork in inode 34363

cleared inode 34363

data fork in ino 36099 claims dup extent, off - 0, start - 1077701646, cnt 15

bad data fork in inode 36099

cleared inode 36099

- agno = 1

- agno = 2

- agno = 3

entry "1234_" at block 3 offset 3048 in directory inode 3221225607 references free inode

3221253640

clearing inode number in entry at

- agno = 4

- agno = 5

- agno = 6

- agno = 7

- agno = 8

- agno = 9

- agno = 10

- agno = 11

- agno = 12

- agno = 13

- agno = 14

- agno = 15

- agno = 16

- agno = 17

- agno = 18

- agno = 19

- agno = 20

- agno = 21

- agno = 22

- agno = 23

- agno = 24

- agno = 25

- agno = 26

- agno = 27

- agno = 28

- agno = 29

- agno = 30

- agno = 31

Phase 5 - rebuild AG headers

-

Phase 6 - check

- resetting contents of realtime bitmap and summary inodes

- ensuring existence of lost+found directory

- traversing filesystem starting at / ...

rebuilding directory inode 140

rebuilding directory inode 3221225607

entry "249_AutoSave_" in directory inode 36083 points to free inode 36099, marking

entry to be junked

rebuilding directory inode 36083

entry "" in directory inode 33885 points to free inode

34363, marking entry to be junked

rebuilding directory inode 33885

- traversal finished ...

- traversing all unattached subtrees ...

- traversals finished ...

- moving disconnected inodes to lost+found ...

Phase 7 - verify and correct

resetting inode 1073753124 nlinks from 1 to 2

resetting inode 1073753127 nlinks from 1 to 2

done

备注：根据文件系统的损坏程度决定修复时间的长短。此修复具有一定的危险性，建议用户在修复过程中备份重要数据。

6、重启存储设备

root@StorOS ~#reboot