[zfs-discuss] ZFS Boot manual setup in b65
Now that I know *what*, could you perhaps explain to my *why*? I understood zpool import and export operations much as mount and unmount, like maybe some checks on the integrity of the pool and updates to some structure on the OS to maintain the imported/exported state of that pool. But now I suspect this state information is in fact maintained in the pool itself. Does this make sense? In short, once a pool is exported, it's not available/visible for live usage, even after reboot. Do you think this panic when the root pool is not visible is a bug? Should I file one? In that case, may I suggest that you add a note to the manual (http://www.opensolaris.org/os/community/zfs/boot/zfsb oot-manual/) stating that the pool should not be exported prior to booting off it? done Perhaps you could include a link to this discussion thread, too (for those who want more information). -- Doug This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] ZFS Boot manual setup in b65
On Thu, Jun 14, 2007 at 05:17:36AM -0700, Douglas Atique wrote: Do you think this panic when the root pool is not visible is a bug? Should I file one? No. There is nothing else the OS can do when it cannot mount the root filesystem. That being said, it should have a nicer message (using FMA-style knowledge articles) that tell you what's actually going wrong. There is already a bug filed against this failure mode. - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] ZFS Boot manual setup in b65
hi Doug, On Mon, 2007-06-04 at 12:25 -0700, Douglas Atique wrote: I have been trying to setup a boot ZFS filesystem since b63 and found out about bug 6553537 that was preventing boot from ZFS filesystems starting from b63. First question is whether b65 has solved the problem as was planned on the bug page. I'll verify this today (note that this was only for netinstall/pfinstall ZFS boot - manually setup ZFS boot should work fine.) Second question is: as I cannot boot successfully from a ZFS filesystem after following the ZFS Boot Manual Setup instructions (http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/) due to a panic down the call chain of vfs_mountroot, what else (other than the bug, that is) could be wrong? There's a number of things you could check: 1. Is your root pool one of the supported types (mirror or single-disk) 2. There's a bug with compression at the moment - the root pool, and the top level pool need to have compression set to off. ( 6538017 ) 3. Check that you've got an SMI label on the pool you're trying to boot from ( more at http://blogs.sun.com/timf/entry/zfs_bootable_datasets_happily_rumbling ) 4. Can you make sure your bios is booting from the correct device 5. (a bit more drastic) Can you run the script pointed to at the top of that page and setup ZFS boot that way, which could account for pilot error in following the manual steps. After that, could you verify that by changing the grub menu entry in /pool/boot/grub/menu.lst ( eg. change the title line in the ZFS boot entry, adding some random text) that you see those changes reflected in the menu that grub actually displays ? Let me know if any of these suggestions help ? cheers, tim -- Tim Foster, Sun Microsystems Inc, Solaris Engineering Ops http://blogs.sun.com/timf ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] ZFS Boot manual setup in b65
Hi Doug, On Tue, 2007-06-05 at 06:45 -0700, Douglas Atique wrote: Hi, Tim. Thanks for your hints. No problem Comments on each one follow (marked with Doug: and in blue). html mail :-/ Tim Foster [EMAIL PROTECTED] wrote: There's a number of things you could check: 1. Is your root pool one of the supported types (mirror or single-disk) Doug:I don't know. I have created a pool in a slice of my main disk. This is the layout: I assume your pool has just one slice in it. zpool status -v pool tells you the pool layout. I've a similar (but less complicated) layout on my machine here (with nv_64, admittedly) Did you installgrub the new zfs-capable version of grub onto c0d0s0? (I'm assuming you did, otherwise the bootfs keyword in the ZFS entry would fail) I haven't tried booting a ZFS dataset from grub installed on a UFS disk 2. There's a bug with compression at the moment - the root pool, and the top level pool need to have compression set to off. ( 6538017 ) Doug: I don't set compression on deliberately. Could it be on by default? Nope, I don't think so - check with zfs get compression dataset 3. Check that you've got an SMI label on the pool you're trying to boot from ( more at http://blogs.sun.com/timf/entry/zfs_bootable_datasets_happily_rumbling ) Doug: I guess it is, because of the many slices. But how could I check (read-only, non-destructively) Sounds like you've already got an SMI label if you can boot a UFS-rooted system from that disk. 4. Can you make sure your bios is booting from the correct device Doug: I'm sure. That's the only disk I have. S10 and Solaris Express from UFS all boot correctly. Okay. 5. (a bit more drastic) Can you run the script pointed to at the top of that page and setup ZFS boot that way, which could account for pilot error in following the manual steps. Doug: Haven't tried that, but I would really like to do it by hand to make sure I understand what is going on. I agree. After that, could you verify that by changing the grub menu entry in //boot/grub/menu.lst ( eg. change the title line in the ZFS boot entry, adding some random text) that you see those changes reflected in the menu that grub actually displays ? Doug: This is my ZFS entry in my menu.lst: root (hd0,0,f) bootfs snv/b65 kernel$ /boot/platform/i86pc/kernel/$ISADIR/unkx -B $ZFS-BOOTFS module$ /platform/i86pc/$ISADIR/boot_archive And this entry shows up when you boot in grub ? There's a typo in the above btw, unkx, but I'm sure that was just an error pasting into this mail (otherwise you wouldn't have even got the banner printed) Does your /etc/vfstab file on the snv/b65 ZFS filesystem contain a single entry for /, which should look like: snv/b65 - / zfs - no - and your ufs root entry should have been changed to : /dev/dsk/c1d0s0 /dev/rdsk/c1d0s0 /ufsroot ufs - yes - (or removed) Can't think of anything else that might be wrong unfortunately. cheers, tim -- Tim Foster, Sun Microsystems Inc, Solaris Engineering Ops http://blogs.sun.com/timf ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] ZFS Boot manual setup in b65
I have also been trying to figure out the best strategy regarding ZFS boot... I currently have a single disk UFS boot and RAID-Z for data. I plan on getting a mirror for boot, but I still don't understand what my options are regarding: - Should I set up one zfs slice for the entire drive and mimic live update functionality with writable clones? Or use multiple slices, each with a ZFS boot environment? - Is it reasonable to expect that this scheme will eventually be the way ZFS boot and Live Upgrade will work in official release so I don't have to reinstall entire system? - Are there any other drawbacks to going with ZFS boot at this time? As a side note, and the reason I am so thankful to people who created ZFS, I will tell a brief story... I used to have a Windows XP machine with a motherboard with onboard Sil3112A SATA chipset, and Seagate 200GB 7200.7drive that contained much data. I had spent months over time ripping a few hundred CDs that my wife and I had in our collection, and they were stored in .APE format (compressed, lossless, and checksummed). I had at the same time made a rip in mp3 format for iPod/iTunes, so I rarely had reason to access lossless files - they were there for long term backup and convenience. Occasionally I would realize that one of them refused to decompress (failed checksum), but I figured it is a bug somewhere and re-ripped it and hoped it wouldn't happen again. Then I realized that too many had this problem, and started to systematically decompress them, only to find out that around 25-30% of the files were damaged - at least hundred hours of ripping and cataloguing down the drain. While researching this issue, I found out that there were incompatibilities between controller and the drive, and that people on Linux had to hack the drivers to get around this problem (google Mod15Write). Windows drivers were also fixed at some point - don't know when - and if it weren't for large, checksummed files that disk was full of, I could have gone on for years without realizing that data is getting corrupted. (it was only a few bits at a time - a tiny % of total number of bits, but when you have 500MB files...). This motherboard is still alive and is currently running OpenSolaris (not using on-board SATA controller), and the drive is happily chugging along on a ICH7-based motherboard in OSX. Moral of the story being that even very mainstream and well-regarded hardware that seems a perfectly sensible purchase at the time (The very popular ASUS A7N8X-E Deluxe motherboard with Seagate SATA drives of the same period) can turn out to be a disaster, and you won't know until it is too late. Not to sound too sappy, but right now with a 1yr old, I have too many precious digital photos and videos and losing them is not an option. I use a combination of DVD and online backups, but none of it is any good if data is saliently rotting at the source. Thank you, ZFS team. On 6/4/07, Douglas Atique [EMAIL PROTECTED] wrote: Hi, I have been trying to setup a boot ZFS filesystem since b63 and found out about bug 6553537 that was preventing boot from ZFS filesystems starting from b63. First question is whether b65 has solved the problem as was planned on the bug page. Second question is: as I cannot boot successfully from a ZFS filesystem after following the ZFS Boot Manual Setup instructions (http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/) due to a panic down the call chain of vfs_mountroot, what else (other than the bug, that is) could be wrong? -- Douglas ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] ZFS Boot manual setup in b65
Hi, I have been trying to setup a boot ZFS filesystem since b63 and found out about bug 6553537 that was preventing boot from ZFS filesystems starting from b63. First question is whether b65 has solved the problem as was planned on the bug page. Second question is: as I cannot boot successfully from a ZFS filesystem after following the ZFS Boot Manual Setup instructions (http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/) due to a panic down the call chain of vfs_mountroot, what else (other than the bug, that is) could be wrong? -- Douglas This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
