我正在使用 rsync 脚本将我的家用计算机备份到远程 WD MyCloud。我最近在 WD MyCloud 上发现了无法删除的目录。这是一个例子：
MyHomeCloud:/DataVolume/shares/DalesDesktop/e+/2015-12-26/Documents and Settings/All Users
/Start Menu/Programs# rm -f Garmin
rm: cannot remove `Garmin': Input/output error
MyHomeCloud:/DataVolume/shares/DalesDesktop/e+/2015-12-26/Documents and Settings/All Users
/Start Menu/Programs# ls -li
ls: cannot access Garmin: Input/output error
total 4
? d????????? ? ? ? ? ? Garmin
90309235 drwxrwxrwx 3 197608 197121 4096 Dec 26 23:33 Proton Development Suite
MyHomeCloud:/DataVolume/shares/DalesDesktop/e+/2015-12-26/Documents and Settings/All Users
/Start Menu/Programs#
我希望这些是逻辑错误而不是硬件错误。
WD MyCloud 上的 Linux 是：
uname -a
Linux MyHomeCloud 3.2.26 #1 SMP Thu Jul 9 11:14:15 PDT 2015 wd-2.4-rel armv7l GNU/Linux
dmesga 之后的最后几行reboot是：
[ 73.079642] Hfs+/HfsJ support included
[ 73.079646] optimized: speed
[ 73.079649] Build_for__WD_Sequoia_k3.2.26_2015-03-06_lke_9.2.0_r248522_b40
[ 73.079655]
[ 73.112027] initcall init_module+0x0/0x188 [ufsd] returned 0 after 35758 usecs
[ 78.115289] EXT4-fs (sda4): barriers disabled
[ 80.394824] EXT4-fs (sda4): warning: mounting fs with errors, running e2fsck is recommended
[ 81.006617] EXT4-fs (sda4): mounted filesystem with writeback data mode. Opts: acl,user_xattr,data=writeback,barrier=0,init_itable=10
[ 81.181229] EXT4-fs (sda4): re-mounted. Opts: user_xattr,barrier=0,data=writeback
[ 98.962509] Adding 500672k swap on /dev/sda3. Priority:-1 extents:1 across:500672k
[ 118.222076] calling init_module+0x0/0x200 [netatop] @ 6599
[ 118.228708] initcall init_module+0x0/0x200 [netatop] returned 0 after 894 usecs
MyHomeCloud:~#
这表明我需要运行e2fsck，所以我尝试umount，首先我这样做是为了获取更多信息：
MyHomeCloud:~# parted -l /dev/sda?
Model: ATA WDC WD60EFRX-68L (scsi)
Disk /dev/sda: 6001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Number Start End Size File system Name Flags
3 15.7MB 528MB 513MB linux-swap(v1) primary
1 528MB 2576MB 2048MB ext3 primary raid
2 2576MB 4624MB 2048MB ext3 primary raid
5 4624MB 4724MB 99.6MB primary
6 4724MB 4824MB 101MB primary
7 4824MB 4826MB 1049kB primary
8 4826MB 4828MB 2097kB primary
4 4828MB 6001GB 5996GB ext4 primary
Model: Linux Software RAID Array (md)
Disk /dev/md1: 2048MB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 2048MB 2048MB ext3
然后我试试这个：
MyHomeCloud:~# umount /dev/sda4
MyHomeCloud:~# echo "$?"
0
MyHomeCloud:~# e2fsck /dev/sda4
e2fsck 1.42.5 (29-Jul-2012)
/dev/sda4 is mounted.
e2fsck: Cannot continue, aborting.
MyHomeCloud:~#
我怎样才能umount这样呢e2fsck？
我还尝试使用smartctl它报告短期测试没有问题，但长期测试将需要大约 14 小时，我已经推迟这样做，直到我确定我需要运行它。
编辑 1：我跑去mount查看 /dev/sda4 上安装了哪些目录：
MyHomeCloud:~# mount
/dev/root on / type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=40960k,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=40960k)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,relatime,size=10240k,mode=755)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime,size=102400k,nr_inodes=20480)
/dev/root on /var/log.hdd type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered)
ramlog-tmpfs on /var/log type tmpfs (rw,relatime,size=40960k)
/dev/sda4 on /DataVolume type ext4 (rw,noatime,nodiratime,user_xattr,barrier=0,data=writeback)
/dev/sda4 on /CacheVolume type ext4 (rw,noatime,nodiratime,user_xattr,barrier=0,data=writeback)
/dev/sda4 on /nfs/Public type ext4 (rw,noatime,nodiratime,user_xattr,barrier=0,data=writeback)
/dev/sda4 on /nfs/DalesDesktop type ext4 (rw,noatime,nodiratime,user_xattr,barrier=0,data=writeback)
/dev/sda4 on /nfs/TimeMachineBackup type ext4 (rw,noatime,nodiratime,user_xattr,barrier=0,data=writeback)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
MyHomeCloud:~#
然后我lsof +D在这些目录上运行，结果如下：
MyHomeCloud:~# lsof +D /DataVolume/
lsof: WARNING: can't lstat(/DataVolume/shares/DalesDesktop/e+/2015-12-26/Documents and Settings/All Users/Start Menu/Programs/Garmin): Input/output error
lsof: WARNING: can't lstat(/DataVolume/shares/DalesDesktop/e+/2015-12-26/Documents and Settings/All Users/Start Menu/Programs/Proton Development Suite/Proteus 7 Professional): Input/output error
MyHomeCloud:~# lsof +D /CacheVolume/
MyHomeCloud:~# lsof +D /nfs/Public/
MyHomeCloud:~# lsof +D /nfs/DalesDesktop/
lsof: WARNING: can't lstat(/nfs/DalesDesktop/e+/2015-12-26/Documents and Settings/All Users/Start Menu/Programs/Garmin): Input/output error
lsof: WARNING: can't lstat(/nfs/DalesDesktop/e+/2015-12-26/Documents and Settings/All Users/Start Menu/Programs/Proton Development Suite/Proteus 7 Professional): Input/output error
lsof: WARNING: can't lstat(/nfs/DalesDesktop/e+/2015-12-14/!---Dale/Keuka/SeeBoard/carm3.bmp): No child processes
lsof: can't fork: Cannot allocate memory
MyHomeCloud:~# lsof +D /nfs/TimeMachineBackup/
MyHomeCloud:~#
我使用lsof得当吗？我没有看到任何需要终止的进程，但看起来我还需要修复有关文件 carm3.bmp 的某些内容
另外，这是我的 /etc/fstab ：
MyHomeCloud:~# cat /etc/fstab
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
## found that Access DLNA can sometimes temporarily use up to 70M of the /tmp space
## increasing to 100M maximum
## setting number of inodes to 20K
tmpfs /tmp tmpfs rw,size=100M,nr_inodes=20K 0 0
/dev/md1 / ext3 defaults,noatime,nodiratime,data=writeback,barrier=0 0 0
MyHomeCloud:~#
我没有看到任何与 /dev/sda4 相关的内容，我的解释正确吗？
为什么我的 /etc/fstab 中只有 /dev/md1 ，为什么我的查询结果mount甚至不包括 /etc/fstab 中的 /dev/md1 ？
漫长的测试smartctl在大约16小时内完成，没有出现任何错误。
编辑2：在我的文件中找到此评论后/etc/rc.local：
#
# Note: WD-NAS related post-boot finalization functionality is moved to /etc/init.d/wdInitFinalize script
#
我看了/etc/init.d/wdInitFinalize剧本。我想这可能是挂载/dev/sda4的启动脚本。作为 Linux 新手，我对脚本不太了解。
我可以将此脚本移至另一个目录并尝试重新启动吗？
哇，现在这是一个坏主意。我决定重命名 wdInitFinalize，然后重新启动。大错！！重新启动从未完成。无法通过 ssh 访问它，也无法使用 WD 本地 Web 界面。还以为是变砖了必须打开 MyCloud 外壳，取出驱动器，通过 Sata 电缆将其连接到我的 Win7 计算机，安装 Ext2Fsd，以便我最终可以重命名两个系统分区上的该文件，重新组装 MyCloud，执行“按 40 秒按钮”重置MyCloud，然后重新输入我的所有 myCloud 设置（最重要的是启用 ssh）。直到那时我才回到开始的地方（有一些文件系统错误:)。
----------------- 解决方案 - 解决方案 - 解决方案 - 解决方案 -----------------:
注意：我了解到，确认 aumount成功的最简单的检查就是简单地重复特定的umount.如果umount成功，您将收到一条消息，告诉您它尚未安装！
这是过程（也许可以做得更少，但这对我有用）：
1fuser -vm对顽固卷的所有目录（在我的例子中为 /dev/sda4）执行此操作。您可以使用 来查看那些已安装的目录mount。
2 杀死fuser 显示的所有PID。
3 umount单独的所有这些目录（两次参见上面的注释）
4 umount顽固卷本身（两次）
5 e2fsck顽固的体积（带有任何 - 选项，例如说 -y 来回答带有 y 的问题）
6 为了格外小心，我在修复错误后重新启动。
感谢@psui 指导我完成这项繁琐的工作！
以下是我执行的详细命令：
MyHomeCloud:/etc/init.d# fuser -vm /DataVolume
USER PID ACCESS COMMAND
/DataVolume: root kernel mount /DataVolume
root 9363 F...m restsdk-server
root 16542 f.... lsof
MyHomeCloud:/etc/init.d# kill 16542
-bash: kill: (16542) - No such process
MyHomeCloud:/etc/init.d# kill 9363
MyHomeCloud:/etc/init.d# umount /DataVolume
umount: /DataVolume: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
MyHomeCloud:/etc/init.d# fuser -vm /DataVolume
USER PID ACCESS COMMAND
/DataVolume: root kernel mount /DataVolume
root 10507 f.... du
MyHomeCloud:/etc/init.d# kill 10507
MyHomeCloud:/etc/init.d# fuser -vm /DataVolume
USER PID ACCESS COMMAND
/DataVolume: root kernel mount /DataVolume
MyHomeCloud:/etc/init.d# umount /DataVolume
MyHomeCloud:/etc/init.d# umount /DataVolume
umount: /DataVolume/: not mounted
MyHomeCloud:/etc/init.d# umount /CacheVolume
MyHomeCloud:/etc/init.d# umount /CacheVolume
umount: /CacheVolume: not mounted
MyHomeCloud:/etc/init.d# umount /nfs/Public
MyHomeCloud:/etc/init.d# umount /nfs/Public
umount: /nfs/Public: not mounted
MyHomeCloud:/etc/init.d# umount /nfs/DalesDesktop
MyHomeCloud:/etc/init.d# umount /nfs/DalesDesktop
umount: /nfs/DalesDesktop: not mounted
MyHomeCloud:/etc/init.d# umount /nfs/TimeMachineBackup
MyHomeCloud:/etc/init.d# umount /nfs/TimeMachineBackup
umount: /nfs/TimeMachineBackup: not mounted
MyHomeCloud:/etc/init.d# mount
/dev/root on / type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=40960k,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=40960k)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,relatime,size=10240k,mode=755)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime,size=102400k,nr_inodes=20480)
/dev/root on /var/log.hdd type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered)
ramlog-tmpfs on /var/log type tmpfs (rw,relatime,size=40960k)
/dev/sda4 on /nfs/Dale type ext4 (rw,noatime,nodiratime,user_xattr,barrier=0,data=writeback)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
MyHomeCloud:/etc/init.d# umount /nfs/Dale
MyHomeCloud:/etc/init.d# umount /nfs/Dale
umount: /nfs/Dale: not mounted
MyHomeCloud:/etc/init.d# umount /dev/sda4
umount: /dev/sda4: not mounted
MyHomeCloud:/etc/init.d# e2fsck /dev/sda4
e2fsck 1.42.5 (29-Jul-2012)
/dev/sda4 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 4456616 has zero dtime. Fix<y>? yes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 58261515 was part of the orphaned inode list. FIXED.
Inode 58261571 was part of the orphaned inode list. FIXED.
Inode 58261592 was part of the orphaned inode list. FIXED.
Deleted inode 58261593 has zero dtime. Fix<y>? yes
Inode 84607406 was part of the orphaned inode list. FIXED.
Deleted inode 84607407 has zero dtime. Fix<y>? yes
Deleted inode 166068240 has zero dtime. Fix<y>? yes
Inode 166068241 was part of the orphaned inode list. FIXED.
Inode 166068242 was part of the orphaned inode list. FIXED.
Inode 166068243 was part of the orphaned inode list. FIXED.
Deleted inode 166068245 has zero dtime. Fix<y>? yes
Inode 166068246 was part of the orphaned inode list. FIXED.
Inode 166068247 was part of the orphaned inode list. FIXED.
Inode 166068248 was part of the orphaned inode list. FIXED.
Deleted inode 166068326 has zero dtime. Fix<y>? yes
Inode 166068339 was part of the orphaned inode list. FIXED.
Deleted inode 166068615 has zero dtime. Fix<y>? yes
Extended attribute block 1332744333 has reference count 4, should be 2. Fix<y>? yes
Pass 2: Checking directory structure
Entry '..' in .../??? (4456624) has deleted/unused inode 4456618. Clear<y>? yes
Entry 'Proteus 7 Professional' in /shares/DalesDesktop/e+/2015-12-26/Documents and Settings/All Users/Start Menu/Programs/Proton Development Suite (90309235) has deleted/unused inode 100467315. Clear<y>? yes
Entry 'Garmin' in /shares/DalesDesktop/e+/2015-12-26/Documents and Settings/All Users/Start Menu/Programs (4719331) has deleted/unused inode 85590643. Clear<y>? yes
Pass 3: Checking directory connectivity
Unconnected directory inode 4456624 (...)
Connect to /lost+found<y>? yes
Pass 4: Checking reference counts
Inode 4456624 ref count is 3, should be 2. Fix<y>? yes
Inode 4719331 ref count is 4, should be 3. Fix<y>? yes
Inode 23466035 ref count is 16, should be 15. Fix<y>? yes
Inode 23466036 ref count is 16, should be 15. Fix<y>? yes
Inode 23466037 ref count is 16, should be 15. Fix<y>? yes
Inode 23528078 ref count is 16, should be 15. Fix<y>? yes
Inode 23528079 ref count is 16, should be 15. Fix<y>? yes
Inode 23528080 ref count is 16, should be 15. Fix<y>? yes
Inode 23528081 ref count is 16, should be 15. Fix<y>? yes
Inode 23528082 ref count is 16, should be 15. Fix<y>? yes
Inode 23528083 ref count is 16, should be 15. Fix<y>? yes
Inode 23528084 ref count is 16, should be 15. Fix<y>? yes
Inode 23528085 ref count is 16, should be 15. Fix<y>? yes
Inode 23528086 ref count is 16, should be 15. Fix<y>? yes
Inode 23528087 ref count is 16, should be 15. Fix<y>? yes
Inode 23528088 ref count is 16, should be 15. Fix<y>? yes
Inode 23528089 ref count is 16, should be 15. Fix<y>? yes
Inode 23528090 ref count is 16, should be 15. Fix<y>? yes
Inode 23528091 ref count is 16, should be 15. Fix<y>? yes
Inode 23528092 ref count is 16, should be 15. Fix<y>? yes
Inode 23528093 ref count is 16, should be 15. Fix<y>? yes
Inode 23528094 ref count is 16, should be 15. Fix<y>? yes
Inode 23528095 ref count is 16, should be 15. Fix<y>? yes
Inode 23528096 ref count is 16, should be 15. Fix<y>? yes
Inode 23528097 ref count is 16, should be 15. Fix<y>? yes
Inode 23528098 ref count is 16, should be 15. Fix<y>? yes
Inode 23528099 ref count is 16, should be 15. Fix<y>? yes
Inode 23528100 ref count is 16, should be 15. Fix<y>? yes
Inode 23528101 ref count is 16, should be 15. Fix<y>? yes
Inode 23528102 ref count is 16, should be 15. Fix<y>? yes
Inode 23528103 ref count is 16, should be 15. Fix<y>? yes
Inode 23528104 ref count is 16, should be 15. Fix<y>? yes
Inode 23528105 ref count is 16, should be 15. Fix<y>? yes
Inode 23528106 ref count is 16, should be 15. Fix<y>? yes
Inode 23528107 ref count is 16, should be 15. Fix<y>? yes
Inode 23528108 ref count is 16, should be 15. Fix<y>? yes
Inode 23528109 ref count is 16, should be 15. Fix<y>? yes
Inode 32506004 ref count is 14, should be 13. Fix<y>? yes
Inode 32506005 ref count is 14, should be 13. Fix<y>? yes
Inode 32506015 ref count is 14, should be 13. Fix<y>? yes
Inode 58720627 ref count is 12, should be 11. Fix<y>? yes
Inode 90309235 ref count is 3, should be 2. Fix<y>? yes
Inode 179700859 ref count is 14, should be 15. Fix<y>? yes
Inode 179700860 ref count is 14, should be 15. Fix<y>? yes
Inode 179700861 ref count is 14, should be 15. Fix<y>? yes
Inode 179700862 ref count is 14, should be 15. Fix<y>? yes
Inode 179700863 ref count is 14, should be 15. Fix<y>? yes
Inode 179700864 ref count is 14, should be 15. Fix<y>? yes
Inode 179700865 ref count is 14, should be 15. Fix<y>? yes
Inode 179700866 ref count is 14, should be 15. Fix<y>? yes
Inode 179700867 ref count is 14, should be 15. Fix<y>? yes
Inode 179700868 ref count is 14, should be 15. Fix<y>? yes
Inode 179700869 ref count is 14, should be 15. Fix<y>? yes
Inode 179700870 ref count is 14, should be 15. Fix<y>? yes
Inode 179700884 ref count is 14, should be 15. Fix<y>? yes
Inode 179700885 ref count is 14, should be 15. Fix<y>? yes
Inode 179700913 ref count is 14, should be 15. Fix<y>? yes
Inode 179700914 ref count is 14, should be 15. Fix<y>? yes
Inode 179700915 ref count is 14, should be 15. Fix<y>? yes
Inode 179700916 ref count is 14, should be 15. Fix<y>? yes
Inode 179700917 ref count is 14, should be 15. Fix<y>? yes
Inode 179701633 ref count is 14, should be 15. Fix<y>? yes
Inode 179701634 ref count is 14, should be 15. Fix<y>? yes
Inode 179701635 ref count is 14, should be 15. Fix<y>? yes
Inode 179701636 ref count is 14, should be 15. Fix<y>? yes
Inode 179701640 ref count is 14, should be 15. Fix<y>? yes
Inode 179701642 ref count is 14, should be 15. Fix<y>? yes
Inode 179701643 ref count is 14, should be 15. Fix<y>? yes
Inode 179701648 ref count is 14, should be 15. Fix<y>? yes
Pass 5: Checking group summary information
Block bitmap differences: -35656376 -466096174 -466096194 -466124842 -466124915 -466128388 -466128396 -466128399 -466128405 -466128410 -466130267 -466130269 -466130272 -466130275 -466130279 -466130286 -466130290 -466130296 -466130312 -466131490 -466131492 -466131495 -466131500 -676860386 -(676889088--676889089) -676889091 -676889094 -676889097 -676889101 -676889108 -676889112 -676889118 -676889134 -1328549952 -(1328550033--1328550034) -1328550301 -(1328578561--1328578568)
Fix<y>? yes
Free blocks count wrong for group #1088 (28278, counted=28279).
Fix<y>? yes
Free blocks count wrong for group #14224 (27997, counted=27999).
Fix<y>? yes
Free blocks count wrong for group #14225 (31816, counted=31836).
Fix<y>? yes
Free blocks count wrong for group #20656 (27980, counted=27981).
Fix<y>? yes
Free blocks count wrong for group #20657 (32758, counted=32768).
Fix<y>? yes
Free blocks count wrong for group #20896 (28002, counted=28003).
Fix<y>? yes
Free blocks count wrong for group #24528 (27998, counted=27999).
Fix<y>? yes
Free blocks count wrong for group #24544 (27997, counted=27998).
Fix<y>? yes
Free blocks count wrong for group #24560 (28002, counted=28003).
Fix<y>? yes
Free blocks count wrong for group #40544 (28260, counted=28264).
Fix<y>? yes
Free blocks count wrong for group #40545 (32758, counted=32766).
Fix<y>? yes
Free blocks count wrong (1296055779, counted=1296055829).
Fix<y>? yes
Inode bitmap differences: -4456616 -58261515 -58261571 -(58261592--58261593) -(84607406--84607407) -(166068240--166068243) -(166068245--166068248) -166068326 -166068339 -166068615
Fix<y>? yes
Free inodes count wrong for group #1088 (3643, counted=3644).
Fix<y>? yes
Directories count wrong for group #1088 (362, counted=361).
Fix<y>? yes
Free inodes count wrong for group #14224 (3391, counted=3395).
Fix<y>? yes
Directories count wrong for group #14224 (635, counted=633).
Fix<y>? yes
Free inodes count wrong for group #20656 (3464, counted=3466).
Fix<y>? yes
Directories count wrong for group #20656 (631, counted=630).
Fix<y>? yes
Free inodes count wrong for group #20896 (3458, counted=3459).
Fix<y>? yes
Directories count wrong for group #20896 (638, counted=637).
Fix<y>? yes
Free inodes count wrong for group #24528 (3458, counted=3459).
Fix<y>? yes
Directories count wrong for group #24528 (638, counted=637).
Fix<y>? yes
Free inodes count wrong for group #24544 (3458, counted=3459).
Fix<y>? yes
Directories count wrong for group #24544 (638, counted=637).
Fix<y>? yes
Free inodes count wrong for group #24560 (3458, counted=3459).
Fix<y>? yes
Directories count wrong for group #24560 (638, counted=637).
Fix<y>? yes
Free inodes count wrong for group #40544 (3706, counted=3717).
Fix<y>? yes
Directories count wrong for group #40544 (377, counted=374).
Fix<y>? yes
Free inodes count wrong (181303937, counted=181303959).
Fix<y>? yes
/dev/sda4: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda4: 1693033/182996992 files (0.4% non-contiguous), 167896043/1463951872 blocks
MyHomeCloud:/etc/init.d#
答案1
您必须停止使用该卷才能卸载它。您可以使用 来追踪仍在该卷上保持文件打开状态的程序，lsof然后将其杀死。此外，它应该在安装之前自动进行 fscked。确保 /etc/fstab 中卷的 fsck 顺序（最后一列旁边）未设置为零，因为这会禁用自动 fsck。