James C. McPherson wrote:
James C. McPherson wrote:
Jeff Bonwick wrote:
6420204 root filesystem's delete queue is not running
The workaround for this bug is to issue to following command...
# zfs set readonly=off <pool>/<fs_name>
This will cause the delete queue to start up and should flush your
queue.
Thanks for the update. James, please let us know if this solves your
problem.
yes, I've tried that several times and it didn't work for me at all.
One thing that worked a *little* bit was to set readonly=on, then
go in with mdb -kw and set the drained flag on root_pool to 0 and
then re-set readonly=off. But that only freed up about 2Gb.
Here's the next installment in the saga. I bfu'd to include Mark's
recent putback, rebooted, re-ran the "set readonly=off" op on the
root pool and root filesystem, and waited. Nothing. Nada. Not a
sausage.
Here's my root filesystem delete head:
> ::fsinfo ! head -2
VFSP FS MOUNT
fffffffffbcaa4e0 zfs /
> fffffffffbcaa4e0::print struct vfs vfs_data |::print struct zfsvfs
z_delete_head
{
z_delete_head.z_mutex = {
_opaque = [ 0 ]
}
z_delete_head.z_cv = {
_opaque = 0
}
z_delete_head.z_quiesce_cv = {
_opaque = 0
}
z_delete_head.z_drained = 0x1
z_delete_head.z_draining = 0
z_delete_head.z_thread_target = 0
z_delete_head.z_thread_count = 0
z_delete_head.z_znode_count = 0x5ce4
So we have a bunch of stuff in the in-core delete queue, but no threads
to process them. The fact that we don't have the threads is related to
the bug that Tabriz is working on.
-Mark
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss