It wasn't a completely full volume so I wasn't getting the classic 'no space'
issue.
What I did end up doing was booting OpenIndiana (build 147) which seemed tohave
more succes clearing up the space. I also set up some scripts to clear out
space slower. Deleting a 4GB file would take 1-2 min
No datasets in the pool.
As another data point I've been slowing trying to clear things out but
eventually the IO operations hang.
Pool Free Dir UsedFile Used File
...
189,238,526 44,771,026 102,413 FileName.part103.rar
189,238,526 44,668,613 102,41
Oh, a few items to highlight.
There are no snapshots - never have been on this volume.
It's not just this directory in the example - it's any directory or file. The
system was running fine up until it hit 96%. Also, a full scrub of the file
system was done (took nearly two days).
--
This mes
I have a zpool that once it hit 96% full the performance degraded horribly.
So, in order to get things better I'm trying to clear out some space. The
problem I have is after I've deleted a directory it no longer shows on the
filesystem level (ls) but the free space isn't cleared up. After a r
In the process of replacing a raidz1 of four 500GB drives with four 1.5TB
drives on the third one I ran into an interesting issue. The process was to
remove the old drive, put the new drive in and let it rebuild.
The problem was the third drive I put in had a hardware fault. That caused
both
I had a friend rebuild his system and instead of running a "zpool import" he
ran a "zpool create". Sadly this means he has an empty raidz disk now. A
"zpool import" only shows the last zpool he created. a "zpool import -D" shows
now destroyed pools for importing.
Any suggestions as to data r
