Disc is full and now i cant even copy my data, disc went to 800kb

[tihizor]

Okey, first of all i knew i screwd up. And i dont have any backup (Misstake 1)

I have a one disc setup that was encrypted (Misstake 2), using FreeNAS-9.2.0-RELEASE-x64 (ab098f4). I filled the disc completly (Misstake3). I bought 2 more discs to make proper set-up.

I turned of the computer inserted one disc and it worked great. But the "old" full disc went to 800 kb like the users in this post experience (Misstake4);
https://forums.freenas.org/index.php?threads/lost-files-disk-size.14570/

output from zpool status, zpool import and mount -l can be found here;
http://pastebin.com/qFvTy3mq

Ís there anyhing i can do to try to copy my data or should i just forget about it and start over?

 

[Robert Trevellyan]

I turned of the computer inserted one disc and it worked great.

Please clarify exactly what you did.

Your zpool status appears to show that your pool is functioning.

What is the exact problem you're having?

Please post full details per the forum rules.

 

[tihizor]

Sorry if i was unclear.

When i connected my second drive i made another pool, so now there was two pools. After that i restarted the computer and when unlocking the old drive i was faced with this;

http://imgur.com/1L9ue1d

The drive is a 3 tb wd red.

After that i could not access it. I have tried to detatch and auto-import the volume but i get the same problem.

My setup is a Hp microsever N40l
http://n40l.wikia.com/wiki/HP_MicroServer_N40L_Wiki

Is there any other information i can give you that could help?

Thanks for your patience.

 

[Robert Trevellyan]

Your goal should be to free some space on the full pool, which you may be able to do using the command-line echo trick referenced in this thread (linked from the one you referenced). ZFS needs free space for every operation, which is why a completely full pool is such a problem.

When i connected my second drive i made another pool, so now there was two pools.

If you had striped the two drives together, you would have created space in the pool, but at the expense of halving the reliability. Actually, you could still try this, assuming you didn't put anything on the new pool. Just destroy it, wiping the drive in the process, then add it to the existing pool by selecting it as the "volume to extend".

When you eventually solve this problem (or give up and start over), build a pool with some redundancy.