Re: [zfs-discuss] booting from ashift=12 pool..
On Fri, Jul 29, 2011 at 01:04:49AM -0400, Daniel Carosone wrote: > .. evidently doesn't work. GRUB reboots the machine moments after > loading stage2, and doesn't recognise the fstype when examining the > disk loaded from an alernate source. > > This is with SX-151. Here's hoping a future version (with grub2?) > resolves this, as well as lets us boot from raidz. > > Just a note for the archives in case it helps someone else get back > the afternoon I just burnt. I've noticed this behaviour this morning and have been debugging it since. I found out that, for some unknown reason, grub fails to get the disk geometry, assumes 0 sectors/track and then does a divide-by-zero. I don't think this is a zfs issue. Hans -- %SYSTEM-F-ANARCHISM, The operating system has been overthrown ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] booting from ashift=12 pool..
On Fri, Jul 29, 2011 at 10:22:27AM -0400, Fajar A. Nugraha wrote: > On Fri, Jul 29, 2011 at 4:57 PM, Hans Rosenfeld > wrote: > > I've noticed this behaviour this morning and have been debugging it > > since. I found out that, for some unknown reason, grub fails to get the > > disk geometry, assumes 0 sectors/track and then does a divide-by-zero. > > > > I don't think this is a zfs issue. > > If the problem is on zfs code in grub/grub2, then it should be zfs issue, > right? I thought that due to the geometry stuff the zfs code never runs, but after some more debugging I know that was wrong. These are in fact two unrelated problems. > Anyway, for comparison purposes, with ubuntu + grub2 + zfsonlinux > (which can force ashift at pool creation time) + zfs root, grub2 > won't even install on pools with ashift=12, while it works just fine > with ashift=9. There were also booting problems if you've scrubbed > rpool. > > Does zfs code for grub/grub2 also depend on Oracle releasing updates, > or is it simply a matter of no one with enough skill have looked into > it yet? I'm working on a patch for grub that fixes the ashift=12 issue. I'm probably not going to fix the div-by-zero reboot. Hans -- %SYSTEM-F-ANARCHISM, The operating system has been overthrown ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] booting from ashift=12 pool..
On Fri, Jul 29, 2011 at 04:36:33PM +0200, Hans Rosenfeld wrote: > > Does zfs code for grub/grub2 also depend on Oracle releasing > > updates, > > or is it simply a matter of no one with enough skill have looked > > into > > it yet? > > I'm working on a patch for grub that fixes the ashift=12 issue. I'm > probably not going to fix the div-by-zero reboot. If you want to try it, the patch can be found at http://cr.illumos.org/view/6qc99xkh/illumos-1303-webrev/illumos-1303-webrev.patch Hans -- %SYSTEM-F-ANARCHISM, The operating system has been overthrown ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] booting from ashift=12 pool..
On Mon, Aug 01, 2011 at 11:22:36AM +1000, Daniel Carosone wrote: > > If you want to try it, the patch can be found at > > http://cr.illumos.org/view/6qc99xkh/illumos-1303-webrev/illumos-1303-webrev.patch > > Any chance of providing an alternate stage1/stage2 binary I can feed > to installgrub? When you're ready.. There is already an updated patch that also works with mirrored pools: http://cr.illumos.org/view/77bat2me/illumos-1303-webrev-2/illumos-1303-webrev-2.patch We track this issue at https://www.illumos.org/issues/1303, so if I have to update the patch again, you can find it there. Hans -- %SYSTEM-F-ANARCHISM, The operating system has been overthrown ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] booting from ashift=12 pool..
Hi, On Mon, Sep 05, 2011 at 02:18:48AM -0400, Daniel Carosone wrote: > I see via the issue tracker that there have been several updates > since, and an integration back into the main Illumos tree. How do I > go about getting hold of current boot blocks? The OpenIndiana release that was announced earlier today has the fixed boot blocks. Hans -- %SYSTEM-F-ANARCHISM, The operating system has been overthrown ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] booting from ashift=12 pool..
On Wed, Sep 14, 2011 at 07:10:21PM -0400, Daniel Carosone wrote: > Yep, saw that and have it here ready to boot and install grub. I hope > the fact that the pool itself is v31 for zfs crypto will not be a > problem.. I doubt that works. IIRC the highest supported zpool and zfs versions are hardcoded in the grub zfs code, probably to make sure that no garbage is read. > If it should be the case that the pool version is an issue running > from the OI CD, can I take the updated stage* files and use them with > the installgrub from solaris express b151? Would make no difference. You could try to get the grub source code from S11X and patch and rebuild it manually. Hans -- %SYSTEM-F-ANARCHISM, The operating system has been overthrown ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Question on 4k sectors
On Thu, Jul 19, 2012 at 02:29:38PM +0200, Hans J. Albertsson wrote: > I think the problem is with disks that are 4k organised, but report > their blocksize as 512. > > If the disk reports it's blocksize correctly as 4096, then ZFS should > not have a problem. > At least my 2TB Seagate Barracuda disks seemed to report their > blocksizes as 4096, and my zpools on those machines have ashift set to > 12, which is correct, since 2¹² = 4096 > > You cannot mix 512 and 4096 byte blocksize disks in one pool, at least > not in a mirror. All disks in a single pool should have the same blocksize. Ashift is a vdev property. As far as I know you can have several vdevs with different ashifts in one pool. Besides, it is possible to mix 512 and 4096 byte blocksizes in a mirror vdev (and likely also in other vdev configurations), if and only if you start with the 4096 byte blocksize disk. That is, you can attach 512 byte blocksize disks to ashift=12 vdevs, but you can't attach a 4096 byte blocksize disk to an ashift=9 vdev. And even that is not entirely true: some implementation of ZFS might choose to just warn about it or not care at all, while others will refuse to create or import such a pool. Hans -- %SYSTEM-F-ANARCHISM, The operating system has been overthrown ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] configure ST33000650SS with 4k advanced sector format
Hi, On Fri, Dec 07, 2012 at 08:36:46AM -0500, Christof Haemmerle wrote: > i cannot figure out how to make openindiana recognize the seagate ES.2 > SAS 3TB (ST33000650SS) as a 4k advanced sector drive. Are you sure this is an 4k sector drive? The drives manual doesn't mention anything about 4k sectors or "advanced format". Hans -- %SYSTEM-F-ANARCHISM, The operating system has been overthrown ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
