Re: [OpenIndiana-discuss] Revive retired disks with data sets on them with vitual OI
Jonathan Adams t12nsloo...@gmail.com writes: Probably not the most reliable, but definitely the easiest, way to get access to your data is to use USB disks because VirtualBox allows direct USB passthrough. My boss uses OpenSolaris with USB drives to get access to the ZFS pool running on his Linux system. [...] There are actually 3 pair of disks that were set up in mirrored zpools: 2 @ 500 gb (Older IDE) 2 @ 500 gb (oldish sata) 2 @ 750 gb (slightly newer sata) [...] Richard Elling richard.ell...@richardelling.com writes: On Mar 26, 2012, at 12:34 PM, Jonathan Adams wrote: Probably not the most reliable, but definitely the easiest, way to get access to your data is to use USB disks because VirtualBox allows direct USB passthrough. My boss uses OpenSolaris with USB drives to get access to the ZFS pool running on his Linux system. USB drives tend to ignore cache flush commands, which can appear as unreliable disks. Shouldn't be much of a problem if you rarely plug them. Is the kind of size (3.5 TB) and scale mentioned above available in usb drives? Any chance of mirrored pairs as described? ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Dependency problem on pkg:/service/network/dns/bind
We're running our server quite happily on OI, currently on entire@0.5.11,5.11-0.151.1 Trying to install service/network/dns/bind always creates a new BE. Poking around the dependencies I see it depends on pkgs from 0.151.1.2! pkg contents -m -r service/network/dns/bind@9.6.2.2,5.11-0.151.1 | egrep '^depend' depend fmri=consolidation/sfw/sfw-incorporation type=require depend fmri=network/dns/bind@9.6.2.2-0.151.1 type=require depend fmri=library/security/openssl@0.9.8.15-0.151.1 type=require depend fmri=system/library@0.5.11-0.151.1 type=require depend fmri=library/libxml2@2.7.6-0.151.1 type=require depend fmri=library/zlib@1.2.3-0.151.1 type=require depend fmri=system/library/math@0.5.11-0.151.1 type=require depend fmri=SUNWcs@0.5.11-0.151.1 type=require depend fmri=consolidation/sfw/sfw-incorporation type=require depend fmri=network/dns/bind@9.6.2.2-0.151.1.2 type=require depend fmri=library/security/openssl@0.9.8.15-0.151.1.2 type=require depend fmri=system/library@0.5.11-0.151.1.2 type=require depend fmri=library/libxml2@2.7.6-0.151.1.2 type=require depend fmri=library/zlib@1.2.3-0.151.1.2 type=require depend fmri=system/library/math@0.5.11-0.151.1.2 type=require depend fmri=SUNWcs@0.5.11-0.151.1.2 type=require (everything from sfw-incorporation down) I think that makes it impossible to install without essentially updating the whole machine to 0.151.1.2 and rebooting. That seems unreasonable just to get named! Am I reading this wrong? Is there a workaround? Chris ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Dependency problem on pkg:/service/network/dns/bind
On Fri, Mar 30, 2012 at 7:07 AM, Chris Ridd chrisr...@mac.com wrote: We're running our server quite happily on OI, currently on entire@0.5.11,5.11-0.151.1 Trying to install service/network/dns/bind always creates a new BE. Poking around the dependencies I see it depends on pkgs from 0.151.1.2! The original repository for 0.151 was in /dev. When the next prestable came out, packages were put in /prestable, so that people like you could either stay with their current system and fetch things from /dev, or change their repository to point to /prestable and update their system. For some reason, a decision was made to put the next prestable back in /dev. Since that is where your repository is pointing, it will try to get the most recent version of bind from there. I would suppose that to ease testing all packages/dependencies must be at a specific release version (not sure if anything has actually changed in every single package from bind through zlib). Am I reading this wrong? Is there a workaround? I'm not sure if the repository got overwritten, or simply newer packages got added without removing the old ones. If the latter, there may be a way to force the installation of the older version of bind, the one corresponding to the rest of the system. (Or if there still exists a mirror of the original repository somewhere...) Jan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Dependency problem on pkg:/service/network/dns/bind
On 30 Mar 2012, at 15:19, Jan Owoc wrote: On Fri, Mar 30, 2012 at 7:07 AM, Chris Ridd chrisr...@mac.com wrote: We're running our server quite happily on OI, currently on entire@0.5.11,5.11-0.151.1 Trying to install service/network/dns/bind always creates a new BE. Poking around the dependencies I see it depends on pkgs from 0.151.1.2! The original repository for 0.151 was in /dev. When the next prestable Yes, my publisher's origin is still pkg.openindiana.org/dev. came out, packages were put in /prestable, so that people like you could either stay with their current system and fetch things from /dev, or change their repository to point to /prestable and update their system. For some reason, a decision was made to put the next prestable back in /dev. Since that is where your repository is pointing, it will try to get the most recent version of bind from there. I would suppose that to ease testing all packages/dependencies must be at a specific release version (not sure if anything has actually changed in every single package from bind through zlib). Rewriting history in a repository seems like a bad idea! Am I reading this wrong? Is there a workaround? I'm not sure if the repository got overwritten, or simply newer packages got added without removing the old ones. If the latter, there may be a way to force the installation of the older version of bind, the one corresponding to the rest of the system. (Or if there still exists a mirror of the original repository somewhere...) Updating to 0.151.1.2 from /dev and rebooting is an option. Or should I be changing my publisher to something more reliable? Chris ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Revive retired disks with data sets on them with vitual OI
On Mar 30, 2012, at 2:01 AM, Harry Putnam wrote: Richard Elling richard.ell...@richardelling.com writes: On Mar 26, 2012, at 12:34 PM, Jonathan Adams wrote: Probably not the most reliable, but definitely the easiest, way to get access to your data is to use USB disks because VirtualBox allows direct USB passthrough. My boss uses OpenSolaris with USB drives to get access to the ZFS pool running on his Linux system. USB drives tend to ignore cache flush commands, which can appear as unreliable disks. Shouldn't be much of a problem if you rarely plug them. Is the kind of size (3.5 TB) and scale mentioned above available in usb drives? Any chance of mirrored pairs as described? Something like: http://sharecenter.dlink.com/ShareCenter_Meet_The_Family Kinda makes DIY look expensive. -- richard -- DTrace Conference, April 3, 2012, http://wiki.smartos.org/display/DOC/dtrace.conf ZFS Performance and Training richard.ell...@richardelling.com +1-760-896-4422 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Dependency problem on pkg:/service/network/dns/bind
On 30/03/2012 16:08, Jan Owoc wrote: On Fri, Mar 30, 2012 at 8:55 AM, Chris Riddchrisr...@mac.com wrote: Am I reading this wrong? Is there a workaround? I'm not sure if the repository got overwritten, or simply newer packages got added without removing the old ones. If the latter, there may be a way to force the installation of the older version of bind, the one corresponding to the rest of the system. (Or if there still exists a mirror of the original repository somewhere...) Updating to 0.151.1.2 from /dev and rebooting is an option. Or should I be changing my publisher to something more reliable? There is (currently) no stable release of OI. Your choices are to stay with whatever system you happened to install (it works!), or update to the most recent pre-stable release. I'm unable to find anything newer/more stable than this: http://wiki.openindiana.org/oi/oi_151a_prestable1+Release+Notes After refreshing the repositories with pkg refresh --full, you may or may not need to first update pkg (pkg install -v pkg:/package/pkg) before doing the full system upgrade (I did when going from 151a to 151a-pre0). Jan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss There was no history rewriting (whatever that is supposed to mean), later versions are added to the repo with nothing being taken away. The /dev repo is the most reliable for OI currently. If you don't want to update then use: pkg install blah@0.5.11-0.151.1.1 JT ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Dependency problem on pkg:/service/network/dns/bind
On 30 Mar 2012, at 19:17, Jon Tibble me...@btinternet.com wrote: There was no history rewriting (whatever that is supposed to mean), That is just a guess as to what happened to apparently break these dependencies. Forget this bit - do you think the deps on the pkg I mentioned are right? How can a .151.1 package depend on a .151.1.2 package? If you don't want to update then use: pkg install blah@0.5.11-0.151.1.1 I tried that before and it doesn't work for the package I mentioned (.151.1) because it seems to depend on things with later build numbers. See the list of deps I posted originally. I'll run a pkg install -nv if you'd like... Chris ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
