On 08/23/11 10:48, Chris Quenelle wrote:
I'm seeing pkg update get wedged on my system. This is on build 171. When I use the 171 pkg to update my old 170 BE, I get the same hang (at least a similar read/seek loop). llseek(6, 0x006AF086, SEEK_SET) = 7008390 read(6, " p k g : / / s o l a r i".., 131072) = 131072 llseek(6, 0x01341482, SEEK_SET) = 0x01341482 read(6, " p k g : / / s o l a r i".., 131072) = 131072 llseek(6, 0x012E7680, SEEK_SET) = 0x012E7680 read(6, " p k g : / / s o l a r i".., 131072) = 131072 llseek(6, 0x007E60D2, SEEK_SET) = 8282322 read(6, " p k g : / / s o l a r i".., 131072) = 131072 llseek(6, 0x0125EFAC, SEEK_SET) = 0x0125EFAC read(6, " p k g : / / s o l a r i".., 131072) = 131072 llseek(6, 0x0159D632, SEEK_SET) = 0x0159D632 read(6, " p k g : / / s o l a r i".., 131072) = 131072 llseek(6, 0x00B6ED9C, SEEK_SET) = 11988380 read(6, " p k g : / / s o l a r i".., 131072) = 131072 llseek(6, 0x016368CF, SEEK_SET) = 0x016368CF Is this a known bug? I can supply the host and admin password if anyone wants to investigate it. I'll keep the BE around. But now I'm going to try booting back to 170 and upgrading to 172 from there.
I doubt it's actually "hung", every time I've looked at this in the past it's simply been the conflict checking logic seeking around the action.offset files. On some systems, this can take some time since it's highly dependent on how many packages you have installed and how many actions are in those packages.
If you 'pstack' the process, that would give a better idea of where it's working at.
-Shawn _______________________________________________ pkg-discuss mailing list pkg-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
