search for: b134

Hi, I am posting my question to both storage-discuss and zfs-discuss as I am not quite sure what is causing the messages I am receiving. I have recently migrated my zfs volume from b104 to b134 and upgraded it from zfs version 14 to 22. It consist of two zvol''s ''vol01/zvol01'' and ''vol01/zvol02''. During zpool import I am getting a non-zero exit code, however the volume is imported successfuly. Could you please help me to understand what could b...

Hi, It doesn''t work as a PVM domain within xVM: # uname -srv SunOS 5.11 snv_133 # virt-install --name osvm01 -p -r 1024 -f /export/xvm/osvm01/disk1 -l nfs://localhost/export/install --nographics Starting install... Retrieving file unix... 100% |=========================| 2.1 MB 00:00 Retrieving file boot_arch 100% |=========================| 44 MB 00:00 Creating

I see in NexentaStor''s announcement of Community Edition 3.0.3 they mention some backported patches in this release. Aside from their management features / UI what is the core OS difference if we move to Nexenta from OpenSolaris b134? These DeDup bugs are my main frustration - if a staff member does a rm * in a directory with dedup you can take down the whole storage server - all with 1% cpu load and relatively little disk i/o due to DeDup DDT not fitting in the SSD + RAM (l2arc+arc). This is rediculous, something must be sin...

I have two 500 GB drives on my system that are attached to built-in SATA ports on my Asus M4A785-M motherboard, running in AHCI mode. If I shut down the system, remove either drive, and then try to boot the system, it will fail to boot. If I disable the splash screen, I find that it will display the SunOS banner and the hostname, but it never gets as far as the "Reading ZFS config:"

Anyone knows if this is something that will be looked at before b134 is released? Bug 13743 - virsh and xm is unable to start domain first time after boot http://defect.opensolaris.org/bz/show_bug.cgi?id=13743 Regards Henrik http://sparcv9.blogspot.com

Hi all, I''m getting a very strange problem with a recent OpenSolaris b134 install. System is: Supermicro X5DP8-G2 BIOS 1.6a 2x Supermicro AOC-SAT2-MV8 1.0b 11 Seagate Barracuda 1TB ES.2 ST31000340NS drives If I have any of the 11 1TB Seagate drives plugged into the controller, the AOC-SAT2-MV8 BIOS appears to detect them just fine, but I get the following problems:...

Not sure what the best list to send this to is right now, so I have selected a few, apologies in advance. A couple questions. First I have a physical host (call him bob) that was just installed with b134 a few days ago. I upgraded to b145 using the instructions on the Illumos wiki yesterday. The pool has been upgraded (27) and the zfs file systems have been upgraded (5). chris at bob:~# zpool upgrade rpool This system is currently running ZFS pool version 27. Pool ''rpool'' is al...

Not sure what the best list to send this to is right now, so I have selected a few, apologies in advance. A couple questions. First I have a physical host (call him bob) that was just installed with b134 a few days ago. I upgraded to b145 using the instructions on the Illumos wiki yesterday. The pool has been upgraded (27) and the zfs file systems have been upgraded (5). chris at bob:~# zpool upgrade rpool This system is currently running ZFS pool version 27. Pool ''rpool'' is al...

Hello, Im new to this discussion lists so i hope im posting in the right place. I started using zfs not too long ago. Im trying to figure out the ISCSI and NFS sharing for the moment. For the ISCSI sharing at the moment im using COMSTAR. A created the appropriate target, also a LU corespondent to the zvol with sbdadm, then created a view attached to this. Im wondering is there a way to actually

...have a fresh install of Solaris 11 Express on a new SSD. I have inserted the old hard disk, and tried to import it, with: # zpool import -f <long id number> Old_rpool but the computer reboots. Why is that? On my old hard disk, I have 10-20 BE, starting with OpenSolaris 2009.06 and upgraded to b134 up to snv_151a. I also have a WinXP entry in GRUB. This hard disk is partitioned, with a 900GB zfs TempStorage partition. I can import the TempStorage partition without problems, but can not import the rpool. How can I access my data from the old hard disk''s rpool? Any pointers or help...

