在initramfs中使用fsck时的操作的影响

我有一个公司服务器托pipe的VPS无法启动以下问题:

/dev/mapper/vg00-lv01 contains a file system with errors, check forced. Inodes that were part of a corrupted orphan linked list found. /dev/mapper/vg00-lv01: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY (ie, without -a or -p options) fsck exited with status code 4 The root filesystem on /dev/dm-0 requires a manual fsck modprobe: modulo ehci-orion not found in modules.dep (initramfs) 

联系我的提供商后,他们告诉我,问题出在我身上,而且我必须运行以下命令:

 fsck /dev/mapper/vg00-lv01 

这里是命令的输出:

 fsck from util-linux 2.25.2 e2fsck 1.42.12 (29-Aug-14) /dev/mapper/vg00-lv01 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inodes that were part of a corrupted orphan linked list found. Fix(y)? n Inode 2258929 was part of the orphaned inode list. IGNORED. ... (9 more similar lines) Deleted inode 9461576 has zero dtime. Fix(y)? n Inode 9461578 was part of the orphaned inode list. IGNORED. ... (5 more similar lines) Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong (14902881, counted=14900324) Fix(y)? n Inode bitmap differences: -2258929 -2258935 ... (some other numbers) Fix(y)? n Free inodes count wrong (8427713, counted=8427682) Fix(y)? n /dev/mapper/vg00-lv01: ******** WARNING: Filesystem still has errors ******* /dev/mapper/vg00-lv01: 1902399/10330112 files (0.1% non-contiguous), 26413471/41316352 blocks 

我有两个问题:

  • 修复(回答这些)有哪些风险?
  • 这可能是什么造成的? 服务器目前只运行一些docker集装箱。

对不起,如果这不属于ServeurFault。