On 08/17/11 15:53, Jack Schwartz wrote:
Hi everyone.
I have a virgin B170 BE and am trying to update a clone of it using pkg
-R. Things seem to progress for a few minutes (in that the "Creating
Plan" spinner whirls), but then the spinner stops and the disk light
goes on solid. When I do a pfiles on the process, the only file activity
is for
var/pkg/actions.stripped.
Changes to the offset of that file seem to indicate that the process is
stuck in a loop, as it doesn't continuously increase as if the process
is reading the file sequentially. At this point, the process has been
running for about 20 minutes in this state.
Anyone else seen this problem? I couldn't find a bug filed for it,
looking for "actions.stripped" and haven't noticed anything recent about
it on this alias. Did I miss it?
In case this is a new issue reported, I can easily demo this to anyone
in SCA. I'm also happy to file a bug.
It's not an infinite loop, it will finish, but it can take a while on
some systems (30 minutes is not unexpected in some cases).
There are lots of conflict checks going on and it will seek back and
forth through the actions files as it process them.
It does this to avoid increased memory usage at the cost of increased I/O.
On my system an update takes much less time, but I don't have
redistributable installed, and I'm not running on SPARC.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
