Re: [zfs-discuss] After update to S11, zfs reports some disks as 'corrupted data'
Phew… seems that the S11 update process replaced my modified qlc.conf with a standard one. In SE11 I had to lower the queue depth by setting max_execution_throttle to something lower than 16. Mostly since I am exposing 16 LUNs from each storage and this the qlc.driver flooded the storage controllers with I/Os. Cheers, budy ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] early save the date: What's New and What's Coming in ZFS for illumos, Jan 10
Sign up at: http://www.meetup.com/illumos-User-Group/events/41665962/ January's meeting of the Bay Area illumos user group (formerly SFOSUG and SVOSUG) will feature a report from Matt Ahrens of the ZFS Working Group about what's new and what's coming in ZFS, with time for discussion about other topics of interest to the community. Pizza and beer (and soft drinks) will be provided. Note: The following meetup will be at Joyent's San Francisco office; we'll switch locations between the city and the Valley to spread the commute burden. Frequency of meetings TBD. Yes, we'll try to stream it and definitely record it. -- best regards, Deirdré Straughan SmartOS Community Manager Joyent cell 720 371 4107 ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] early save the date: What's New and What's Coming in ZFS for illumos, Jan 10
Thank you for the note. A stream, or an mpeg file will certainly be appreciated by those of us not on the west coast. Jerry On 11/21/11 02:03 PM, Deirdre Straughan wrote: Sign up at: http://www.meetup.com/illumos-User-Group/events/41665962/ January's meeting of the Bay Area illumos user group (formerly SFOSUG and SVOSUG) will feature a report from Matt Ahrens of the ZFS Working Group about what's new and what's coming in ZFS, with time for discussion about other topics of interest to the community. Pizza and beer (and soft drinks) will be provided. Note: The following meetup will be at Joyent's San Francisco office; we'll switch locations between the city and the Valley to spread the commute burden. Frequency of meetings TBD. Yes, we'll try to stream it and definitely record it. -- best regards, Deirdré Straughan SmartOS Community Manager Joyent cell ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] virtualbox rawdisk discrepancy
I have a Sun machine running Solaris 10, and a Vbox instance running Solaris 11 11/11. The vbox machine has a virtual disk pointing to /dev/disk1 (rawdisk), seen in sol11 as c0t2. If I create a zpool on the Sun s10 machine, on a USB stick, I can take that USB stick and access it through the vbox virtual disk. Just as expected. If I boot vbox from the s11 ISO, and install s11 onto USB stick (via the virtual device), I can boot the Sun machine from it, which puts up the grub menu but then fails to boot Solaris. There's some kind of error which might not be making it to /SP/console, but after grub it seems to hang for a few seconds then reboot. The vbox happens to be running on Mac OS 10.6.x. This *should* work, yes? Any thoughts as to why it doesn't? Not that this should matter, but on the vbox machine, sol11 sees the USB stick as a normal SATA hard drive, e.g. when I run 'format' it is in the list of drives. On the Sun machine, it is seen as a removable drive by s10, e.g. I have to run 'format -e' to see the drive. ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] virtualbox rawdisk discrepancy
On Tue, Nov 22, 2011 at 11:26 AM, Frank Cusack fr...@linetwo.net wrote: I have a Sun machine running Solaris 10, and a Vbox instance running Solaris 11 11/11. The vbox machine has a virtual disk pointing to /dev/disk1 (rawdisk), seen in sol11 as c0t2. If I create a zpool on the Sun s10 machine, on a USB stick, I can take that USB stick and access it through the vbox virtual disk. Just as expected. If I boot vbox from the s11 ISO, and install s11 onto USB stick (via the virtual device), I can boot the Sun machine from it, which puts up the grub menu but then fails to boot Solaris. There's some kind of error which might not be making it to /SP/console, but after grub it seems to hang for a few seconds then reboot. The vbox happens to be running on Mac OS 10.6.x. This *should* work, yes? Any thoughts as to why it doesn't? Not that this should matter, but on the vbox machine, sol11 sees the USB stick as a normal SATA hard drive, e.g. when I run 'format' it is in the list of drives. On the Sun machine, it is seen as a removable drive by s10, e.g. I have to run 'format -e' to see the drive. So basically the question is if you install solaris on one machine, can you move the disk (in this case the usb stick) to another machine and boot it there, right? The answer, as far as I know, is NO, you can't. Of course, I could be wrong though (and in this case I'll be happy if I'm wrong :D ). IIRC the only supported way to move (or clone) solaris installation is by using flash archive (flar), which (now) should also work on zfs. -- Fajar ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] virtualbox rawdisk discrepancy
On Mon, Nov 21, 2011 at 9:04 PM, Fajar A. Nugraha w...@fajar.net wrote: So basically the question is if you install solaris on one machine, can you move the disk (in this case the usb stick) to another machine and boot it there, right? Yes, but one of the machines is a virtual machine. The answer, as far as I know, is NO, you can't. Of course, I could be wrong though (and in this case I'll be happy if I'm wrong :D ). IIRC the only supported way to move (or clone) solaris installation is by using flash archive (flar), which (now) should also work on zfs. If we ignore the vbox aspect of it, and assume real hardware with real devices, of course you can install on one x86 hardware and move the drive to boot on another x86 hardware. This is harder on SPARC (b/c hostid and zfs mount issues) but still possible. The weird thing here is that the install hardware is a virtual machine. One thing I know is odd is that the USB drive is seen to the virtual machine as a SATA drive but when moved to the real hardware it's seen as a USB drive. There may be something else going on here that someone more familiar with vbox may know more about. Since this works seamlessly when the zpool in question is just a data pool, I'm wondering why it doesn't work when it's a boot drive. One thing I noticed is that when mounting it as a data drive, the real hardware sees the type of disk (between ... in 'format' output) as ATA-VBOX. Clearly that info must have been written when the pool was created on vbox, and maybe some hardware info was encoded that doesn't match up when it's booted as a real USB stick. This doesn't to matter when it's a data pool but maybe this is tripping it up during boot. ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] virtualbox rawdisk discrepancy
On Tue, Nov 22, 2011 at 12:19 PM, Frank Cusack fr...@linetwo.net wrote: On Mon, Nov 21, 2011 at 9:04 PM, Fajar A. Nugraha w...@fajar.net wrote: So basically the question is if you install solaris on one machine, can you move the disk (in this case the usb stick) to another machine and boot it there, right? Yes, but one of the machines is a virtual machine. It shouldn't matter, really. As far as solaris (or any other is) is concerned, it's just a different machine. The answer, as far as I know, is NO, you can't. Of course, I could be wrong though (and in this case I'll be happy if I'm wrong :D ). IIRC the only supported way to move (or clone) solaris installation is by using flash archive (flar), which (now) should also work on zfs. If we ignore the vbox aspect of it, and assume real hardware with real devices, of course you can install on one x86 hardware and move the drive to boot on another x86 hardware. This is harder on SPARC (b/c hostid and zfs mount issues) but still possible. Have you tried? :D IIRC there was a discussion about it (several years ago, I think), and the issue back then was that there might be some necessary device nodes not available when you simply move the disk around. The weird thing here is that the install hardware is a virtual machine. One thing I know is odd is that the USB drive is seen to the virtual machine as a SATA drive That's how it works when you use rawdisk passthrough. Virtualbox does not have the necessary USB-boot support (yet). Think of it like you have a SATA disk with usb enclosure, but now you remove the enclosure and plug it directly to the onboard SATA controller. but when moved to the real hardware it's seen as a USB drive. ... and that's how it should be There may be something else going on here that someone more familiar with vbox may know more about. Since this works seamlessly when the zpool in question is just a data pool, I'm wondering why it doesn't work when it's a boot drive. I have a hunch that it might be something related to grub. Trying something ... -- Fajar ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] virtualbox rawdisk discrepancy
On Mon, Nov 21, 2011 at 9:31 PM, Fajar A. Nugraha w...@fajar.net wrote: On Tue, Nov 22, 2011 at 12:19 PM, Frank Cusack fr...@linetwo.net wrote: If we ignore the vbox aspect of it, and assume real hardware with real devices, of course you can install on one x86 hardware and move the drive to boot on another x86 hardware. This is harder on SPARC (b/c hostid and zfs mount issues) but still possible. Have you tried? :D Yes, I do this all the time. Between identical hardware, though. It used to be tricky when you had to know actual device paths and/or /dev/dsk/* names but with zfs that issue has gone away and it doesn't matter if drives show up at different locations when moving the boot drive around. ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] virtualbox rawdisk discrepancy
On Tue, Nov 22, 2011 at 12:53 PM, Frank Cusack fr...@linetwo.net wrote: On Mon, Nov 21, 2011 at 9:31 PM, Fajar A. Nugraha w...@fajar.net wrote: On Tue, Nov 22, 2011 at 12:19 PM, Frank Cusack fr...@linetwo.net wrote: If we ignore the vbox aspect of it, and assume real hardware with real devices, of course you can install on one x86 hardware and move the drive to boot on another x86 hardware. This is harder on SPARC (b/c hostid and zfs mount issues) but still possible. Have you tried? :D Yes, I do this all the time. Between identical hardware, though. It used to be tricky when you had to know actual device paths and/or /dev/dsk/* names but with zfs that issue has gone away and it doesn't matter if drives show up at different locations when moving the boot drive around. Ah, you're more experienced that I am then. In that case you might want to try: - boot with live CD on your sun box - plug your usb drive there - force-import then export your usb root pool (to eliminate any disk path or ID problem) - try boot from usb drive - if the above still doesn't work, try running installgrub: http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#ZFS_Root_Pool_and_Boot_Issues I'm still trying to install sol11 on USB, but it's dreadfully slow on my system (not sure why) -- Fajar ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] virtualbox rawdisk discrepancy
On Mon, Nov 21, 2011 at 9:59 PM, Fajar A. Nugraha w...@fajar.net wrote: On Tue, Nov 22, 2011 at 12:53 PM, Frank Cusack fr...@linetwo.net wrote: On Mon, Nov 21, 2011 at 9:31 PM, Fajar A. Nugraha w...@fajar.net wrote: On Tue, Nov 22, 2011 at 12:19 PM, Frank Cusack fr...@linetwo.net wrote: If we ignore the vbox aspect of it, and assume real hardware with real devices, of course you can install on one x86 hardware and move the drive to boot on another x86 hardware. This is harder on SPARC (b/c hostid and zfs mount issues) but still possible. Have you tried? :D Yes, I do this all the time. Between identical hardware, though. It used to be tricky when you had to know actual device paths and/or /dev/dsk/* names but with zfs that issue has gone away and it doesn't matter if drives show up at different locations when moving the boot drive around. Ah, you're more experienced that I am then. In that case you might want to try: - boot with live CD on your sun box - plug your usb drive there - force-import then export your usb root pool (to eliminate any disk path or ID problem) ah, good idea - try boot from usb drive - if the above still doesn't work, try running installgrub: http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#ZFS_Root_Pool_and_Boot_Issues grub does need to have an idea of the device path, maybe in vbox it's seen as the 3rd disk (c0t2), so the boot device name written to grub.conf is disk3 (whatever the terminology for that is in grub-speak), but when I boot on the Sun hardware it is seen as disk0 and this just doesn't work. If it's that easy that'd be awesome, all I need is an alternate grub entry. I'm still trying to install sol11 on USB, but it's dreadfully slow on my system (not sure why) Same here, sustained write to a USB stick is painfully slow. Normal operation is fine though. ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] virtualbox rawdisk discrepancy
Moving boot disks from one machine to another used to work as long as the machines were of the same architecture. I don't recall if it was *supported* (and wouldn't want to pretend to speak for Oracle now), but it was meant to work (unless you minimized the install and removed drivers not needed on the first system that are needed on the other system). You did have to do a reconfigure boot though! Nico -- ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] virtualbox rawdisk discrepancy
On Mon, Nov 21, 2011 at 10:06 PM, Frank Cusack fr...@linetwo.net wrote: grub does need to have an idea of the device path, maybe in vbox it's seen as the 3rd disk (c0t2), so the boot device name written to grub.conf is disk3 (whatever the terminology for that is in grub-speak), but when I boot on the Sun hardware it is seen as disk0 and this just doesn't work. If it's that easy that'd be awesome, all I need is an alternate grub entry. Or maybe not. I guess this was findroot() in sol10 but in sol11 this seems to have gone away. Also, I was wrong about the disk target. When I do the install I configure the USB stick at disk0, seen by Solaris as c3t0, and no findroot() line gets written to menu.lst. Maybe it needs that line when it boots as a USB still on real hardware? I'll try import/export and a reconfigure boot when I get a chance. ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
