@artoostark 话说智图有 linux 版没有？

@someonetwo 是限速的原因，不过我想表达的意思是，当家里的网速快到一定程度之后，网速快慢就取决于网络服务商的带宽了。

@tempdban 好的，谢谢啦

@likuku 谢谢

我觉得 68 足够了，我就用的这个，但我觉得，家用带宽并不是最重要的，最重要的是，服务提供商要提高出口带宽，不然家用再高也没用，比如，我家 200M，但百度云下载速度只有 2M。。。。。。

@tempdban 太感谢了，非常感谢，要不是你的提示，我这会儿还像无头苍蝇一样乱撞。我刚才一个个检查进程，关闭了所有和目标卷有关的进程，然后重新 repair，成功找回了所有文件！太谢谢了

@tempdban 我刚尝试执行 xfs_repair -L 清空日志，但提示设备忙，直接 xfs_repair 也提示设备忙

@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.

@tempdban 没那么大的硬盘啊，，，，，，

@tempdban 额，不会全丢吧？

支持，望早日成功

@tempdban 另外大概会丢失多少文件？

@tempdban 直接 repair 会报错，也是输入输出错误，repair -L 还没试。你说的那个会丢失部分数据的方法是什么？

@Damenly1 好的，谢谢了

@Damenly1 我发个邮件试试吧，不知道看邮件的人能不能看懂中文？

@tempdban 我执行 vg 恢复以后，研究里一下午 dmesg，但什么都没研究出来，倒是发现之前那个报大小不一致的错误现在不报了。
https://c.cxice.com/thread-2975.htm
这是最新的 dmesg，还请过目。

@msg7086 说的也是啊，感觉这是随机的。

哇，大神你真厉害。不过我这边最后还是老老实实的认证了服务号，因为做微信登录的初衷是方便用户在手机端不用扫码，点击直接登录直接登录，能省钱更好，实在不能省就不省了。小程序登录确实省钱也很方便，不过在手机端每次登录来回跳转，感觉违背了做微信登录的初衷。所以最后没有选择这个方法，另外也没有选开放平台，因为网站主要用户都是手机端的，仔细研究开放平台之后发现开放平台主要针对电脑用户，所以就没有选择。最后谢谢大神了，大神这种钻研精神值得学习！相信这种方案在手机端需求不高的情况下会很好用的！

@msg7086 确定没有成功执行，因为 repair 也提示输入输出错误