我在使用以下方法复制大量文件时遇到了这个问题tar -cf - * | (cd ../bar; tar -xf - );
我确实搜索了这个问题，并找到了以下建议，但对我都不起作用。即使重启后，这个问题仍然存在。
问题的一个特点是目标磁盘只是 NTFS 中的数据磁盘，因为我使用的是双启动（ubuntu 20.04 和 Windows 10）。因此，我尝试使用校验在 Windows 10 中（见下面的第 6 点），但这并没有多大帮助。在 Windows 10 中启动时，我也无法将文件复制到磁盘中，但看到一条不同的消息说“碎片太多”，所以我尝试使用 Windows 工具对磁盘进行碎片整理，但优化没有进行。我不认为“碎片太多”是真正的问题，因为在 15T 空间中只使用了 2T，而且磁盘才两个月大。
有人能建议我还可以尝试哪些方法吗？非常感谢您的专业知识！
- 检查磁盘空间<- 有足够的空间（有问题的磁盘是/mnt/e（倒数第二个） DF-H
Filesystem Size Used Avail Use% Mounted on
udev 252G 0 252G 0% /dev
tmpfs 51G 32M 51G 1% /run
/dev/nvme0n1p2 1.8T 828G 912G 48% /
tmpfs 252G 15M 252G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 252G 0 252G 0% /sys/fs/cgroup
/dev/loop0 128K 128K 0 100% /snap/bare/5
/dev/loop1 56M 56M 0 100% /snap/core18/2246
/dev/loop2 62M 62M 0 100% /snap/core20/1169
/dev/loop3 219M 219M 0 100% /snap/gnome-3-34-1804/72
/dev/loop5 56M 56M 0 100% /snap/core18/2128
/dev/loop4 66M 66M 0 100% /snap/gtk-common-themes/1519
/dev/loop6 9.5M 9.5M 0 100% /snap/htop/3233
/dev/nvme0n1p1 511M 5.3M 506M 2% /boot/efi
/dev/nvme1n1p3 1.9T 1.2T 665G 65% /mnt/c
/dev/loop7 33M 33M 0 100% /snap/snapd/13640
/dev/loop8 51M 51M 0 100% /snap/snap-store/547
/dev/loop9 33M 33M 0 100% /snap/snapd/13270
/dev/loop10 66M 66M 0 100% /snap/gtk-common-themes/1515
tmpfs 51G 16K 51G 1% /run/user/125
/dev/sda2 15T 12T 3.3T 78% /mnt/z
/dev/sdb2 15T 2.0T 13T 14% /mnt/e
tmpfs 51G 36K 51G 1% /run/user/1000
- inode 使用率 <- 1% 用于/mnt/e，DF-我
Filesystem Inodes IUsed IFree IUse% Mounted on
udev 65989773 1100 65988673 1% /dev
tmpfs 65997179 8821 65988358 1% /run
/dev/nvme0n1p2 122068992 1554395 120514597 2% /
tmpfs 65997179 40 65997139 1% /dev/shm
tmpfs 65997179 5 65997174 1% /run/lock
tmpfs 65997179 18 65997161 1% /sys/fs/cgroup
/dev/loop0 29 29 0 100% /snap/bare/5
/dev/loop1 10833 10833 0 100% /snap/core18/2246
/dev/loop2 11732 11732 0 100% /snap/core20/1169
/dev/loop3 18500 18500 0 100% /snap/gnome-3-34-1804/72
/dev/loop5 10803 10803 0 100% /snap/core18/2128
/dev/loop4 65095 65095 0 100% /snap/gtk-common-themes/1519
/dev/loop6 3605 3605 0 100% /snap/htop/3233
/dev/nvme0n1p1 0 0 0 - /boot/efi
/dev/nvme1n1p3 698250164 1718509 696531655 1% /mnt/c
/dev/loop7 479 479 0 100% /snap/snapd/13640
/dev/loop8 15841 15841 0 100% /snap/snap-store/547
/dev/loop9 474 474 0 100% /snap/snapd/13270
/dev/loop10 64986 64986 0 100% /snap/gtk-common-themes/1515
tmpfs 65997179 45 65997134 1% /run/user/125
/dev/sda2 3505524112 20634 3505503478 1% /mnt/z
/dev/sdb2 13549630048 3278197 13546351851 1% /mnt/e
tmpfs 65997179 94 65997085 1% /run/user/1000
磁盘/文件权限问题<-不是问题
增加 inotify.max_user_watches。它原来是 65536，现在增加到 524288，但没用
检查 du -h 和 df -h 返回的大小。两者相同
磁盘可能已损坏 <- Windows chkdsk 发现一个不相关的孤立文件，已修复。在第二次运行 chkdsk 时，Windows 中未发现任何问题， chkdsk E：/f
Stage 2: Examining file name linkage ...
Deleted invalid filename Refinitiv\References (2BE9F9) in directory 5.
File 2BE9F9 has been orphaned since all its filenames were invalid
Windows will recover the file in the orphan recovery phase.
Correcting minor file name errors in file 2BE9F9.
Deleting index entry Refinitiv\References in index $I30 of file 5.
6 reparse records processed.
3630180 index entries processed.
Index verification completed.
Phase duration (Index verification): 14.18 minutes.
CHKDSK is scanning unindexed files for reconnect to their original directory.
1 unindexed files scanned.
0 unindexed files recovered to original directory.
Phase duration (Orphan reconnection): 0.00 milliseconds.
CHKDSK is recovering remaining unindexed files.
1 unindexed files recovered to lost and found.
Lost and found is located at \found.000
Phase duration (Orphan recovery to lost and found): 0.00 milliseconds.
6 reparse records processed.
Phase duration (Reparse point and Object ID verification): 8.49 milliseconds.
- lsof/ | grep “已删除” --> 没有这样的文件或目录，并出现以下警告
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/125/gvfs Output information may be incomplete.
lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing Output information may be incomplete.