Bugzilla – Bug 2716
Build 94 ISO install is DOA
Last modified: 2009-02-28 00:37:34 UTC
You need to log in before you can comment on or make changes to this bug.
Alan S. reported: The bld94 pkg commands are not working. It is looking for symlinks which are not correctly named: releng@bellflower:/var/pkg/state/installed$ pkg list Traceback (most recent call last): File "/usr/bin/pkg", line 1534, in ? ret = main_func() File "/usr/bin/pkg", line 1496, in main_func return list_inventory(img, pargs) File "/usr/bin/pkg", line 151, in list_inventory img.load_catalogs(progress.NullProgressTracker()) File "/usr/lib/python2.4/vendor-packages/pkg/client/image.py", line 1037, in load_catalogs self.load_catalog_cache() File "/usr/lib/python2.4/vendor-packages/pkg/client/image.py", line 993, in load_catalog_cache self.__load_pkg_states() File "/usr/lib/python2.4/vendor-packages/pkg/client/image.py", line 1113, in __load_pkg_states auth = self.installed_file_authority(path) File "/usr/lib/python2.4/vendor-packages/pkg/client/image.py", line 580, in installed_file_authority f = file(filepath, "r+") IOError: [Errno 2] No such file or directory: '/var/pkg/state/installed/BRCMbnx@0.5.11%2C5.11-0.94%3A20080721T210721Z' The pathname above is a symbolic link to: /var/pkg/pkg/BRCMbnx/0.5.11%2C5.11-0.94%3A20080721T210721Zinstalled But the actual path is: /var/pkg/pkg/BRCMbnx/0.5.11%2C5.11-0.94%3A20080721T210721Z/installed The "/" before the "installed" file is missing. Subsequent diagnosis indicates that this is likely a result of running into limits in the file names used on the hsfs generated by mkisofs, into which we move most of the /var/pkg data in order to keep the root archive size moderately manageable. Suggested fix at this point is to move this data to a compressed UFS archive, which will eliminate any chance of filesystem-related incompatibility between the live CD and an installed system.
Implementing the change to move all the IPS related data in var/pkg into a compressed UFS archive. This compress UFS archive will be named pkg.zlib to be stored / in the Live CD. This will be mounted to /mnt/pkg when the Live CD is booted up. From the root archive, most of the files in var/pkg will be symlinks to this archive. When users choose to install the Live CD, these symlinks will be converted appropriately back to original files.
Changes in DC gate: changeset: 101:eb5c7bfafb6 Changes in Slim gate: changeset: 181:b1b2f06da765
Now that the root cause for the broken symlinks on hsfs is known (see bug 5385), would it make sense to revert the workarounds that have been added because of the hsfs bug (of cause after hsfs is fixed in onnv-gate)?
(In reply to comment #3) > Now that the root cause for the broken symlinks on hsfs is known > (see bug 5385), would it make sense to revert the workarounds > that have been added because of the hsfs bug (of cause after hsfs > is fixed in onnv-gate)? Yes, I think it would make sense to do that.