I''m running a mirrored pair of 2 TB SATA drives as my data storage drives on my home workstation, a Core i7-based machine with 10 GB of RAM. I recently added a sandforce-based 60 GB SSD (OCZ Vertex 2, NOT the pro version) as an L2ARC to the single mirrored pair. I''m running B134, with ZFS pool version 22, with dedup enabled. If I understand correctly, the dedup table should be in the L2ARC on the SSD, and I should have enough RAM to keep the references to that table in memory, and that this is therefore a well-performing solution. My question is what happens at power off....

Hi, I have a problem similar to the previous poster (thread: Virtual network of DomU''s), but apparently not with similar solutions... Situation: - two physical links aggregated to "default0" - dladm create-vlan on default0 with several different vlans - xVM DomU running linux connected to the same vlans when trying to ping the DomU from Dom0, I can see with snoop (in Dom0)

...How can it be missing a device that didn''t exist? A "zpool import -fF" results in the above kernel panic. This also creates /etc/zfs/zpool.cache.tmp, which then results in the pool being imported, which leads to a continuous reboot/panic cycle. I can''t obviously use b134 to import the pool without logs, since that would imply upgrading the pool first, which is hard to do if it''s not imported. My zdb skills are lacking - zdb -l gets you about so far and that''s it. (where the heck are the other options to zdb even written down, besides in the code...

...39;m including zfs-discuss to get the ZFS folks thoughts on the issue. -evan More info from original thread: > On 05/ 4/10 10:45 AM, Christian Thalinger wrote: >> On Tue, 2010-05-04 at 10:36 -0500, Shawn Walker wrote: >>>> What confuses me is that the update from b133 to b134 obviously worked >>>> before--because I have a b134 image--but it doesn''t now. >>> >>> I''m on b135 myself and haven''t seen this issue yet. >>> >>>> I can''t think of anything I did that changed anything on th...

Hi, I have two servers running: freebsd with a zpool v28 and a nexenta (opensolaris b134) running zpool v26. Replication (with zfs send/receive) from the nexenta box to the freebsd works fine, but I have a problem accessing my replicated volume. When I''m typing and autocomplete with tab key the command cd /remotepool/us (for /remotepool/users) I get a panic. check the panic...

Hi list, while preparing for the changed ACL/mode_t mapping semantics coming with onnv-147 [1], I discovered that in onnv-134 on my system ACLs are not inherited when aclmode is set to passthrough for the filesystem. This very much puzzles me. Example: $ uname -a SunOS os 5.11 snv_134 i86pc i386 i86pc $ pwd /Volumes/ACLs/dir1 $ zfs list | grep /Volumes rpool/Volumes 7,00G 39,7G 6,84G

...a X-25V @ 40GB and use 15-20 GB for root and the rest for an L2ARC. For small form factor machines or machines with max capacity of 8GB of RAM (a typical home system) this can make a pleasant improvement over a HDD-only implementation." For the upcoming 2010.03 release and now testing with a b134. What is the most appropiate way to accomplish this? The caiman installer allows you to control the size of the partition on the boot disk but it doesn''t allow you (at least I couldn''t figure out how) to control the size of the slices. So you end with slice0 filling the entire pa...

Hi, I hit ZFS bug that it would be resolve in latter snv 134 or latter. I''m running SNV111 How do I upgrade to latest version ? THanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100821/7d8eebc1/attachment.html>

...getting our data off. We then deleted a filesystem that was using de-duplication and the box suddenly went into a freeze and the pool had activity like crazy. After several failed attempts to recover the box to usable state (days of importing failed), we reloaded the boot drives with Nexenta 3.0 (b134) (which was our goal anyway). When we tried to import this pool again, after 24 hours the pool finally imported but with the error that the two spares were FAULTED with too many errors. Controller is an LSI 1068E-IR Normally, I''d believe the drive was dead except, both spares? Could this...

...tarcyrheb=sun16 crashkernel=128M KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /boot/initramfs-2.6.32-696.el6.x86_64.img title Debian 8.7 root (hd0,1) chainloader +1 title Scientific Linux 6.7 (Carbon) root(hd0,2) kernel /boot/vmlinuz-2.6.32-573.el6.x86_64 ro root=UUID=af382492-c826-4cf8-b134-9456fe5c100c initrd /boot/initramfs-2.6.32-573.el6.x86_64.img chainloader +1 I can boot fine into the Mac OSX from rEFInd. When I boot from rEFInd into the CentOS partition I get the Grub version 0.97 menu list with the 3 OSs listed above. I can then boot fine into CentOS 6.8 or Debian 8.7 just...