Re: [OpenIndiana-discuss] [oi-dev] [HEADSUP] OpenIndiana Hipster default repository URL has changed
On 14 January 2015 16:33:34 CET, Alexander Pyhalov a...@rsu.ru wrote: Hello. This message concerns OI Hipster users. We have just moved default package repository from http://pkg.openindiana.org/hipster-2014.1/ to http://pkg.openindiana.org/hipster-2015 and bumped branch version from 2014.1.3 to 2015.0.0. This was necessary to decrease repository size and speedup operations of IPS tools. To make your system use new repository, do the following. 1) Make sure that you are running the latest bits # pkg refresh # pkg update 2) Reboot to new BE if necessary # init 6 3) Change openindiana.org publisher to new one # pkg set-publisher -G http://pkg.openindiana.org/hipster-2014.1/ -g http://pkg.openindiana.org/hipster-2015 openindiana.org 4) Update your system # pkg update 5) Reboot to new BE # init 6 6) Check that you have updated osnet-incorporation installed # pkg info osnet-incorporation ### Should report version = 2015.0.0.14851 If you are using custom illumos-gate builds, don't forget to change PKGVERS_BRANCH to 2015.X.0.0. Thanks, worked for my laptop as well, with its split-root configuration (and thus upfating in the pre-created ABE, as automated by scripts on the Split-Root installation). I had to manually intervene into the documented procedure though: * created/mounted the BE with beadm-clone.sh (applies custom dataset attrs like greater compression or quotas) * set the new publisher url as Alexander wrote, but prefixed with the altroot (pkg -R /a set-publisher...) * updated the ABE etc. following thr documented procedure So I verified it is still relevant ;) Thanks, Jim -- Typos courtesy of K-9 Mail on my Samsung Android ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] rpool defragmentation
# zpool list NAME SIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT rpool 68G 49.5G 18.5G -50%72% 1.00x ONLINE - users 928G 72.4G 856G - 1% 7% 1.00x ONLINE - # zfs list NAMEUSED AVAIL REFER MOUNTPOINT rpool 48.9G 16.9G82K /rpool rpool/ROOT 44.9G 16.9G22K legacy rpool/ROOT/hipster-17 44.9G 16.9G 34.9G / rpool/dump 1.97G 16.9G 1.97G - rpool/export 32K 16.9G32K /export rpool/swap 2.01G 16.9G 2.01G - users 72.4G 827G 72.3G /export/home How does one defragment this? I thought about creating a new BE and then sending the current BE to it, but there doesn't seem to be enough room. Gary ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] GNOME 2.32.1 in Hipster
True, if we consider it from our 'full-fledged' GNOME 2.32.1 desktop environment deployment perspective. But, the basic GNOME 2.32.1 desktop environment is there. Some work exists to finish porting the otherpackages - but nothing major. Also, the GNOME 2.32.1 'platform' foundation is complete. Meaning, all GNOME2-based applications currentlyexisting are portable to OI with minimal fuss (aka non-kernel related). See you in two weeks! ~ Ken On Thursday, January 15, 2015 9:01 PM, Alexander Pyhalov a...@rsu.ru wrote: Hello. ken mays via openindiana-discuss писал 16.01.2015 02:02: Hello, We are now at GNOME 2.32.1 in Hipster. Sorry, but this is an exaggeration. We have updated a lot of Gnome components to Gnome 2.32 and chasing the goal to ship Gnome 2.32, but still are not there. Just do pkg list |grep gnome|grep 151.1.8 - and you'll see that there are still a lot og Gnome 2.30 components, for example, accessibility libraries, gconf-editor, gnome-audio and so on. --- System Administrator of Southern Federal University Computer Center ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] rpool defragmentation
On 01/16/15 03:47 PM, Gary Gendel wrote: On 01/16/2015 10:22 AM, Andrew Gabriel wrote: On 01/16/15 02:37 PM, Gary Gendel wrote: # zpool list NAME SIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT rpool 68G 49.5G 18.5G -50%72% 1.00x ONLINE - users 928G 72.4G 856G - 1% 7% 1.00x ONLINE - # zfs list NAMEUSED AVAIL REFER MOUNTPOINT rpool 48.9G 16.9G82K /rpool rpool/ROOT 44.9G 16.9G22K legacy rpool/ROOT/hipster-17 44.9G 16.9G 34.9G / rpool/dump 1.97G 16.9G 1.97G - rpool/export 32K 16.9G32K /export rpool/swap 2.01G 16.9G 2.01G - users 72.4G 827G 72.3G /export/home How does one defragment this? I presume you are referring to rpool, and not users? What makes you think you need to? What do you use the root filesystem for? I thought about creating a new BE and then sending the current BE to it, but there doesn't seem to be enough room. Since rpool can only be either a single disk or a mirror, the easiest way to defrag it is to attach another mirror side and let it resilver. The new mirror side will be defragged. Make sure the new disk is bootable (has grub etc on it), and then zpool split off the old disk. It would be a good opportunity to move to a bigger rpool disk too. Yes, this is the rpool and is mirrored. Would resilvering really defragment it? Yes, space is allocated afresh when resilvering (which is a significant difference from traditional RAID). I figured that with this high a fragmentation there would be some penalty in memory consumption and possible disk access. The FRAG figure there is a measure of free space fragmentation in the form of how many metaslabs have no blocks of space bigger than 8Mbyte free, and also takes into account how small their biggest free block is. 50% FRAG can mean something between the following two extremes: 1. half the metaslabs being completely fragmented (no blocks bigger than 1kbyte available) and half the metaslabs having 16Mbyte blocks, or 2. all the metaslabs having 128Kbyte free blocks available. I wouldn't worry about 50% on an rpool, although I haven't done any detailed performance metrics since the metaslab histograms appeared. Specifically, FRAG does not tell you anything about how fragmented the layout of your existing data is on the disk, only how easily zfs can find free space for you to write new data into. The rpool has gotten worse slowly. This started with somewhere around OpenSolaris SNV_124 when the disk requirements were much smaller and has gone though 100s of updates since then. I'm hanging on to this SunFire v20z until I can figure out a cheap, less power hungry replacement. It replaced my Sparc SunFire 150 that started running OpenSolaris around SNV_62! In my SOHO, the V20z runs the network: * Firewall and router WAN to LAN. *** It would be nice to get a DHCPv6 PD client working so I don't have to have a 4-6 tunnel. * Web server (Web pages, Wiki, Owncloud, etc.) * File server (user pool and archive pool). * Archive server. * Mail server * DCHP 4 and 6 server. * Software testing platform. Most of the time this machine is lightly loaded. Only when software testing goes on does it ever sweat. It's kind of a kludge setup as I have the disks off of sata cables directly from the controller to the disks in an external cabinet because of the lack of sata multiplexing. That's much better than trying to use SATA drives via port expanders! -- Andrew ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hipster 2015 x264 issue
Hi, If you are going to create a /hipster-encumbered repository can I put a request in for VLC 2.1.5, Handbrake 0.10.0 to be included ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Openoffice 4.1.3
Hi, Still having problems with Openoffice, I can not save in any openoffice format but I can save in Microsoft .doc format. I am also unable to export in PDF. Regards Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hipster 2015 x264 issue
Russell, You can get it from here:http://sfe.opencsw.org/localhostoi151a8/en/index.shtml media/vlc@2.1.5,5.11-0.0.151.1.8:20150110T173732Z ~ Ken On Friday, January 16, 2015 11:09 AM, russell str...@willows7.myzen.co.uk wrote: Hi, If you are going to create a /hipster-encumbered repository can I put a request in for VLC 2.1.5, Handbrake 0.10.0 to be included ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] rpool defragmentation
On Fri, Jan 16, 2015 at 11:47 AM, Andrew Gabriel illu...@cucumber.demon.co.uk wrote: On 01/16/15 03:47 PM, Gary Gendel wrote: On 01/16/2015 10:22 AM, Andrew Gabriel wrote: On 01/16/15 02:37 PM, Gary Gendel wrote: I thought about creating a new BE and then sending the current BE to it, but there doesn't seem to be enough room. Since rpool can only be either a single disk or a mirror, the easiest way to defrag it is to attach another mirror side and let it resilver. The new mirror side will be defragged. Make sure the new disk is bootable (has grub etc on it), and then zpool split off the old disk. It would be a good opportunity to move to a bigger rpool disk too. Yes, this is the rpool and is mirrored. Would resilvering really defragment it? Yes, space is allocated afresh when resilvering (which is a significant difference from traditional RAID). I find that surprising. Does the metadata on the older drive(s) manage to refer to the new, independent location of the blocks on the new mirror, and if so, how? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] rpool defragmentation
Timothy Coalson wrote: On Fri, Jan 16, 2015 at 11:47 AM, Andrew Gabriel illu...@cucumber.demon.co.uk wrote: On 01/16/15 03:47 PM, Gary Gendel wrote: On 01/16/2015 10:22 AM, Andrew Gabriel wrote: On 01/16/15 02:37 PM, Gary Gendel wrote: I thought about creating a new BE and then sending the current BE to it, but there doesn't seem to be enough room. Since rpool can only be either a single disk or a mirror, the easiest way to defrag it is to attach another mirror side and let it resilver. The new mirror side will be defragged. Make sure the new disk is bootable (has grub etc on it), and then zpool split off the old disk. It would be a good opportunity to move to a bigger rpool disk too. Yes, this is the rpool and is mirrored. Would resilvering really defragment it? Yes, space is allocated afresh when resilvering (which is a significant difference from traditional RAID). I find that surprising. Does the metadata on the older drive(s) manage to refer to the new, independent location of the blocks on the new mirror, and if so, how? Good question - I'm going to have to think about that. I have done the mirror side attach and old side detach a few times and got significantly better performing pool in the case of an old pool, but maybe my rationale for the reason is not correct. I haven't done it since the spacemap histograms were introduced, so I haven't seen if the spacemap is significantly less fragmented as a result. Something to try out. -- Andrew ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] rpool defragmentation
On 16 January 2015 16:22:15 CET, Andrew Gabriel illu...@cucumber.demon.co.uk wrote: On 01/16/15 02:37 PM, Gary Gendel wrote: # zpool list NAME SIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT rpool 68G 49.5G 18.5G -50%72% 1.00x ONLINE - users 928G 72.4G 856G - 1% 7% 1.00x ONLINE - # zfs list NAMEUSED AVAIL REFER MOUNTPOINT rpool 48.9G 16.9G82K /rpool rpool/ROOT 44.9G 16.9G22K legacy rpool/ROOT/hipster-17 44.9G 16.9G 34.9G / rpool/dump 1.97G 16.9G 1.97G - rpool/export 32K 16.9G32K /export rpool/swap 2.01G 16.9G 2.01G - users 72.4G 827G 72.3G /export/home How does one defragment this? I presume you are referring to rpool, and not users? What makes you think you need to? What do you use the root filesystem for? I thought about creating a new BE and then sending the current BE to it, but there doesn't seem to be enough room. Since rpool can only be either a single disk or a mirror, the easiest way to defrag it is to attach another mirror side and let it resilver. The new mirror side will be defragged. Make sure the new disk is bootable (has grub etc on it), and then zpool split off the old disk. It would be a good opportunity to move to a bigger rpool disk too. Are you sure about defragging via mirroring? I believe (from practice digging with on-disk allocation) that offsets in vdev's that comprise a mirror are the same for copies of the same block, as well as raidzN offset into the logical tlvdev divided by total number of disks would give the offset into each disk's part of the vdev to find the sector pertaining to that stripe, and remainder from such division would give the disk number formthe particular byte offset. My description may be a bit blurry so late in the night, but you get the point ;) Jim -- Typos courtesy of K-9 Mail on my Samsung Android ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
