Power went out during defrag, no space left

Hi guys.

I have a ReadyNas RN104 with 2 x 4 TB drives (WD Red) running in raid.
I'm using the scheduler to automate defrag, scrub and balance. During the defrag the power went out and when it came back on, the defrag process was stopped. Before the drag I had about 1TB of space left, now after it has booted up again it said I had 132kb. I tried to do a disk balance which increased the free disk space to about 2GB.

I've SSH'ing into the NAS and tried to figure out where the space went, but I haven't been able to figure it out.

/# du -sh /
du: cannot access `/proc/8090/task/8090/fd/4': No such file or directory
du: cannot access `/proc/8090/task/8090/fdinfo/4': No such file or directory
du: cannot access `/proc/8090/fd/4': No such file or directory
du: cannot access `/proc/8090/fdinfo/4': No such file or directory
2.8T	/

/# df -H
Filesystem      Size  Used Avail Use% Mounted on
rootfs          4.0G  959M  2.9G  25% /
tmpfs            10M  4.0K   10M   1% /dev
/dev/md0        4.0G  959M  2.9G  25% /
tmpfs           248M     0  248M   0% /dev/shm
tmpfs           248M  564K  248M   1% /run
tmpfs           248M     0  248M   0% /sys/fs/cgroup
tmpfs           248M     0  248M   0% /media
/dev/md127      3.7T  3.7T  2.1G 100% /data
/dev/md127      3.7T  3.7T  2.1G 100% /apps
/dev/md127      3.7T  3.7T  2.1G 100% /home

/# df -i
Filesystem     Inodes IUsed IFree IUse% Mounted on
rootfs          65536 19181 46355   30% /
tmpfs           63410   273 63137    1% /dev
/dev/md0        65536 19181 46355   30% /
tmpfs           63410     1 63409    1% /dev/shm
tmpfs           63410   398 63012    1% /run
tmpfs           63410     4 63406    1% /sys/fs/cgroup
tmpfs           63410     1 63409    1% /media
/dev/md127          0     0     0     - /data
/dev/md127          0     0     0     - /apps
/dev/md127          0     0     0     - /home

/# dumpe2fs /dev/md127
dumpe2fs 1.42.10 (18-May-2014)
dumpe2fs: Bad magic number in super-block while trying to open /dev/md127
Couldn't find valid filesystem superblock.

/# fdisk -l

Disk /dev/mtdblock0: 1 MB, 1572864 bytes
255 heads, 63 sectors/track, 0 cylinders, total 3072 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf7ff1c18

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 131072 bytes
255 heads, 63 sectors/track, 0 cylinders, total 256 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x322e3535

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/mtdblock2: 6 MB, 6291456 bytes
255 heads, 63 sectors/track, 0 cylinders, total 12288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe1a0f004

Disk /dev/mtdblock2 doesn't contain a valid partition table

Disk /dev/mtdblock3: 4 MB, 4194304 bytes
255 heads, 63 sectors/track, 0 cylinders, total 8192 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6e907a39

Disk /dev/mtdblock3 doesn't contain a valid partition table

Disk /dev/mtdblock4: 121 MB, 121634816 bytes
255 heads, 63 sectors/track, 14 cylinders, total 237568 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mtdblock4 doesn't contain a valid partition table

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 4000.8 GB, 4000787030016 bytes
256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes
256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/md0: 4292 MB, 4292804608 bytes
2 heads, 4 sectors/track, 1048048 cylinders, total 8384384 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table

Disk /dev/md1: 536 MB, 536543232 bytes
2 heads, 4 sectors/track, 130992 cylinders, total 1047936 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md1 doesn't contain a valid partition table

Disk /dev/md127: 3995.8 GB, 3995818655744 bytes
2 heads, 4 sectors/track, 975541664 cylinders, total 7804333312 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md127 doesn't contain a valid partition table

I've experienced something like this before, but that was due to the snapshotting not working properly and keeping old snapshots even though they should have been deleted. I've disabled snapshotting for all shares and deleted all old snapshot files, so it's not the same problem again.

Any help would be greatly appreciated :)