On Mon, 2007-04-30 at 16:53 -0700, Darren Dunham wrote:
> > > zpool list doesn't reflect pool usage stats instantly. Why?
> >
> > This is no different to how UFS behaves.
>
> It is different now (although I spent about 5 minutes looking for an old
> bug that would point to *when* the UFS change w
> > zpool list doesn't reflect pool usage stats instantly. Why?
>
> This is no different to how UFS behaves.
It is different now (although I spent about 5 minutes looking for an old
bug that would point to *when* the UFS change went in, I wasn't able to
find one).
> If you rm a file, this uses t
zpool list doesn't reflect pool usage stats instantly. Why?
This is no different to how UFS behaves.
If you rm a file, this uses the system call unlink(2) to do the work which is
asynchronous.
In other words, unlink(2) almost immediately returns a successful return code to
rm (which can the
> zpool list doesn't reflect pool usage stats instantly. Why?
>
> # ls -l
> total 209769330
> -rw--T 1 root root 107374182400 Apr 30 14:28 deleteme
>
> # zpool list
> NAMESIZEUSED AVAILCAP HEALTH ALTROOT
> wo136G100G 36.0G
Hi,
OS : Solaris 10 11/06
zpool list doesn't reflect pool usage stats instantly. Why?
# ls -l
total 209769330
-rw--T 1 root root 107374182400 Apr 30 14:28 deleteme
# zpool list
NAMESIZEUSED AVAILCAP HEALTH ALTROOT
wo136G10
