Re: [OmniOS-discuss] panic: bd_strategy after new loader installed
On Thu, Jun 01, 2017 at 01:01:49PM -0700, Paul B. Henson wrote: > > From: Geoff Nordli > > Sent: Tuesday, May 30, 2017 7:57 PM > > > > Right, it will not boot after upgrading to the new loader; even if the > > 4K disks are not part of the rpool. > > Yikes 8-/, I'm glad I hadn't got around to updating; my data pool consists > of 13 WD Red 3TB drives which are 4K native. I'm surprised this deficiency > wasn't noticed during development or testing, aren't 4K native drives fairly > common nowadays? I deployed my pool back in 2009. WAIT A MINUTE. I thought it wasn't 4k, but "4K" that actually had more bytes on them (some sort of T.10 thing). I'm on the road right now, but I'm pretty sure I have 4k data disks and I'm on 022 + loader Just Fine (TM). Here's the relevant mail: http://lists.omniti.com/pipermail/omnios-discuss/2017-May/008906.html I can confirm/deny this when I get home. Dan ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] panic: bd_strategy after new loader installed
> From: Geoff Nordli > Sent: Tuesday, May 30, 2017 7:57 PM > > Right, it will not boot after upgrading to the new loader; even if the > 4K disks are not part of the rpool. Yikes 8-/, I'm glad I hadn't got around to updating; my data pool consists of 13 WD Red 3TB drives which are 4K native. I'm surprised this deficiency wasn't noticed during development or testing, aren't 4K native drives fairly common nowadays? I deployed my pool back in 2009. Hmm, fortunately, it looks like you can stick with grub: https://omnios.omniti.com/wiki.php/BSDLoader So until the bug you referenced is fixed upstream and back ported to r151022 (if it ever is, given the current instability of maintenance ), people with 4K drives will need to be sure to *not* migrate to loader. Perhaps somebody with privs to update the wiki would be kind enough to put a large bold warning on the release notes to make sure no one else gets themselves in the position of a non-bootable system? Hmm, wait, I think I have wiki edit privs... Yup, warning added. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] is zil mirrored within pool
On Thu, 1 Jun 2017, Artem Penner wrote: are *zfs intent log* data will be striped across all disk in pool without redundancy? If hard drive fail and this cause kernel panic, can I lose my data? You will not lose data if sufficient hard drives are working properly. That is the purpose of zfs and its intent log as well. Normally hard drive failures do not cause kernel panics if sufficient redundancy remains. If the kernel panics for some other reason (e.g. RAM failure or a software bug), it is possible for zfs corruption or data loss to occur since zfs is based on software and zfs stores quite a lot of data in cache. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] is zil mirrored within pool
are *zfs intent log* data will be striped across all disk in pool without redundancy? If hard drive fail and this cause kernel panic, can I lose my data? чт, 1 июн. 2017 г. в 17:45, Rafael Pardinas: > By default, ZFS stores the ZIL in the pool with all the data, so yes. > > On Thu, 1 Jun 2017 at 15:39 Artem Penner wrote: > >> Hi, if I hadn't separate log device, is zfs intent log is mirrored inside >> raidz pool? >> >> ___ >> OmniOS-discuss mailing list >> OmniOS-discuss@lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss >> > ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] To the OmniOS Community
On Thu, 1 Jun 2017, qutic development wrote: ; Hi Theo, ; ; that is a word! ; ; > I was hoping not to be the first, but I will attempt to lead by example. I'll pledge my time to do required security package publications on 014 and 022. As security issues with packages in core arise, I will update the build system, re-roll the packages and publish them. ; ; There are a few security related releases since Dan left: ; ; - sudo ; - openssl (bugfix) ; - openjdk 7 ; - bind 9 ; - ldap ; ; As 014 and 022 have signed packages, nobody else than OmniTi can build packages for these, right? I have added a pull request for the openssl update to omnios-build, just to see if anyone was picking these up. https://github.com/omniti-labs/omnios-build/pull/105 I've updated my local omnios r22 package mirror and updated our servers too but I've obviously had to disable package signatures. Seems we don't currently have a maintained package repository although people (including me) have volunteered to maintain it. Andy -- Citrus IT Limited | +44 (0)870 199 8000 | enquir...@citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss