Disk Space increase and clearing

Hello again,
Finlly I arrived to recover my files, and reinstall the whole server, but again, after just installing, and re-puting in production, i find:

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

But when i do:

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/slaves

I'm finding journal errors into this /var/named directories, so, i reboot into rescue mode, as the server is remote, and then run:

root@rescue:~# fdisk -l 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/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/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 root@rescue:~# fsck -yvf /dev/sda1 fsck from util-linux-ng 2.17.2 fsck: fsck.linux_raid_member: not found fsck: Error 2 while executing fsck.linux_raid_member for /dev/sda1 root@rescue:~# fsck -yvf /dev/sda2 fsck from util-linux-ng 2.17.2 fsck: fsck.linux_raid_member: not found fsck: Error 2 while executing fsck.linux_raid_member for /dev/sda2 root@rescue:~# fsck -yvf /dev/sda3 fsck from util-linux-ng 2.17.2 fsck: fsck.swap: not found fsck: Error 2 while executing fsck.swap for /dev/sda3 root@rescue:~# fsck -yvf /dev/md1 fsck from util-linux-ng 2.17.2 e2fsck 1.41.12 (17-May-2010) /: recovering journal 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 /: ***** FILE SYSTEM WAS MODIFIED ***** 287718 inodes used (44.81%) 2326 non-contiguous files (0.8%) 98 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 9776/113/0 2387772 blocks used (93.28%) 0 bad blocks 2 large files 231158 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 -------- 290682 files root@rescue:~# fsck -yvf /dev/md2 fsck from util-linux-ng 2.17.2 e2fsck 1.41.12 (17-May-2010) /home: recovering journal 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 The system is going down for reboot NOW!et (pts/1) (Thu Jul 12 09:47:37 2012) root@rescue:~# Connection to 91.121.220.185 closed by remote host. Connection to 91.121.220.185 closed.

Then, reconnect, and:

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

But when I do in the main root partition... I mean cd, I get:

du -h --max-depth=1 8,0K ./.pki 16K ./.ssh 48K ./.subversion 516K .

Same at all...

Any advice, please!!

error

1. it looks like you've got 2 physical disks: sda, sdb.
Each of these is split into 3 partitions
a) root ie '/'
b) /home
c) swap

2. '/' is 99% full (~10Gb partition)
/home is 1% full (~100GB partition)

3. it appears that these 2 disks are probably mirrored (RAID1). Normally these would start with /dev/md0, but it appears you have /dev/md1 ('/') & /dev/md2 (/home) defined.
I think(?) your swap partitions are not mirrored
Check by running

cat /proc/mdstat
mdadm --detail /dev/md1
mdadm --detail /dev/md2

4. first you need to check the disk layouts as above & also check /etc/fstab.
It appears, as previously noted, that you have multiple bind-mount points on the same partitions, which you almost definitely don't need; booth for 'root' and for 'named'.

5. once you've got a clear idea of the layout, I'd recommend coming up with a simpler layout and probably moving some stuff eg /var off of the root partition.


6. Basically, you've got enough total disk space, but it's laid out wrong.

Thank you Chris for your prompt.
It's really hard that i got this just yesterday in the evening, after that we lose and damage large number of data, and had to recover...etc
The issue come from the installation, as I had been moved this server from another povider to ovh, where in the installation process they don't offer any personalisation for the partitions, so it's just a standard install...

No, I just recoverd, and have a new installation, which i just put in production this morning, and having the following:

# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty] md1 : active raid1 sdb1[1] sda1[0] 10238912 blocks [2/2] [UU] md2 : active raid1 sdb2[1] sda2[0] 106451904 blocks [2/2] [UU] unused devices: <none> [root@xxxxx ~]# mdadm --detail /dev/md1 /dev/md1: Version : 0.90 Creation Time : Thu Jul 12 20:59:46 2012 Raid Level : raid1 Array Size : 10238912 (9.76 GiB 10.48 GB) Used Dev Size : 10238912 (9.76 GiB 10.48 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Fri Jul 13 12:21:06 2012 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : a6e66c18:bd14dc8b:a4d2adc2:26fd5302 Events : 0.17 Number Major Minor RaidDevice State 0 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1 [root@xxxx ~]# mdadm --detail /dev/md2 /dev/md2: Version : 0.90 Creation Time : Thu Jul 12 20:59:52 2012 Raid Level : raid1 Array Size : 106451904 (101.52 GiB 109.01 GB) Used Dev Size : 106451904 (101.52 GiB 109.01 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 2 Persistence : Superblock is persistent Update Time : Fri Jul 13 12:21:09 2012 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : 7accdf33:02185b1e:a4d2adc2:26fd5302 Events : 0.13 Number Major Minor RaidDevice State 0 8 2 0 active sync /dev/sda2 1 8 18 1 active sync /dev/sdb2

And my fstab is this:

# <file system> <mount point> <type> <options> <dump> <pass> /dev/md1 / ext3 errors=remount-ro 0 1 /dev/md2 /home ext3 defaults 1 2 /dev/sda3 swap swap defaults 0 0 /dev/sdb3 swap swap defaults 0 0

So, i had to move all my personal data, webs, and others to the home directory, instead of the html directory, to keep the space to the system, and get it runing, where now I have:

df -h S.ficheros Size Used Avail Use% Montado en rootfs 9,7G 6,8G 2,5G 73% / /dev/root 9,7G 6,8G 2,5G 73% / none 7,8G 404K 7,8G 1% /dev /dev/md2 101G 2,6G 94G 3% /home

So, even, 73% of the storage for the system is reasonable, but I was thinking to resize the md2 partition, but no idea if this may damage again the files, or if there's any risk in runing such as task, or what I should do?

Regards,