condensing!!!!!

[patraff]

Apologies to all.
I am not very conversant with linux or freenas.
My problem is.
I have a HP Proliant microserver with 16gb memory on board.
I have 4 disk drives of 2Tb running in a 2 x 2 raid sort of setup (here I am drawing on memory from setup by son in law IT geek bloke).
Everything was going hunky dory for a number of years until trouble struck.
I had to replace a hard drive - errors showing (freenas 11.1).
So I thought - Ok I'll just transfer all my files onto a large Tb hard drive. AARrgh smb no longer worked. It seems that I went to do this we had a cracker storm and there was power surges and electricity bits flying everywhere. The end result was the thumb drive running freenas was dead.
So - I thought I would replace the drive, burn the new freenas 11.2 U6 and away we go. Well sort of.
11.2 booted - allowed me to load the new drive, import the pool, showed all disks online - albeit with no space left!!! and THEN
I am now stuck in a condensing nightmare. The microserver has been cranking now for over two weeks.
It shows on the screen the following line:
condensing: txg (sequence of 8 numbers), msp[2,3 numbers] 0xfffff(then varying number letter combos totalling 11), vdev id (0 or 1 ), spa zfs - (drive name)

The sequence of 8 numbers appears to be gradually increasing - but man when is it finished?
I've got a screen shot to possibly explain better?

Any advice? I'm thinking that I might have to go back to 11.1 on the usb drive - reboot and try and receover my data that way? (read into this the wife will kill me if 30 years of photos are gone)

Yeah yeah - I am hearing the (what about your regular backup regime????) - it is now going to be on my list.

Patrick

 

[Apollo]

I see this every time I reboot my server, so I don't think you should be worried about it. I have a powerful server but it can take a minute or two to pass this state sometimes. I think this might be something related to the cache being read.
However sticking there for 2 weeks isn't normal.

 

[patraff]

i didn't think 2 weeks is normal. As far as I can tell it is due to the issue I was having with almost zero space left on the drives. Just so I have an idea - what should the txg set of numbers get to? Is it supposed to match the allocated terabyte space?

 

[Jailer]

As far as I can tell it is due to the issue I was having with almost zero space left on the drives.

That's your issue. There's many warnings online and on this forum about filling a ZFS pool to capacity. Unless you can truncate some files to clear up some space this is likely not going to resolve itself.

 

[patraff]

Is there a guide to how to do this using ssh or something?

 

[patraff]

Before I try and go this step of using shell to delete files. The numbers slowly going up? What should be the crucial number that it gets too? if i'm not clear here I mean - if I have two 2Tb disks that are in mirrorwith two others then the total memory capacity is under 4Tb? So these TXG numbers should not exceed this?