On Oct 30, 2010, at 12:25 PM, Cuyler Dingwell wrote:
It would have been nice if performance didn't take a nose dive when nearing
(and not even at) capacity. In my case I would have preferred if the
necessary space was reserved and I got a space issue before degrading to the
point of
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
On Mon, Oct 25, 2010 at 2:46 AM, Cuyler Dingwell cuy...@gmail.com wrote:
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 Mon, Oct 25, 2010 at 4:57 PM, Cuyler Dingwell cuy...@gmail.com wrote:
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).
--
I'm just stabbing
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
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
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
