因此我尝试安装一个包并得到以下输出...
phys1ks@DIGITALL-Crunchy:~$ sudo dpkg -i teamviewer_linux.deb
(Reading database ... 142512 files and directories currently installed.)
Preparing to unpack teamviewer_linux.deb ...
Error: No space left on device
Removed symlink /etc/systemd/system/graphical.target.wants/teamviewerd.service.
Unpacking teamviewer9 (9.0.32150) over (9.0.32150) ...
Setting up teamviewer9 (9.0.32150) ...
Error: No space left on device
Processing triggers for menu (2.1.47) ...
phys1ks@DIGITALL-Crunchy:~$
df 的输出显示我有足够的空间......
phys1ks@DIGITALL-Crunchy:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sdg2 129G 6.6G 116G 6% /
udev 10M 0 10M 0% /dev
tmpfs 6.3G 9.9M 6.3G 1% /run
tmpfs 16G 72K 16G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/md0p1 2.7T 431G 2.2T 17% /home
tmpfs 3.2G 4.0K 3.2G 1% /run/user/118
//192.168.11.1/nccs/00_NDOLPH/00_CrashPlan_Backup/ 1.0T 461G 564G 45% /mnt/backup
tmpfs 3.2G 8.0K 3.2G 1% /run/user/1000
phys1ks@DIGITALL-Crunchy:~$ df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sdg2 8552448 163621 8388827 2% /
udev 4104065 582 4103483 1% /dev
tmpfs 4114442 862 4113580 1% /run
tmpfs 4114442 3 4114439 1% /dev/shm
tmpfs 4114442 4 4114438 1% /run/lock
tmpfs 4114442 13 4114429 1% /sys/fs/cgroup
/dev/md0p1 183115776 1215741 181900035 1% /home
tmpfs 4114442 6 4114436 1% /run/user/118
//192.168.11.1/nccs/00_NDOLPH/00_CrashPlan_Backup/ 0 0 0 - /mnt/backup
tmpfs 4114442 15 4114427 1% /run/user/1000
phys1ks@DIGITALL-Crunchy:~$ df -m
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/sdg2 131285 6739 117855 6% /
udev 10 0 10 0% /dev
tmpfs 6429 10 6419 1% /run
tmpfs 16073 1 16072 1% /dev/shm
tmpfs 5 1 5 1% /run/lock
tmpfs 16073 0 16073 0% /sys/fs/cgroup
/dev/md0p1 2816079 441310 2231698 17% /home
tmpfs 3215 1 3215 1% /run/user/118
//192.168.11.1/nccs/00_NDOLPH/00_CrashPlan_Backup/ 1048573 471282 577292 45% /mnt/backup
tmpfs 3215 1 3215 1% /run/user/1000
phys1ks@DIGITALL-Crunchy:~$ free -h
total used free shared buffers cached
Mem: 31G 4.8G 26G 12M 907M 1.1G
-/+ buffers/cache: 2.9G 28G
Swap: 7.5G 0B 7.5G
phys1ks@DIGITALL-Crunchy:~$
我已经完成了所有操作sudo apt-get clean，并sudo touch /forcefsck在重启时强制检查文件。但没有任何帮助……
更多信息 -
尝试更改哈希类型后，我现在看到的是这个......
phys1ks@DIGITALL-Crunchy:~$ sudo dpkg -i teamviewer_linux.deb
[sudo] password for phys1ks:
Selecting previously unselected package teamviewer9.
(Reading database ... 144541 files and directories currently installed.)
Preparing to unpack teamviewer_linux.deb ...
Unpacking teamviewer9 (9.0.32150) ...
Setting up teamviewer9 (9.0.32150) ...
Error: No space left on device
Job for teamviewerd.service failed. See 'systemctl status teamviewerd.service' and 'journalctl -xn' for details.
Processing triggers for menu (2.1.47) ...
phys1ks@DIGITALL-Crunchy:~$ sudo journalctl -xn
-- Logs begin at Tue 2014-11-18 15:00:37 CST, end at Tue 2014-11-18 15:02:32 CST. --
Nov 18 15:01:48 DIGITALL-Crunchy systemd[1]: Activated swap /dev/disk/by-path/pci-0000:07:00.0-scsi-0:1:12:0-part1.
-- Subject: Unit dev-disk-by\x2dpath-pci\x2d0000:07:00.0\x2dscsi\x2d0:1:12:0\x2dpart1.swap has finished start-up
-- Defined-By: systemd
-- Support:
--
-- Unit dev-disk-by\x2dpath-pci\x2d0000:07:00.0\x2dscsi\x2d0:1:12:0\x2dpart1.swap has finished starting up.
--
-- The start-up result is done.
Nov 18 15:01:48 DIGITALL-Crunchy systemd[1]: Starting TeamViewer remote control daemon...
-- Subject: Unit teamviewerd.service has begun with start-up
-- Defined-By: systemd
-- Support:
--
-- Unit teamviewerd.service has begun starting up.
Nov 18 15:01:48 DIGITALL-Crunchy systemd[1]: PID file /var/run/teamviewerd.pid not readable (yet?) after start.
Nov 18 15:01:48 DIGITALL-Crunchy systemd[1]: Failed to add watch on /: too many watches
Nov 18 15:01:48 DIGITALL-Crunchy systemd[1]: Failed to set a watch for teamviewerd.service's PID file /var/run/teamviewerd.pid: No space left on device
Nov 18 15:01:48 DIGITALL-Crunchy systemd[1]: Failed to start TeamViewer remote control daemon.
-- Subject: Unit teamviewerd.service has failed
-- Defined-By: systemd
-- Support:
--
-- Unit teamviewerd.service has failed.
--
-- The result is failed.
Nov 18 15:01:48 DIGITALL-Crunchy systemd[1]: Unit teamviewerd.service entered failed state.
Nov 18 15:01:49 DIGITALL-Crunchy sudo[2545]: pam_unix(sudo:session): session closed for user root
Nov 18 15:02:32 DIGITALL-Crunchy sudo[4558]: phys1ks : TTY=pts/0 ; PWD=/home/phys1ks ; USER=root ; COMMAND=/bin/journalctl -xn
Nov 18 15:02:32 DIGITALL-Crunchy sudo[4558]: pam_unix(sudo:session): session opened for user root by phys1ks(uid=0)
phys1ks@DIGITALL-Crunchy:~$
答案1
该服务是否确实有效或者错误信息是否有意义？
我之所以问这个问题，是因为在使用 systemd 启动/停止服务时，我遇到了类似的错误消息，结果发现这是因为我用完了 inotify 监视。在我的情况下，用完这些监视的原因是我正在运行 CrashPlan 备份软件：http://support.code42.com/CrashPlan/Latest/Troubleshooting/Real-Time_Backup_For_Network-Attached_Drives#linux
另一件需要注意的事情是查看文件系统上的 inode 是否用完了：df -ih
答案2
我假设您使用的是 ext4。这不太可能发生，但我能想到的唯一其他解释是哈希冲突。ext4 功能dir_index允许大型目录按哈希排序存储其条目。两个不同的名称可能会给出相同的哈希，因此无法添加第二个名称。您可以尝试切换使用的哈希算法，看看是否能解决问题。您需要从另一个磁盘启动，以便可以切换哈希算法并 fsck 卷：
tune2fs -E hash_alg=tea /dev/sdg2
e2fsck -fD /dev/sdg2