OVH's Brilliant File Partitioning...

eastonch

 
Filesystem            Size  Used Avail Use% Mounted on
rootfs                 10G  7.0G  2.5G  74% /
/dev/root              10G  7.0G  2.5G  74% /
none                   16G  408K   16G   1% /dev
/dev/md2              102G   69G   28G  71% /home
/dev/root              10G  7.0G  2.5G  74% /var/named/chroot/etc/named
/dev/root              10G  7.0G  2.5G  74% /var/named/chroot/var/named
/dev/root              10G  7.0G  2.5G  74% /var/named/chroot/etc/named.conf
/dev/root              10G  7.0G  2.5G  74% /var/named/chroot/etc/named.rfc1912.                                                                zones
/dev/root              10G  7.0G  2.5G  74% /var/named/chroot/etc/rndc.key
/dev/root              10G  7.0G  2.5G  74% /var/named/chroot/usr/lib64/bind
/dev/root              10G  7.0G  2.5G  74% /var/named/chroot/etc/named.iscdlv.k                                                                ey
/dev/root              10G  7.0G  2.5G  74% /var/named/chroot/etc/named.root.key

What the actual hell? This has 2x 120GB Drives inside, and one seems flooded with /var/named/chroot/* crap.

I never put them there and allowed default partitioning of the drive upon the OS installation, anybody have any cautioned words before reallocating?

gsrdgrdghd

Wait, does this mean that various bind files use 7gb disk space?

Anyway did you try reinstalling with another image than the default one?

eastonch

@gsrdgrdghd

I'm confused by this now.

And yeah, it looks that way, maybe an old Disk not formatted? Its the same I have for an identical server with a normal layout.

Also,

 
[root@ns3271432 ~]# 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: 0x0003e088

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        1306    10485760+  fd  Linux raid autodetect
/dev/sda2            1306       14528   106204160   fd  Linux raid autodetect
/dev/sda3           14528       14593      526304   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: 0x000a0f99

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1        1306    10485760+  fd  Linux raid autodetect
/dev/sdb2            1306       14528   106204160   fd  Linux raid autodetect
/dev/sdb3           14528       14593      526304   82  Linux swap / Solaris

This suggests It's 'RAID'? I can't remember enabling a Raid array on this machine, and it's only Soft raid if anything, Mdadm reports empty.

I've already got software on this node, and It'd be a real shame to have to reinstall it.

AuroraZ

That is what it looks to me. That is one screwy way to do things if it turns out to be done that way. That image must specifically designed for that type of box only or something because it would not work otherwise. Doesn't make any sense to me but then again I did not make it either.

rds100

Relax. The /var/named/chroot filesystems are not real, it is just a fake (bind) mount of the / filesystem.
It is not taking up any of your space.
The /dev 16GB is not real either - it is RAM.

eastonch

@Rds100

Yeah, I've looked at it, nuked bind and now working on trying to 'unraid' this device.

I asssume the OVH Web-Panel is the easiest way to do this?

lbft

Yeah, it looks like it's partitioned as 10G root partition + the rest as /home as two Linux mdadm RAID-1 arrays (as far as I know, that's the standard OVH config).

Reinstall it from the manager, making sure to use the advanced settings or whatever it's called, to change the RAID and partitioning settings.

fly

you realize you can mount an iso in kvm and do a regular install yourself, right?