【Linux】记一次xfs分区数据恢复
项目有一块磁盘无法挂载，而且还没有做RAID....
# mount /dev/sda /xxx 报错
mount: special device /dev/sda/ does not exist
(a path prefix is not a directory)
# dmesg | tail -n 100
....
-XFS: bad magic number
-XFS: SB validate failed
-XFS: bad magic number
-XFS: SB validate failed查看messages也没有特别有用的信息
查看/etc/fstab里面的配置也正确没有问题
# cat /etc/fstab
...
/dev/sda /xxx xfs defaults 1 1尝试使用mount -a直接挂在还是报错
# mount -a
mount: wrong fs type, bad option, bad superblock on /dev/sda,
or too many mounted file systemsdmesg | tail -n 100
....
XFS: bad magic number
XFS: SB validate failed
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sda.这次查看messages有报错了
# tail -10 /var/log/messages
kernel: XFS mounting filesystem sda
kernel: XFS: failed to read root inode由于是centos4系统，不是centos7，所以xfs不是默认磁盘分区，恢复工具也不是fsck
# fsck
fsck 1.35 (28-Feb-2004)
fsck: cannot check /dev/sda: fsck.xfs not found这时就陷入了僵局，开始google后，发现有这么一个工具
xfs_check 和xfs_repair 这两个命令可以修复xfs分区异常。
立刻下载安装这个工具，这个工具的包是xfsprogs
yum install xfsprogs -y
.....
安装完成。
在这期间还出现点小插曲。其他同事莫名其妙执行了
fdisk /dev/sda 然后莫名分出来一个/dev/sda1
这波操作有点吓人。。本来数据就有异常，不容易还原，竟然还有心思分区，属实吓到我了
立刻让他先不要动了，先把分区的/dev/sda1 删除，恢复完整的/dev/sda
开始执行恢复工作
# xfs_check /dev/sda
bad agf magic # 0x5256be03 in ag 0
bad agf version # 0x21e82a01 in ag 0
bad agi magic # 0xea702200 in ag 0
bad agi version # 0x302 in ag 0
can't seek in filesystem at bb 56725244801482755
can't read agfl block for ag 1589639201
can't seek in filesystem at bb 56725261580796024
can't read btree block 1589639201/2097414159
can't seek in filesystem at bb 56725262624130048
can't read btree block 1589639201/2227830912
can't seek in filesystem at bb 56725252479682552
can't read btree block 1589639201/959774975
agf_freeblks 68157577, counted 0 in ag 0
agf_longest 1141008009, counted 0 in ag 0
agi_count 134230062, counted 0 in ag 0
agi_freecount 1651470196, counted 0 in ag 0
agi unlinked bucket 0 is 1634166066 in ag 0 (inode=1634166066)
agi unlinked bucket 1 is 539976303 in ag 0 (inode=539976303)
agi unlinked bucket 2 is 1869885287 in ag 0 (inode=1869885287)
agi unlinked bucket 3 is 1920295471 in ag 0 (inode=1920295471)
agi unlinked bucket 4 is 1735554402 in ag 0 (inode=1735554402)
agi unlinked bucket 5 is 778268526 in ag 0 (inode=778268526)
agi unlinked bucket 6 is 1711276032 in ag 0 (inode=1711276032)
agi unlinked bucket 7 is 0 in ag 0 (inode=0)
agi unlinked bucket 8 is 0 in ag 0 (inode=0)
agi unlinked bucket 9 is 0 in ag 0 (inode=0)
agi unlinked bucket 10 is 0 in ag 0 (inode=0)
agi unlinked bucket 11 is 0 in ag 0 (inode=0)
agi unlinked bucket 12 is 0 in ag 0 (inode=0)
agi unlinked bucket 13 is 0 in ag 0 (inode=0)
agi unlinked bucket 14 is 0 in ag 0 (inode=0)
agi unlinked bucket 15 is 0 in ag 0 (inode=0)
agi unlinked bucket 16 is 0 in ag 0 (inode=0)
agi unlinked bucket 17 is 0 in ag 0 (inode=0)
agi unlinked bucket 18 is 4197564558 in ag 0 (inode=4197564558)
agi unlinked bucket 19 is 3633238158 in ag 0 (inode=3633238158)
agi unlinked bucket 20 is 3228001929 in ag 0 (inode=3228001929)
agi unlinked bucket 21 is 771499008 in ag 0 (inode=771499008)
agi unlinked bucket 22 is 6733296 in ag 0 (inode=6733296)
agi unlinked bucket 23 is 520093798 in ag 0 (inode=520093798)
agi unlinked bucket 24 is 2314009447 in ag 0 (inode=2314009447)
agi unlinked bucket 25 is 2283141156 in ag 0 (inode=2283141156)
agi unlinked bucket 26 is 52499 in ag 0 (inode=52499)
agi unlinked bucket 27 is 1726505216 in ag 0 (inode=1726505216)
agi unlinked bucket 28 is 48988 in ag 0 (inode=48988)
agi unlinked bucket 29 is 1140850873 in ag 0 (inode=1140850873)
agi unlinked bucket 30 is 3695509504 in ag 0 (inode=3695509504)
agi unlinked bucket 31 is 704196800 in ag 0 (inode=704196800)
agi unlinked bucket 32 is 4243827432 in ag 0 (inode=4243827432)
agi unlinked bucket 33 is 2550267904 in ag 0 (inode=2550267904)
agi unlinked bucket 34 is 3901489152 in ag 0 (inode=3901489152)
agi unlinked bucket 35 is 16050682 in ag 0 (inode=16050682)
agi unlinked bucket 36 is 4294967179 in ag 0 (inode=4294967179)
agi unlinked bucket 37 is 1143212195 in ag 0 (inode=1143212195)
agi unlinked bucket 38 is 2424832 in ag 0 (inode=2424832)
agi unlinked bucket 39 is 2311284363 in ag 0 (inode=2311284363)
agi unlinked bucket 40 is 1143211110 in ag 0 (inode=1143211110)
agi unlinked bucket 41 is 2734957824 in ag 0 (inode=2734957824)
agi unlinked bucket 42 is 12705796 in ag 0 (inode=12705796)
agi unlinked bucket 43 is 29598168 in ag 0 (inode=29598168)
agi unlinked bucket 44 is 1157628041 in ag 0 (inode=1157628041)
agi unlinked bucket 45 is 2198339584 in ag 0 (inode=2198339584)
agi unlinked bucket 46 is 9049352 in ag 0 (inode=9049352)
agi unlinked bucket 47 is 1140850827 in ag 0 (inode=1140850827)
agi unlinked bucket 48 is 1277431016 in ag 0 (inode=1277431016)
agi unlinked bucket 49 is 1358954496 in ag 0 (inode=1358954496)
agi unlinked bucket 50 is 1720307047 in ag 0 (inode=1720307047)
agi unlinked bucket 51 is 1727999232 in ag 0 (inode=1727999232)
agi unlinked bucket 52 is 620757242 in ag 0 (inode=620757242)
agi unlinked bucket 53 is 1734741761 in ag 0 (inode=1734741761)
agi unlinked bucket 54 is 356525312 in ag 0 (inode=356525312)
agi unlinked bucket 55 is 991424 in ag 0 (inode=991424)
agi unlinked bucket 56 is 1719912449 in ag 0 (inode=1719912449)
agi unlinked bucket 57 is 253935718 in ag 0 (inode=253935718)
agi unlinked bucket 58 is 3927384832 in ag 0 (inode=3927384832)
agi unlinked bucket 59 is 524390 in ag 0 (inode=524390)
agi unlinked bucket 60 is 3088056462 in ag 0 (inode=3088056462)
agi unlinked bucket 61 is 3633234062 in ag 0 (inode=3633234062)
agi unlinked bucket 62 is 3767462030 in ag 0 (inode=3767462030)
agi unlinked bucket 63 is 3498771492 in ag 0 (inode=3498771492)貌似没有太大问题 ，继续执行
# xfs_repair /dev/sda
Phase 1 - find and verify superblock...
sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128
resetting superblock root inode pointer to 128
sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129
resetting superblock realtime bitmap ino pointer to 129
sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130
resetting superblock realtime summary ino pointer to 130
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
bad magic # 0x5256be03 for agf 0
bad version # 568863233 for agf 0
bad sequence # 1589639201 for agf 0
bad length 1720397187 for agf 0, should be 4460544
flfirst 2130938693 in agf 0 too large (max = 128)
fllast 69813508 in agf 0 too large (max = 128)
bad magic # 0xea702200 for agi 0
bad version # 770 for agi 0
bad sequence # -256 for agi 0
bad length # 0 for agi 0, should be 4460544
reset bad agf for ag 0
reset bad agi for ag 0
bad agbno 836484611 in agfl, agno 0
freeblk count 1 != flcount 1711343047 in ag 0
bad agbno 2097414159 for btbno root, agno 0
bad agbno 2227830912 for btbcnt root, agno 0
bad agbno 959774975 for inobt root, agno 0
root inode chunk not found
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
error following ag 0 unlinked list
- process known inodes and perform inode discovery...
- agno = 0
bad magic number 0x5841 on inode 128
bad version number 0x0 on inode 128
bad inode format in inode 128
bad magic number 0x0 on inode 129
bad version number 0x0 on inode 129
bad magic number 0x5841 on inode 130
bad version number 0x0 on inode 130
bad (negative) size -1 on inode 130
bad magic number 0xffff on inode 131
bad version number 0xffffffff on inode 131
bad inode format in inode 131
bad magic number 0x0 on inode 132
bad version number 0x0 on inode 132
bad inode format in inode 132
bad magic number 0x0 on inode 133
bad version number 0x0 on inode 133
bad magic number 0x0 on inode 134
bad version number 0x0 on inode 134
bad magic number 0x0 on inode 135
bad version number 0x0 on inode 135
bad magic number 0x0 on inode 136
bad version number 0x0 on inode 136
bad magic number 0x0 on inode 137
bad version number 0x0 on inode 137
bad magic number 0x0 on inode 138
bad version number 0x0 on inode 138
bad magic number 0x0 on inode 139
bad version number 0x0 on inode 139
bad magic number 0x0 on inode 140
bad version number 0x0 on inode 140
bad magic number 0x0 on inode 141
bad version number 0x0 on inode 141
bad magic number 0x4142 on inode 142
bad version number 0x0 on inode 142
bad inode format in inode 142
bad magic number 0x0 on inode 143
bad version number 0x0 on inode 143
bad magic number 0x0 on inode 144
bad version number 0x0 on inode 144
bad magic number 0x0 on inode 145
bad version number 0x0 on inode 145
bad magic number 0x0 on inode 146
bad version number 0x0 on inode 146
bad magic number 0x0 on inode 147
bad version number 0x0 on inode 147
bad magic number 0x0 on inode 148
bad version number 0x0 on inode 148
bad magic number 0x0 on inode 149
bad version number 0x0 on inode 149
bad magic number 0x0 on inode 150
bad version number 0x0 on inode 150
bad magic number 0x0 on inode 151
bad version number 0x0 on inode 151
bad magic number 0x0 on inode 152
bad version number 0x0 on inode 152
bad magic number 0x0 on inode 153
bad version number 0x0 on inode 153
bad magic number 0x0 on inode 154
bad version number 0x0 on inode 154
bad magic number 0x0 on inode 155
bad version number 0x0 on inode 155
bad magic number 0x0 on inode 156
bad version number 0x0 on inode 156
bad magic number 0x0 on inode 157
bad version number 0x0 on inode 157
bad magic number 0x4142 on inode 158
bad version number 0x0 on inode 158
bad inode format in inode 158
bad magic number 0x0 on inode 159
bad version number 0x0 on inode 159
bad magic number 0x0 on inode 160
bad version number 0x0 on inode 160
bad magic number 0x0 on inode 161
bad version number 0x0 on inode 161
bad magic number 0x0 on inode 162
bad version number 0x0 on inode 162
bad magic number 0x0 on inode 163
bad version number 0x0 on inode 163
bad magic number 0x0 on inode 164
bad version number 0x0 on inode 164
bad magic number 0x0 on inode 165
bad version number 0x0 on inode 165
bad magic number 0x0 on inode 166
bad version number 0x0 on inode 166
bad magic number 0x0 on inode 167
bad version number 0x0 on inode 167
bad magic number 0x0 on inode 168
bad version number 0x0 on inode 168
bad magic number 0x0 on inode 169
bad version number 0x0 on inode 169
bad magic number 0x0 on inode 170
bad version number 0x0 on inode 170
bad magic number 0x0 on inode 171
bad version number 0x0 on inode 171
bad magic number 0x0 on inode 172
bad version number 0x0 on inode 172
bad magic number 0x0 on inode 173
bad version number 0x0 on inode 173
bad magic number 0x4941 on inode 174
bad version number 0x0 on inode 174
bad inode format in inode 174
bad magic number 0x1 on inode 175
bad version number 0x0 on inode 175
bad inode format in inode 175
bad magic number 0x1 on inode 176
bad version number 0x0 on inode 176
bad inode format in inode 176
bad magic number 0x2 on inode 177
bad version number 0x0 on inode 177
bad inode format in inode 177
bad magic number 0x0 on inode 178
bad version number 0x0 on inode 178
bad magic number 0x0 on inode 179
bad version number 0x0 on inode 179
bad magic number 0x0 on inode 180
bad version number 0x0 on inode 180
bad magic number 0x0 on inode 181
bad version number 0x0 on inode 181
bad magic number 0x0 on inode 182
bad version number 0x0 on inode 182
bad magic number 0x0 on inode 183
bad version number 0x0 on inode 183
bad magic number 0x0 on inode 184
bad version number 0x0 on inode 184
bad magic number 0x0 on inode 185
bad version number 0x0 on inode 185
bad magic number 0x0 on inode 186
bad version number 0x0 on inode 186
bad magic number 0x0 on inode 187
bad version number 0x0 on inode 187
bad magic number 0x0 on inode 188
bad version number 0x0 on inode 188
bad magic number 0x0 on inode 189
bad version number 0x0 on inode 189
bad magic number 0x0 on inode 190
bad version number 0x0 on inode 190
bad magic number 0x0 on inode 191
bad version number 0x0 on inode 191
bad magic number 0x5841 on inode 128, resetting magic number
bad version number 0x0 on inode 128, resetting version number
bad inode format in inode 128
cleared root inode 128
bad magic number 0x0 on inode 129, resetting magic number
bad version number 0x0 on inode 129, resetting version number
imap claims a free inode 129 is in use, correcting imap and clearing inode
cleared realtime bitmap inode 129
bad magic number 0x5841 on inode 130, resetting magic number
bad version number 0x0 on inode 130, resetting version number
bad (negative) size -1 on inode 130
cleared realtime summary inode 130
bad magic number 0xffff on inode 131, resetting magic number
bad version number 0xffffffff on inode 131, resetting version number
bad inode format in inode 131
cleared inode 131
bad magic number 0x0 on inode 132, resetting magic number
bad version number 0x0 on inode 132, resetting version number
bad inode format in inode 132
cleared inode 132
bad magic number 0x0 on inode 133, resetting magic number
bad version number 0x0 on inode 133, resetting version number
bad magic number 0x0 on inode 134, resetting magic number
bad version number 0x0 on inode 134, resetting version number
bad magic number 0x0 on inode 135, resetting magic number
bad version number 0x0 on inode 135, resetting version number
bad magic number 0x0 on inode 136, resetting magic number
bad version number 0x0 on inode 136, resetting version number
bad magic number 0x0 on inode 137, resetting magic number
bad version number 0x0 on inode 137, resetting version number
bad magic number 0x0 on inode 138, resetting magic number
bad version number 0x0 on inode 138, resetting version number
bad magic number 0x0 on inode 139, resetting magic number
bad version number 0x0 on inode 139, resetting version number
bad magic number 0x0 on inode 140, resetting magic number
bad version number 0x0 on inode 140, resetting version number
bad magic number 0x0 on inode 141, resetting magic number
bad version number 0x0 on inode 141, resetting version number
bad magic number 0x4142 on inode 142, resetting magic number
bad version number 0x0 on inode 142, resetting version number
bad inode format in inode 142
cleared inode 142
bad magic number 0x0 on inode 143, resetting magic number
bad version number 0x0 on inode 143, resetting version number
bad magic number 0x0 on inode 144, resetting magic number
bad version number 0x0 on inode 144, resetting version number
bad magic number 0x0 on inode 145, resetting magic number
bad version number 0x0 on inode 145, resetting version number
bad magic number 0x0 on inode 146, resetting magic number
bad version number 0x0 on inode 146, resetting version number
bad magic number 0x0 on inode 147, resetting magic number
bad version number 0x0 on inode 147, resetting version number
bad magic number 0x0 on inode 148, resetting magic number
bad version number 0x0 on inode 148, resetting version number
bad magic number 0x0 on inode 149, resetting magic number
bad version number 0x0 on inode 149, resetting version number
bad magic number 0x0 on inode 150, resetting magic number
bad version number 0x0 on inode 150, resetting version number
bad magic number 0x0 on inode 151, resetting magic number
bad version number 0x0 on inode 151, resetting version number
bad magic number 0x0 on inode 152, resetting magic number
bad version number 0x0 on inode 152, resetting version number
bad magic number 0x0 on inode 153, resetting magic number
bad version number 0x0 on inode 153, resetting version number
bad magic number 0x0 on inode 154, resetting magic number
bad version number 0x0 on inode 154, resetting version number
bad magic number 0x0 on inode 155, resetting magic number
bad version number 0x0 on inode 155, resetting version number
bad magic number 0x0 on inode 156, resetting magic number
bad version number 0x0 on inode 156, resetting version number
bad magic number 0x0 on inode 157, resetting magic number
bad version number 0x0 on inode 157, resetting version number
bad magic number 0x4142 on inode 158, resetting magic number
bad version number 0x0 on inode 158, resetting version number
bad inode format in inode 158
cleared inode 158
bad magic number 0x0 on inode 159, resetting magic number
bad version number 0x0 on inode 159, resetting version number
bad magic number 0x0 on inode 160, resetting magic number
bad version number 0x0 on inode 160, resetting version number
bad magic number 0x0 on inode 161, resetting magic number
bad version number 0x0 on inode 161, resetting version number
bad magic number 0x0 on inode 162, resetting magic number
bad version number 0x0 on inode 162, resetting version number
bad magic number 0x0 on inode 163, resetting magic number
bad version number 0x0 on inode 163, resetting version number
bad magic number 0x0 on inode 164, resetting magic number
bad version number 0x0 on inode 164, resetting version number
bad magic number 0x0 on inode 165, resetting magic number
bad version number 0x0 on inode 165, resetting version number
bad magic number 0x0 on inode 166, resetting magic number
bad version number 0x0 on inode 166, resetting version number
bad magic number 0x0 on inode 167, resetting magic number
bad version number 0x0 on inode 167, resetting version number
bad magic number 0x0 on inode 168, resetting magic number
bad version number 0x0 on inode 168, resetting version number
bad magic number 0x0 on inode 169, resetting magic number
bad version number 0x0 on inode 169, resetting version number
bad magic number 0x0 on inode 170, resetting magic number
bad version number 0x0 on inode 170, resetting version number
bad magic number 0x0 on inode 171, resetting magic number
bad version number 0x0 on inode 171, resetting version number
bad magic number 0x0 on inode 172, resetting magic number
bad version number 0x0 on inode 172, resetting version number
bad magic number 0x0 on inode 173, resetting magic number
bad version number 0x0 on inode 173, resetting version number
bad magic number 0x4941 on inode 174, resetting magic number
bad version number 0x0 on inode 174, resetting version number
bad inode format in inode 174
cleared inode 174
bad magic number 0x1 on inode 175, resetting magic number
bad version number 0x0 on inode 175, resetting version number
bad inode format in inode 175
cleared inode 175
bad magic number 0x1 on inode 176, resetting magic number
bad version number 0x0 on inode 176, resetting version number
bad inode format in inode 176
cleared inode 176
bad magic number 0x2 on inode 177, resetting magic number
bad version number 0x0 on inode 177, resetting version number
bad inode format in inode 177
cleared inode 177
bad magic number 0x0 on inode 178, resetting magic number
bad version number 0x0 on inode 178, resetting version number
bad magic number 0x0 on inode 179, resetting magic number
bad version number 0x0 on inode 179, resetting version number
bad magic number 0x0 on inode 180, resetting magic number
bad version number 0x0 on inode 180, resetting version number
bad magic number 0x0 on inode 181, resetting magic number
bad version number 0x0 on inode 181, resetting version number
bad magic number 0x0 on inode 182, resetting magic number
bad version number 0x0 on inode 182, resetting version number
bad magic number 0x0 on inode 183, resetting magic number
bad version number 0x0 on inode 183, resetting version number
bad magic number 0x0 on inode 184, resetting magic number
bad version number 0x0 on inode 184, resetting version number
bad magic number 0x0 on inode 185, resetting magic number
bad version number 0x0 on inode 185, resetting version number
bad magic number 0x0 on inode 186, resetting magic number
bad version number 0x0 on inode 186, resetting version number
bad magic number 0x0 on inode 187, resetting magic number
bad version number 0x0 on inode 187, resetting version number
bad magic number 0x0 on inode 188, resetting magic number
bad version number 0x0 on inode 188, resetting version number
bad magic number 0x0 on inode 189, resetting magic number
bad version number 0x0 on inode 189, resetting version number
bad magic number 0x0 on inode 190, resetting magic number
bad version number 0x0 on inode 190, resetting version number
bad magic number 0x0 on inode 191, resetting magic number
bad version number 0x0 on inode 191, resetting version number
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
root inode lost
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 6
- agno = 8
- agno = 7
- agno = 9
- agno = 10
- agno = 11
- agno = 13
- agno = 12
- agno = 14
- agno = 15
entry ".." at block 0 offset 32 in directory inode 134217902 references free inode 189
clearing inode number in entry at offset 32...
no .. entry for directory 134217902
entry ".." at block 0 offset 32 in directory inode 134221408 references free inode 136
clearing inode number in entry at offset 32...
no .. entry for directory 134221408
entry "dbdata" in shortform directory 2013266048 references non-existent inode 11889632
junking entry "dbdata" in directory inode 2013266048
- agno = 5
entry "dblogs" in shortform directory 2013276640 references free inode 132
junking entry "dblogs" in directory inode 2013276640
entry ".." at block 0 offset 32 in directory inode 135836896 references free inode 131
clearing inode number in entry at offset 32...
no .. entry for directory 135836896
Phase 5 - rebuild AG headers and trees...
- reset superblock...
Phase 6 - check inode connectivity...
reinitializing root directory
reinitializing realtime bitmap inode
reinitializing realtime summary inode
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ...
bad hash table for directory inode 134217902 (no data entry): rebuilding
rebuilding directory inode 134217902
bad hash table for directory inode 134221408 (no data entry): rebuilding
rebuilding directory inode 134221408
bad hash table for directory inode 135836896 (no data entry): rebuilding
rebuilding directory inode 135836896
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected dir inode 134217902, moving to lost+found
disconnected dir inode 134221408, moving to lost+found
disconnected dir inode 135836896, moving to lost+found
disconnected dir inode 269011168, moving to lost+found
disconnected dir inode 269011169, moving to lost+found
disconnected dir inode 324386881, moving to lost+found
disconnected dir inode 402653312, moving to lost+found
disconnected dir inode 1610621057, moving to lost+found
Phase 7 - verify and correct link counts...
resetting inode 128 nlinks from 2 to 3
resetting inode 2013266048 nlinks from 4 to 3
resetting inode 2013276640 nlinks from 4 to 3
done完成后，尝试挂载磁盘
# mount /dev/sda /xxx
挂载成功
# cd /xxx
# cd lost+found
可以看到一些数字，就是repair最后生成的
进入到最新的一个里面
# ls
-drwxr-xr-x 2 root root 4.0K Feb 19 2019 134217902
-drwxr-xr-x 2 root root 4.0K Jul 7 09:23 134221408
-drwxr-xr-x 2 root root 4.0K Jun 21 2016 135836896
-drwxr-xr-x 5 root root 48 Aug 28 2018 1610621057
-drwxr-xr-x 2 root root 25 Jul 28 2016 269011168
-drwxr-xr-x 2 root root 25 Feb 26 2019 269011169
-drwxr-xr-x 2 root root 25 Aug 4 07:59 324386881
-drwxr-xr-x 8 root root 138 Aug 4 07:04 402653312
# cd 402653312
看到了想要恢复的数据。一切非常顺利最后有几点需要注意。
1.磁盘无法挂载后，千万千万不要尝试格式化磁盘和分区，不然数据真的就找不到了
2.如果xfs_repair /dev/sda 使用异常，还是没有成功，尝试使用xfs_repair -L /dev/sda 但是但是，需要注意，使用-L选项后，数据会有部分丢失，这点要特别注意，但是不使用-L数据不会丢失。除非异常操作
3.恢复数据后，记得本地异地都要备份。
【Linux】记一次xfs分区数据恢复的更多相关文章
- DiskGenius(磁盘分区/数据恢复) 32位 V4.9.1 免费绿色版
软件名称: DiskGenius(磁盘分区/数据恢复) 32位 软件语言: 简体中文 授权方式: 免费软件 运行环境: Win 32位/64位 软件大小: 19.5MB 图片预览: 软件简介: Dis ...
- Linux创建和挂载XFS文件系统测试实践
XFS文件系统简介 维基百科关于XFS的简介如下: XFS is a high-performance 64-bit 年,由Silicon Graphics为他们的IRIX操作系统而开发,是IRIX ...
- Linux 基础教程 33-硬盘分区及挂载
挂载命令 在Windows系统中如果插入了U盘.移动硬盘.光驱等,只要能被Windows系统识别出来,则系统会进行自动挂载并添加盘符,然后我们就可以访问,而这一切均由系统完成,用户并不需要做任 ...
- linux下给U盘分区&制作文件系统
这几天读到TLCL-Storage Media一节,不由的想要折腾一下U盘,一直以来U盘只是被拿来暂存数据,其内部有没有文件系统,数据怎么管理,那是从来也不清楚,本文就依葫芦画瓢,折腾下手中的King ...
- 安装 Linux 时碰到的硬盘分区的陷阱及应对
硬盘分区的陷阱及应对 之所以想到写这篇,是因为本人在折腾 Linux 系统的过程中,有多次掉入硬盘分区的陷阱的经历.最近几天,再一次掉入坑中,折腾了两天才从坑中爬出来.经过多方查询资料,终于弄明白了硬 ...
- Linux安装时内存如何分区的相关问题
Linux系统安装时内存如何分区:Linux系统必须的分区是根分区(/)和swap交换分区.普通用户一般分三个区,一个根分区(/),一个家目录(home分区),一个交换分区(swap分区),以80G的 ...
- Linux中的SWAP交换分区
大多数 Linux 在系统安装时都会提醒并建议你划分一个 SWAP 交换分区,如果你是从 Windows 切换到 Linux 的新用户,兴许对这个 SWAP 会感到十分疑惑. SWAP 交换分区到底是 ...
- 为linux系统添加虚拟内存swap分区
阿铭linux学习笔记之swap分区 一.作用: swap分区是交换分区,在系统物理内存不足时与swap进行交换,对web服务器的性能影响极大,通过调整swap分区大小来提升服务器的性能,节省资源费用 ...
- linux（ubuntu）下分区和格式化sd卡
我的手机sd卡需要分成两个分区,在windowxp下面死活搞不成.主要的问题是,window只认识sd卡的第一个分区.有人用修改驱动程序,让windows把sd卡认成日立的microdisk,分区和格 ...
随机推荐
- Android全面解析之Window机制
前言 你好! 我是一只修仙的猿,欢迎阅读我的文章. Window,读者可能更多的认识是windows系统的窗口.在windows系统上,我们可以多个窗口同时运行,每个窗口代表着一个应用程序.但在安卓上 ...
- 一文带你彻底了解大数据处理引擎Flink内存管理
摘要: Flink是jvm之上的大数据处理引擎. Flink是jvm之上的大数据处理引擎,jvm存在java对象存储密度低.full gc时消耗性能,gc存在stw的问题,同时omm时会影响稳定性.同 ...
- css进阶 03-网页设计和开发中，关于字体的常识
03-网页设计和开发中,关于字体的常识 #前言 我周围的码农当中,有很多是技术大神,却常常被字体这种简单的东西所困扰. 这篇文章,我们来讲一讲关于字体的常识.这些常识所涉及到的问题,有很强的可操作性, ...
- 基于excel实现接口自动化测试
本文档介绍如何使用excel管理接口测试用例并一键执行的实现方式,其中包括 python 读写excel, request库的基本操作,接口用例的设计 接口用例设计 用例字段描述 被依赖表达式: 示例 ...
- python一键搭建ftp服务
from pyftpdlib.authorizers import DummyAuthorizer from pyftpdlib.handlers import FTPHandler from pyf ...
- Windows 系列GVLK密钥
以下是GVLK密钥版本对照表,可配合KMS服务器进行使用. Windows 系列GVLK密钥 Windows Server 2019 Operating system edition KMS Clie ...
- [PASECA2019]honey_shop writeup
这是PASECA2019的一道web题 前端是一个蜂蜜商店,你有$1336,可以买蜂蜜和flag.但是flag要$1337,所以我们只能买蜂蜜. 一般这种题目的常规操作就是通过修改你的钱使你能够买到f ...
- 腾讯云联合多家生态伙伴，重磅开源 SuperEdge 边缘容器项目
在2020年12月19-20日腾讯 Techo Park 开发者大会上,腾讯云联合英特尔.VMware 威睿.虎牙.寒武纪.美团.首都在线,共同发布 SuperEdge 边缘容器开源项目. Super ...
- 在ubuntu上利用科大讯飞的SDK实现语音识别-语义识别等功能
首先,参考科大讯飞的官方sdk中的案例,实现和机器的日常对话和控制. 具体步骤: 1. 通过麦克风捕获说话的声音,然后通过在线语音识别获取语音中的字符. 2. 将获取到的字符上传到科大讯飞的语义识别中 ...
- logback日志对象要素
<logger>节点 分两种 1.是普通日志对象 logger分为2种,一种是普通日志对象,另一种是根日志对象.对于大部分应用来说,只设置根日志对象即可. 在java日志系统中,无论是lo ...