服务器 Gind.cn
  1. 服务器 Gind.cn
  3. Centos 6在100％的磁盘内意外不一致
Intereting Posts
CNAME（规范名称logging）是否覆盖A（地址logging）？ 如何设置URL重写到Heroku实例？ stream氓程序在Linux中 控制+标点符号不在terminal注册 在访问消息编辑器中的通讯录时，Outlook 2007挂起 Schannell：从远程服务器接收到的证书是由不受信任的证书颁发机构颁发的 Ubuntu 12.04 – 绑定接口的别名无法正常工作 我可以在OS X上的/ etc / hosts的条目中指定一个端口吗？ rsyslogloggingpath与自定义属性 如果“安装”，则encfs是安全的 是否有任何工具/ API来检查Windows群集的一致性？ 虚拟化 – 十个1Gbps链路还是一个10Gbps链路？ （性能） ESXi：允许来宾操作系统在服务器中使用其他磁盘驱动器 在Linux上configurationBazaar存储库 在Windows Server上备份网站和MySQL数据库

Centos 6在100％的磁盘内意外不一致

我有一个运行的centos 6，它突然失败，由于高达…这导致我们几天以来的切断问题。

当我做： 

df -h S.ficheros Size Used Avail Use% Montado en rootfs 9,7G 9,1G 158M 99% / /dev/root 9,7G 9,1G 158M 99% / none 7,8G 404K 7,8G 1% /dev /dev/md2 101G 188M 96G 1% /home /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/etc/named /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/var/named /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/etc/named.conf /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/etc/named.rfc1912.zones /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/etc/rndc.key /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/usr/lib64/bind /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/etc/named.iscdlv.key /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/etc/named.root.key

当我继续时，我得到： 

 du -sh /var/named/* du: ATENCIÓN: Estructura de directorios circular. Esto quiere decir seguramente que el sistema de ficheros está corrupto. COMUNÍQUELO AL ADMINISTRADOR DEL SISTEMA. El siguiente directorio es parte del ciclo: «/var/named/chroot/var/named/chroot» 268K /var/named/chroot 144K /var/named/data 12K /var/named/dynamic 4,0K /var/named/named.ca 4,0K /var/named/named.empty 4,0K /var/named/named.localhost 4,0K /var/named/named.loopback 4,0K /var/named/slave

所以，我重新进入救援模式，然后我做到了： 

 fdisk -l Disk /dev/sda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0000bd74 Device Boot Start End Blocks Id System /dev/sda1 * 1 1275 10238976+ fd Linux raid autodetect /dev/sda2 1275 14528 106451968 fd Linux raid autodetect /dev/sda3 14528 14593 523264 82 Linux swap / Solaris Disk /dev/sdb: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0000fef6 Device Boot Start End Blocks Id System /dev/sdb1 1 1275 10238976+ fd Linux raid autodetect /dev/sdb2 1275 14528 106451968 fd Linux raid autodetect /dev/sdb3 14528 14593 523264 82 Linux swap / Solaris Disk /dev/md2: 109.0 GB, 109006749696 bytes 2 heads, 4 sectors/track, 26612976 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/md2 doesn't contain a valid partition table Disk /dev/md1: 10.5 GB, 10484645888 bytes 2 heads, 4 sectors/track, 2559728 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/md1 doesn't contain a valid partition table

所以，我做了如下的fsck ： 

 root@rescue:~# fsck -yvf /dev/md2 fsck from util-linux-ng 2.17.2 e2fsck 1.41.12 (17-May-2010) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information 12 inodes used (0.00%) 0 non-contiguous files (0.0%) 0 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 257937 blocks used (0.97%) 0 bad blocks 1 large file 0 regular files 3 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets -------- 3 files root@rescue:~# fsck -yvvvvf /dev/md2 fsck from util-linux-ng 2.17.2 e2fsck 1.41.12 (17-May-2010) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information 12 inodes used (0.00%) 0 non-contiguous files (0.0%) 0 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 257937 blocks used (0.97%) 0 bad blocks 1 large file 0 regular files 3 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets -------- 3 files root@rescue:~# fsck -yvvvvf /dev/md1 fsck from util-linux-ng 2.17.2 e2fsck 1.41.12 (17-May-2010) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information 293166 inodes used (45.66%) 2318 non-contiguous files (0.8%) 98 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 9776/113/0 2391131 blocks used (93.41%) 0 bad blocks 2 large files 236606 regular files 53806 directories 15 character device files 77 block device files 2 fifos 2973 links 2625 symbolic links (2625 fast symbolic links) 26 sockets -------- 296130 files root@rescue:~# e2fsck -yvvvvf /dev/md1 e2fsck 1.41.12 (17-May-2010) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information 293166 inodes used (45.66%) 2318 non-contiguous files (0.8%) 98 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 9776/113/0 2391131 blocks used (93.41%) 0 bad blocks 2 large files 236606 regular files 53806 directories 15 character device files 77 block device files 2 fifos 2973 links 2625 symbolic links (2625 fast symbolic links) 26 sockets -------- 296130 files root@rescue:~# e2fsck -yvvvvf /dev/md2 e2fsck 1.41.12 (17-May-2010) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information 12 inodes used (0.00%) 0 non-contiguous files (0.0%) 0 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 257937 blocks used (0.97%) 0 bad blocks 1 large file 0 regular files 3 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets -------- 3 files root@rescue:~# reboot

但是，当我重新启动，我只是login，然后相同的： 

  df -h S.ficheros Size Used Avail Use% Montado en rootfs 9,7G 9,1G 158M 99% / /dev/root 9,7G 9,1G 158M 99% / none 7,8G 404K 7,8G 1% /dev /dev/md2 101G 188M 96G 1% /home /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/etc/named /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/var/named /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/etc/named.conf /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/etc/named.rfc1912.zones /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/etc/rndc.key /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/usr/lib64/bind /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/etc/named.iscdlv.key /dev/root 9,7G 9,1G 158M 99% /var/named/chroot/etc/named.root.key

请知道那里发生了什么，我已经从根目录删除了tmps，而var，删除了消息日志…这是不重要的，但是在文件系统中是不一致的，任何想法？

find什么占用的空间与du -hx --max-depth=1 / ，然后重复必要（ du -hx --max-depth=1 /usr ，例如），直到你find一个大的，你可以承受失去或绑定到/home 。 下一次，使用LVM，不要将所有的空间预先分配到几乎不用的分区上。

了解什么是填充您的根文件系统 

 cd / du -sx | sort -rn

会给你一个按用途sorting的文件/目录列表。 然后cd到最高的使用率，并重复，直到你找出什么是填补磁盘。