Re: [OpenIndiana-discuss] Replacing smaller rpool SSD with bigger one - best praxis
Because initially Predrag Zečević asked about ZFS with ashift 9 and ashift 12, I think this the same as https://www.illumos.org/issues/5242 "zpool won't allow attachment of larger sector drive to mirror" I was not aware of "zdb -C rpool" the value "ashift". According to: https://jrs-s.net/2018/08/17/zfs-tuning-cheat-sheet/ "Ashift tells ZFS what the underlying physical block size your disks use is. It’s in bits, so ashift=9 means 512B sectors (used by all ancient drives), ashift=12 means 4K sectors (used by most modern hard drives), and ashift=13 means 8K sectors (used by some modern SSDs)." So I think the question that is being asked here is whether you can mirror between drives of different sector size. According to https://www.illumos.org/issues/5242 which is flagged as 'open' this is not the case. Regards, David Stes - Op 8 mar 2023 om 11:55 schreef Discussion list for OpenIndiana openindiana-discuss@openindiana.org: >> On 8. Mar 2023, at 02:27, Bill Sommerfeld wrote: >> >> On 3/7/23 13:53, gea wrote: >>> I suppose a method based on mirror/clone + autoexpand will not work with >>> different ashift. >>> A disaster backup/recovery method that should work: >>> - replicate current BE to datapool via zfs send >>> (you can create daily recoverable backups while OI is running with this >>> method) >> >> If you can have all the disks cabled up at the same time, you can use the >> '-p' >> option to 'beadm create' to create a BE in a different pool; I've used this >> to >> move the root a few times (the root pool on one of my machines is currently >> named "r3”). >> > > With this method, you need to keep in mind, only dataset tree from ROOT will > be > replicated. You still need to migrate/re-create other datasets like export, > swap, dump. Also need to update dumpadm and /etc/vfstab (for swap). > > rgds, > toomas > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] libpulsecore error
On Thu, Mar 09, 2023 at 12:30:21PM -0600, Tim Mooney via openindiana-discuss wrote: > Based on your subsequent email, though, it looks like you found the > issue and it was with the binary cache file. Yes, rebuilding the gschemas.compiled file gave me a normal graphic session. Thanks for all the help. I have only left now to determine the origin of that file in OI to know why it was incorrect. The good one looks like this: -rw-r--r-- 1 root root 184871 Mar 9 11:00 gschemas.compiled Here's the bad one: -rw-r--r-- 1 root root 183112 Mar 4 18:30 gschemas.compiled-old According to the date, it came from an old BE, and was not rebuilt or installed in two updates. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] libpulsecore error
In regard to: Re: [oi-dev] libpulsecore error, Gary Mills said (at 10:44am...: On Wed, Mar 08, 2023 at 11:57:36PM -0600, Tim Mooney via oi-dev wrote: That would be my first guess. That a faulty theme is the cause now seems unlikely to me. I looked at some Mate themes on github: all of them contain keys related to geometry and colour, but nothing related to the number of items displayed or to the keyboard. I spent some time looking at themes last night, and I agree that your case probably isn't because of the theme. There are other other theme-related messages that sometimes show up in .xsession-errors, but I think you're correct that the settings-related errors you're seeing aren't coming from the theme. Based on your subsequent email, though, it looks like you found the issue and it was with the binary cache file. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure / Division of Information Technology/701-231-1076 (Voice) North Dakota State University, Fargo, ND 58105-5164 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] what do pkg install phases mean?
On 05/03/2023 18:42, Richard L. Hamilton wrote: On Mar 5, 2023, at 12:12, Peter Tribble wrote: On Sun, Mar 5, 2023 at 4:19 PM Till Wegmüller wrote: Hi IPS works on images of the OS. And it does so in an Atomic way. Speed is not the main goal. Stability is. The emphasis on performance can be seen in several areas of the design - downloading and updating just the files you need rather than whole packages; eliminating the overhead of maintaining the shared contents file. It's unfortunate that the original aim of improving performance got lost along the way. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ Yes...I wasn't badmouthing IPS, just noting that compared to e.g. well-supported > and maintained Linux distros (Kali Linux has impressed me recently), > it's slow. > In fact, most of the phases are really fast (as can be verified with pkg update -v), the competition is lost when it comes to the phase 'Building new search index', which is much slower than everything before summed up. So concentrating the effort to this phase alone could be already sufficient to speed it up a lot. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
