求助, lvm 卷 xfs 文件系统,在经过我一番操作后,提示输入输出错误

2018-07-14 00:53:30 +08:00
 yao990

今天手贱,先是用 lvreduce 命令将分区缩小至原来的一半,然后又用 lvextend 命令扩充至原来的大小,然后挂载,挂载可以正常挂载,当用 ls 列出文件时就提示无法打开目录,输入输出错误。 后执行 vgs.lvs.lvdisplay.pvdisplay.df.等命令均显示正常(或以我的水平还无法看出哪里有问题), 但想要进入分区查看文件时就提示输入输出错误,尝试 xfs_repair.xfs_metadump.xfs_growfs 等命令均提示输入输出错误。

现求助各位大侠该怎么办?

8173 次点击
所在节点    Linux
52 条回复
tempdban
2018-07-14 20:47:36 +08:00
你先 dd 备份一下啊
yao990
2018-07-14 21:23:36 +08:00
@tempdban 没那么大的硬盘啊,,,,,,
yao990
2018-07-14 21:57:38 +08:00
@tempdban 这是执行 xfs_repair -n /dev/mapper/centos-home 的结果,请过目
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
ALERT: The filesystem has valuable metadata changes in a log which is being
ignored because the -n option was used. Expect spurious inconsistencies
which may be resolved by first mounting the filesystem to replay the log.
- scan filesystem freespace and inode maps...
agi unlinked bucket 5 is 4068101 in ag 4 (inode=8594002693)
agi unlinked bucket 20 is 24568916 in ag 4 (inode=8614503508)
agi unlinked bucket 56 is 165262648 in ag 4 (inode=8755197240)
agi unlinked bucket 57 is 165262649 in ag 4 (inode=8755197241)
agi unlinked bucket 58 is 165262650 in ag 4 (inode=8755197242)
agi unlinked bucket 59 is 165262651 in ag 4 (inode=8755197243)
agi unlinked bucket 61 is 165262653 in ag 4 (inode=8755197245)
agi unlinked bucket 62 is 165262654 in ag 4 (inode=8755197246)
agi unlinked bucket 41 is 4173929 in ag 3 (inode=6446624873)
agi unlinked bucket 42 is 4173930 in ag 3 (inode=6446624874)
sb_fdblocks 1267635907, counted 1267644099
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 6446624873, would move to lost+found
disconnected inode 6446624874, would move to lost+found
disconnected inode 8594002693, would move to lost+found
disconnected inode 8614381716, would move to lost+found
disconnected inode 8614503508, would move to lost+found
disconnected inode 8755197240, would move to lost+found
disconnected inode 8755197241, would move to lost+found
disconnected inode 8755197242, would move to lost+found
disconnected inode 8755197243, would move to lost+found
disconnected inode 8755197245, would move to lost+found
disconnected inode 8755197246, would move to lost+found
Phase 7 - verify link counts...
would have reset inode 6446624873 nlinks from 0 to 1
would have reset inode 6446624874 nlinks from 0 to 1
would have reset inode 8594002693 nlinks from 0 to 1
would have reset inode 8614381716 nlinks from 0 to 1
would have reset inode 8614503508 nlinks from 0 to 1
would have reset inode 8755197240 nlinks from 0 to 1
would have reset inode 8755197241 nlinks from 0 to 1
would have reset inode 8755197242 nlinks from 0 to 1
would have reset inode 8755197243 nlinks from 0 to 1
would have reset inode 8755197245 nlinks from 0 to 1
would have reset inode 8755197246 nlinks from 0 to 1
No modify flag set, skipping filesystem flush and exiting.
yao990
2018-07-14 22:55:05 +08:00
@tempdban 我刚尝试执行 xfs_repair -L 清空日志,但提示设备忙,直接 xfs_repair 也提示设备忙
ryd994
2018-07-15 02:42:53 +08:00
没硬盘就去买啊
数据值钱还是硬盘值钱,想想清楚
作死不嫌快
tempdban
2018-07-15 11:07:04 +08:00
这些 inode 谁也不知道是什么文件,你胆大就搞,不敢就放在那。
设备忙是因为还有文件描述符没有关闭,fuser
不用每一步就找我确认一下,我说话不用付什么责任的,操作的人还是你
yao990
2018-07-15 12:29:55 +08:00
@tempdban 太感谢了,非常感谢,要不是你的提示,我这会儿还像无头苍蝇一样乱撞。我刚才一个个检查进程,关闭了所有和目标卷有关的进程,然后重新 repair,成功找回了所有文件!太谢谢了
likuku
2018-07-15 12:33:41 +08:00
自作孽不可活,请节哀。

LVM 和 xfs/ext4 来回 resize 以前也玩过多次,有成功也有失败,扩充容易缩小很麻烦必须非常谨慎。

没有可信赖离线备份 /异地备份前提下,还是剁手先。

真这么喜欢折腾,zfs 优先。btrfs 最近几年被坑很多次,还是不推荐它。当然,可信备份不厌其烦。
likuku
2018-07-15 12:36:10 +08:00
看来是主角光环已经恢复了,恭喜。

关于这类高危实验,依然再次推荐在 virtualbox 环境下测试就可以了。
tempdban
2018-07-15 13:53:37 +08:00
@yao990 看你 43 楼的日志还是有 inode 会丢了的,去 lost+found 找
yao990
2018-07-15 15:57:50 +08:00
@likuku 谢谢
yao990
2018-07-15 15:58:02 +08:00
@tempdban 好的,谢谢啦

这是一个专为移动设备优化的页面(即为了让你能够在 Google 搜索结果里秒开这个页面),如果你希望参与 V2EX 社区的讨论,你可以继续到 V2EX 上打开本讨论主题的完整版本。

https://www.v2ex.com/t/470773

V2EX 是创意工作者们的社区,是一个分享自己正在做的有趣事物、交流想法,可以遇见新朋友甚至新机会的地方。

V2EX is a community of developers, designers and creative people.

© 2021 V2EX