Re: [OpenIndiana-discuss] Using OI as a combined storage server andvirtual server enviroment
Hi, You can do all of that and much more. Here is one example. http://blog.laspina.ca/ubiquitous/provisioning_disaster_recovery_with_zf s Regards, Mike http://blog.laspina.ca/ -Original Message- From: Mats Taraldsvik [mailto:mats.taralds...@gmail.com] Sent: Friday, April 20, 2012 5:31 AM To: openindiana-discuss@openindiana.org Subject: [OpenIndiana-discuss] Using OI as a combined storage server andvirtual server enviroment Hi, I'm currently using EON ZFS as a storage server, but would like to be able to host a couple of virtual machines as well -- using only a single server. Will I, using OI, be able to share a zpool between the virtual machines (created with KVM or another OI-supported technology, and stored in the same or a different zpool), either directly,through nfs or iscsi? Regards, Mats Taraldsvik ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] SSDs honoring cache flush?
This was corrected if you're an Illumos build after Jan 2012 Bug ID 1909 http://www.listbox.com/member/archive/182179/2012/01/search/MTA5MA/sort/time_rev/page/1/?search_for=1909 -Original Message- From: Roy Sigurd Karlsbakk [mailto:r...@karlsbakk.net] Sent: Tuesday, April 24, 2012 11:51 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] SSDs honoring cache flush? > I thought there were perfomance issues with using SLOGs in general on > OI since 148? Do you have any data on that one? An issue number? Something? Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 98013356 r...@karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] openindiana ldap client
Hi Tim, Try the following change to the nsswitch.conf file # consult /etc "files" only if ldap is down. hosts: files dns mdns ldap This will set the resolution order to; 1 local hosts file, 2 dns, 3 multicast dns, 4 ldap lookup Regards, Mike -Original Message- From: Tim Dunphy [mailto:bluethu...@gmail.com] Sent: Saturday, May 05, 2012 9:43 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] openindiana ldap client Thanks! That really did the trick! ldapclient manual -a credentialLevel=proxy -a authenticationMethod=simple -a proxyDN=cn=Manager,dc=example,dc=com -a proxyPassword=secret -a defaultSearchBase=dc=example,dc=com -a domainName=example.com -a defaultServerList=192.168.1.44 Grep ldap for ldap user: root@openindiana:/var/ldap# getent passwd | grep walbs walbs:x:1002:1003:Walkiria Soares-Dunphy:/home/walbs:/bin/bash However I notice that now dns resolution seems mixed up, but only since running ldapclient: root@openindiana:/var/ldap# ping yahoo.com ping: unknown host yahoo.com Here's what nsswitch.conf is looking like: root@openindiana:/var/ldap# cat /etc/nsswitch.conf # CDDL HEADER START # # The contents of this file are subject to the terms of the # Common Development and Distribution License (the "License"). # You may not use this file except in compliance with the License. # # You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE # or http://www.opensolaris.org/os/licensing. # See the License for the specific language governing permissions # and limitations under the License. # # When distributing Covered Code, include this CDDL HEADER in each # file and include the License file at usr/src/OPENSOLARIS.LICENSE. # If applicable, add the following below this CDDL HEADER, with the # fields enclosed by brackets "[]" replaced with your own identifying # information: Portions Copyright [] [name of copyright owner] # # CDDL HEADER END # # Copyright (c) 1999, 2010, Oracle and/or its affiliates. All rights reserved. # # # /etc/nsswitch.ldap: # # An example file that could be copied over to /etc/nsswitch.conf; it # uses LDAP in conjunction with files. # # "hosts:" and "services:" in this file are used only if the # /etc/netconfig file has a "-" for nametoaddr_libs of "inet" transports. # LDAP service requires that svc:/network/ldap/client:default be enabled # and online. # the following two lines obviate the "+" entry in /etc/passwd and /etc/group. passwd: files ldap group: files ldap # consult /etc "files" only if ldap is down. hosts: files ldap # Note that IPv4 addresses are searched for in all of the ipnodes databases # before searching the hosts databases. ipnodes:files ldap networks: files ldap protocols: files ldap rpc:files ldap ethers: files ldap netmasks: files ldap bootparams: files ldap publickey: files ldap netgroup: ldap automount: files ldap aliases:files ldap # for efficient getservbyname() avoid ldap services: files ldap printers: user files ldap auth_attr: files ldap prof_attr: files ldap project:files ldap tnrhtp: files ldap tnrhdb: files ldap If I revert the file to pre-ldapclient I can ping yahoo and external hosts again: root@openindiana:/var/ldap# cat /etc/nsswitch.conf.bak > /etc/nsswitch.conf root@openindiana:/var/ldap# ping yahoo.com yahoo.com is alive And of course I can't find ldap users in the directory again. root@openindiana:/var/ldap# getent passwd | grep walbs root@openindiana:/var/ldap# Is there any way to have my cake and eat it too? thanks tim On Sat, May 5, 2012 at 9:57 PM, Joshua M. Clulow wrote: > On 6 May 2012 11:15, Tim Dunphy wrote: >> I've also tried using ldapclient, but am having no luck there either: > > I would definitely suggest that you'll want to use the native LDAP > bits, not the PADL stuff. > >> root@openindiana:~/nss_ldap-265# ldapclient init -v -a >> profileName=default \ >>> -a domainname=example.com \ >>> -a proxyDN=cn=uid=proxy,ou=People,dc=example,dc=com \ -a >>> proxyPassword=secret \ >>> 192.168.1.44 >> Parsing profileName=default >> Parsing domainname=example.com >> Parsing proxyDN=cn=uid=proxy,ou=People,dc=example,dc=com >> Parsing proxyPassword=secret >> Arguments parsed: >> domainName: example.com >> proxyDN: cn=uid=proxy,ou=People,dc=example,dc=com >> profileName: default >> proxyPassword: secret >> defaultServerList: 192.168.1.44 Handling init option About to >> configure machine by downloading a profile Can not find the >> nisDomainObject for domain example.com > > So you're specifying a profileName here. Have you created a profile > object in your directory with the name "default"? The "init" mode of > ldapclient uses a profile object in the directory for configuration. > > If you don't have or don't want to have a profile object, you could > try using "ldapclient manual" rather than "ldapclient init". I > believe the man
Re: [OpenIndiana-discuss] unable to start nfs
Tim, If you use that method your NFS share properties will only live in the hosts dfstab file. By setting zfs properties you achieve the same thing except the share follows the zfs filesystem. (nas/vol0 in this example) e.g. zfs set sharenfs=rw,nosuid,root=vmware-host-ip-etc sp1/nas/vol0 zfs set mountpoint=/export/ss1-nas-vol0 sp1/nas/vol0 If you do a zfs send to an external zfspool the property lives on it without a tab change. Warning: rw=all = danger! Do you really want every node to have rw access? -Original Message- From: Tim Dunphy [mailto:bluethu...@gmail.com] Sent: Monday, May 07, 2012 4:12 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] unable to start nfs well, shiver me timbers!!! all I had to do to get the service started was to add an entry in dfstab: root@openindiana:/export/home/bluethundr# tail /etc/dfs/dfstab# Do not modify this file directly. # Use the sharemgr(1m) command for all share management # This file is reconstructed and only maintained for backward # compatibility. Configuration lines could be lost. # # share [-F fstype] [ -o options] [-d ""] [resource] # .e.g, # share -F nfs -o rw=engineering -d "home dirs" /export/home2 share -F nfs -o sec=sys,rw=all -d "xen share" /tank/xen I had the idea of adding the entry and starting the service. So glad that did the trick! Thanks for your help guys! On Mon, May 7, 2012 at 3:27 PM, Tim Dunphy wrote: >> To be pedantic, you don't share a zpool, but filesystem directories, >> over NFS :) > > Point taken. :) > >> In fact, you should check the output of "svcs -a | grep nfs" for >> hints whether your nfs/server is "online" or in another state; if it >> is not online, you can drill down to see why. > > It definitely looks as it's offline at the moment. > > root@openindiana:/export/home/bluethundr# svcs -a | grep > svc:/network/nfs/server:default disabled 14:33:21 > svc:/network/nfs/server:default > > Forgive my ignorance but I'm a little new at solaris. The only > drilling down I've done so far is this: > > svc:/network/nfs/server:default (NFS server) > State: disabled since May 7, 2012 03:11:28 PM EDT > Reason: Temporarily disabled by an administrator. > See: http://illumos.org/msg/SMF-8000-1S > See: nfsd(1M) > See: /var/svc/log/network-nfs-server:default.log > Impact: This service is not running. > > root@openindiana:~# svcs -l nfs/server fmri > svc:/network/nfs/server:default name NFS server enabled > false (temporary) state disabled next_state none state_time > May 7, 2012 03:11:28 PM EDT logfile > /var/svc/log/network-nfs-server:default.log > restarter svc:/system/svc/restarter:default contract_id dependency > require_any/error svc:/milestone/network (online) dependency > require_all/error svc:/network/nfs/nlockmgr (online) dependency > optional_all/error svc:/network/nfs/mapid (online) dependency > require_all/restart svc:/network/rpc/bind (online) dependency > optional_all/none svc:/network/rpc/keyserv (online) dependency > optional_all/none svc:/network/rpc/gss (online) dependency > optional_all/none svc:/network/shares/group (multiple) dependency > optional_all/none svc:/system/filesystem/reparse (online) dependency > require_all/error svc:/system/filesystem/local (online) > > Everything that NFS relies on seems to be 'online' and the only > difference is in the entry for vc:/network/shares/group (multiple). > Which seems to correspond to the message I'm getting when I try to > start the service recursively: > > > root@openindiana:~# svcadm enable -r nfs/server > svcadm: svc:/milestone/network depends on svc:/network/physical, which > has multiple instances. > > >> What happens if you do this? >> svcadm enable nfs/server > > If I do this it's basically the same thing as before: > > root@openindiana:~# svcadm enable nfs/server root@openindiana:~# svcs > -a | grep nfs | grep server disabled 15:17:31 > svc:/network/nfs/server:default > >>Do you have any NFS shares defined via zfs sharenfs attribute and/or >>/etc/dfs/dfstab file (legacy)? What does the "share" >>command report (should return a list of defined shares, if any), >>similar to "exportfs" output. > > root@openindiana:~# share > root@openindiana:~# > > root@openindiana:~# cat /etc/dfs/dfstab > > # Do not modify this file directly. > # Use the sharemgr(1m) command for all share management # This file is > reconstructed and only maintained for backward # compatibility. > Configuration lines could be lost. > # > # share [-F fstype] [ -o options] [-d ""] > [resource] # .e.g, # share -F nfs -o rw=engineering -d > "home dirs" /export/home2 > > This is a brand-new setup and I haven't attempted to setup any shares > prior to trying to setup NFS. > > > Basically my goal is to share the top directory of my zpool which > looks like this: > > root@openindiana:~# df -h /tank >
Re: [OpenIndiana-discuss] boot-archive timing out after 3ware driverinstall
The only thing I can think of is ... did you refresh the active service
manifest?
e.g.
svcadm refresh boot-archive:default
-Original Message-
From: Ian Levesque [mailto:i...@crystal.harvard.edu]
Sent: Thursday, May 10, 2012 1:07 PM
To: Discussion list for OpenIndiana
Subject: [OpenIndiana-discuss] boot-archive timing out after 3ware
driverinstall
Hello,
I have a file server with OpenIndiana 151a4 installed. It has a 3ware
9750 SAS card installed with 13 drives attached. I configured each drive
as a "single" disk (there's no JBOD/passthrough), and then setup a zpool
with said drives.
When I rebooted the server, however, it appears that activating the
individual drives is taking too long for the boot-archive to finish
loading. Here's what I see during boot:
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=11
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=7
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=1
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=6
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=8
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=5 May
10 12:55:06 svc.startd[10]: svc:/system/boot-archive:default: Method or
service exit timed out. Killing contract 19.
May 10 12:55:06 svc.startd[10]: svc:/system/boot-archive:default: Method
"/lib/svc/method/boot-archive" failed due to signal KILL.
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=12
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=2
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=0
This causes some 70-odd services to thereby fail, leaving the system
pretty much in maintenance mode.
If I remove the 3ware drivers from /kernel/drv/amd64/ and /kernel/drv/
then reboot, there are no errors with the boot-archive. Unfortunately,
there are also no storage drives for my zpool.
The closest google turns up is here:
http://www.unix.com/solaris/155331-system-stuck-up-maintanence-mode.html
I did run `svccfg -s boot-archive setprop start/timeout_seconds=180` but
the /var/svc/log/system-boot-archive:default.log seems to indicate that
I'm only getting 60 seconds:
[ May 10 12:54:03 Enabled. ]
[ May 10 12:54:06 Executing start method
("/lib/svc/method/boot-archive"). ] [ May 10 12:55:06 Method or service
exit timed out. Killing contract 19. ]
# svccfg -s boot-archive listprop | grep timeout
start/timeout_seconds count 180
stop/timeout_secondscount 3
Any advice other than throw away my $500 HBA? :)
Best,
Ian
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] can't delete aggregate (dladm)
Hi Tim, I always create users for automated functions and never use root unless its forced. As well I usually create a group which is used to assign any required rights for the role or function. The cron job should be assigned to the running user which you can always edit as a primary admin. e.g. crontab -e user-role Least access principle has saved by bacon more times than I wish to count. Regards, Mike -Original Message- From: Tim Dunphy [mailto:bluethu...@gmail.com] Sent: Monday, May 14, 2012 1:50 PM To: Discussion list for OpenIndiana Subject: [OpenIndiana-discuss] can't delete aggregate (dladm) Hello list, I was trying to fix a problem I was having in being able to ping external hosts. For some reason I was able to ping other hosts on the network but had to reboot after installing a package. When the host (an OI 151 box) came back up it wasn't able to ping anything except itself. The links were setup in an active/passive link aggregate called aggr0. I decided to attempt to recreate the link pool with the dladm remove-aggr command. But when I typed dladm remove-aggr -d e1000g1 1 I see the message : dladm: remove operation failed: object not found. Which is weird because if I do a dladm show-aggr I see the aggregate in question. I was able to unplumb the aggregate link with ifconfig aggr0 unplumb. But I cannot plumb or unplumb the individual physical links at this point. If I unplumb them I get ifconfig unplumb e1000g0 ifconfig: cannot unplumb e1000g0: Interface does not exist When I plumb it I see: ifconfig e1000g0 plumb ifconfig: cannot plumb e1000g0: Interface already in use This is a very confusing situation! Does anyone have any solution for this? I need to be able to delete the link aggregation, plumb the individual interfaces and verify they are working before recreating the aggregate. I have good instructions for creating an aggregate and it was working well at one recent point. But I decided to try another tutorial that lead me down this path, and now I know which one to avoid! thanks for any advice you may have -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] can't delete aggregate (dladm)
Sorry its Mark not Tim, Hit reply on the next list message. -Original Message- From: Mike La Spina Sent: Tuesday, May 15, 2012 10:18 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] can't delete aggregate (dladm) Hi Tim, I always create users for automated functions and never use root unless its forced. As well I usually create a group which is used to assign any required rights for the role or function. The cron job should be assigned to the running user which you can always edit as a primary admin. e.g. crontab -e user-role Least access principle has saved by bacon more times than I wish to count. Regards, Mike -Original Message- From: Tim Dunphy [mailto:bluethu...@gmail.com] Sent: Monday, May 14, 2012 1:50 PM To: Discussion list for OpenIndiana Subject: [OpenIndiana-discuss] can't delete aggregate (dladm) Hello list, I was trying to fix a problem I was having in being able to ping external hosts. For some reason I was able to ping other hosts on the network but had to reboot after installing a package. When the host (an OI 151 box) came back up it wasn't able to ping anything except itself. The links were setup in an active/passive link aggregate called aggr0. I decided to attempt to recreate the link pool with the dladm remove-aggr command. But when I typed dladm remove-aggr -d e1000g1 1 I see the message : dladm: remove operation failed: object not found. Which is weird because if I do a dladm show-aggr I see the aggregate in question. I was able to unplumb the aggregate link with ifconfig aggr0 unplumb. But I cannot plumb or unplumb the individual physical links at this point. If I unplumb them I get ifconfig unplumb e1000g0 ifconfig: cannot unplumb e1000g0: Interface does not exist When I plumb it I see: ifconfig e1000g0 plumb ifconfig: cannot plumb e1000g0: Interface already in use This is a very confusing situation! Does anyone have any solution for this? I need to be able to delete the link aggregation, plumb the individual interfaces and verify they are working before recreating the aggregate. I have good instructions for creating an aggregate and it was working well at one recent point. But I decided to try another tutorial that lead me down this path, and now I know which one to avoid! thanks for any advice you may have -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] problem route traceroute pkg.openindiana.orgon 109.71.206.26
Arhipkin, Did you try traceroute -I pkg.openindiana.org Many ISP's do not respond to UDP pings. In this case it looks like the pkg host was actually down. Regards, Mike -Original Message- From: Arhipkin Ilya [mailto:i...@arhipkin.com] Sent: Thursday, May 17, 2012 5:26 AM To: Discussion list for OpenIndiana Subject: [OpenIndiana-discuss] problem route traceroute pkg.openindiana.orgon 109.71.206.26 ilya@miass:~$ traceroute pkg.openindiana.org traceroute to pkg.openindiana.org (91.194.74.133), 30 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 0.618 ms 0.549 ms 0.475 ms 2 217.19.117.145.static.uic.ru (217.19.117.145) 2.539 ms 2.766 ms 2.565 ms 3 217.19.112.129.static.uic.ru (217.19.112.129) 2.870 ms 3.218 ms 3.564 ms 4 62.148.255.9 (62.148.255.9) 8.979 ms 9.034 ms 8.801 ms 5 * * * 6 * * * 7 ae-2.chbs-rgr3.ur.ip.rostelecom.ru (188.128.91.81) 18.535 ms 9.530 ms 74.631 ms 8 * * * 9 ge-1-0-3.r02.frnkge04.de.bb.gin.ntt.net (213.198.82.165) 93.110 ms 93.105 ms 93.396 ms 10 ae-3.r20.frnkge04.de.bb.gin.ntt.net (129.250.3.93) 139.473 ms 88.352 ms 95.757 ms 11 ae-1.r23.amstnl02.nl.bb.gin.ntt.net (129.250.3.179) 143.851 ms 101.716 ms 101.240 ms 12 * * * 13 te3-2-0-cr0.nik.nl.as6908.net (81.20.64.42) 117.917 ms 115.956 ms 117.584 ms 14 te1-4-3508-cr0.thn.uk.as6908.net (78.41.154.13) 127.272 ms 211.781 ms 109.575 ms 15 195.72.129.157 (195.72.129.157) 106.566 ms 103.591 ms 332.526 ms 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * :-(Due to the repository is not available trace packet loss turned out to my email address ilya@miass:~$ sudo pkg install gcc-dev SUNWxorg-headers Password: pkg: 0/1 catalogs successfully updated: Unable to contact valid package repository Encountered the following error(s): Unable to contact any configured publishers. This is likely a network configuration problem. Framework error: code: 28 reason: Connection time-out URL: 'http://pkg.openindiana.org/dev'. (happened 4 times) ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] COMSTAR qlt dropping link and resetting
Hi Adrian, What logs have you checked. The SanBoxes? Dmesg? Stmf service? Are you running snapshots? Dedup? Compression? IRQ sharing? echo ::interrupts | mdb -k -Original Message- From: Adrian Carpenter [mailto:ta...@wbic.cam.ac.uk] Sent: Friday, May 18, 2012 3:26 AM To: openindiana-discuss@openindiana.org Subject: [OpenIndiana-discuss] COMSTAR qlt dropping link and resetting We are using one port of each of a pair of Qlogic 2562 cards to act as a FC target for our Xen environment, we are running oi_151a4. The other port on each card is used as an initiator to attach to some FC storage(Nexsan). We use two Qlogic SanBoxes configured so that the Xen hypervisors have a redundant path to the FC target which provides a Storage Repository from a ZVOL. Everything works really well as expected with good throughput, but randomly once every couple of days simultaneously BOTH FC targets on the Openindiana box reset their FC connections - this of course causes real problem in Xen environment and is not help by having redundant multipaths. We are at a bit of a loss, does anyone have any suggestions? Adrian ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] COMSTAR qlt dropping link and resetting
Hi Adrian, The SanBoxes? - Nexsan nothing in their logs OK Dmesg? : > May 17 17:33:47 hagrid fct: [ID 132490 kern.notice] NOTICE: qlt1,0 > LINK UP, portid 20300, topology Fabric Pt-to-Pt,speed 8G May 17 > 17:33:48 hagrid fct: [ID 132490 kern.notice] NOTICE: qlt0,0 LINK UP, > portid 10400, topology Fabric Pt-to-Pt,speed 8G Seeing a single LINKUP notice would normally only occur on init. I would say it's just that, otherwise you would have a LINKDOWN before the LINKUP, meaning an event on the fabric is your root issue. Stmf service? Nothing at all in the logs OK Are you running snapshots?yes am running auto snapshot service, in addition I'm running a script (hourly) that snapshots the volume and send it over ssh to another machine. I suspect an issue here. The snapshot service runs on fixed time intervals e.g. 15Min 1Hour 24Hhour 1Month if your also adding a snapshot that runs hourly to do a ZFS send/rec they will overlap. The overlap may cause an excessive blocking to stmf sbd access and result in a timeout for the XEN host initiators. I suggest you use the auto based existing hourly snaps and simply send them over to the remote host or file system using a script @ 15 minutes after the hour. Dedup? Off - OK Compression? Lzjb - OK IRQ sharing? echo ::interrupts | mdb -k IRQ Vect IPL BusTrg Type CPU Share APIC/INT# ISR(s) 10x41 5 ISAEdg Fixed 3 1 0x0/0x1 i8042_intr 30xb1 12 ISAEdg Fixed 39 1 0x0/0x3 asyintr 40xb0 12 ISAEdg Fixed 38 1 0x0/0x4 asyintr 50xb2 12 ISAEdg Fixed 40 1 0x0/0x5 asyintr 90x80 9 PCILvl Fixed 1 1 0x0/0x9 acpi_wrapper_isr 12 0x42 5 ISAEdg Fixed 4 1 0x0/0xc i8042_intr 16 0x83 9 PCILvl Fixed 7 2 0x0/0x10 ohci_intr, ohci_intr 17 0x81 9 PCILvl Fixed 5 1 0x0/0x11 ehci_intr 18 0x84 9 PCILvl Fixed 8 3 0x0/0x12 ohci_intr, ohci_intr, ohci_intr 19 0x82 9 PCILvl Fixed 6 1 0x0/0x13 ehci_intr 22 0x40 5 PCILvl Fixed 2 2 0x0/0x16 ata_intr, ata_intr 88 0x43 5 PCIEdg MSI-X 9 1 - ql_isr_aif 89 0x44 5 PCIEdg MSI-X 10 1 - ql_isr_aif 90 0x45 5 PCIEdg MSI-X 11 1 - ql_isr_aif 91 0x46 5 PCIEdg MSI-X 12 1 - ql_isr_aif 92 0x60 6 PCIEdg MSI-X 13 1 - igb_intr_tx_other 93 0x61 6 PCIEdg MSI-X 14 1 - igb_intr_rx 94 0x62 6 PCIEdg MSI-X 15 1 - igb_intr_tx_other 95 0x63 6 PCIEdg MSI-X 16 1 - igb_intr_rx 96 0x64 6 PCIEdg MSI-X 36 1 - igb_intr_tx_other 97 0x65 6 PCIEdg MSI-X 37 1 - igb_intr_rx 98 0x66 6 PCIEdg MSI-X 41 1 - igb_intr_tx_other 99 0x67 6 PCIEdg MSI-X 42 1 - igb_intr_rx 100 0x68 6 PCIEdg MSI-X 43 1 - igb_intr_tx_other 101 0x69 6 PCIEdg MSI-X 44 1 - igb_intr_rx 102 0x6a 6 PCIEdg MSI-X 45 1 - igb_intr_tx_other 103 0x6b 6 PCIEdg MSI-X 46 1 - igb_intr_rx 104 0x47 5 PCIEdg MSI30 1 - qlt_isr 105 0x48 5 PCIEdg MSI31 1 - qlt_isr 160 0xa0 0 Edg IPIall 0 - poke_cpu 208 0xd0 14 Edg IPIall 1 - kcpc_hw_overflow_intr 209 0xd1 14 Edg IPIall 1 - cbe_fire 210 0xd3 14 Edg IPIall 1 - cbe_fire 240 0xe0 15 Edg IPIall 1 - xc_serv 241 0xe1 15 Edg IPIall 1 - apic_error_intr OK Dr T Adrian Carpenter Reader in Imaging Sciences Wolfson Brain Imaging Centre ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ZFS restore from snapshot
I would suggest you run a zpool scrub. -Original Message- From: Jay Heyl [mailto:j...@frelled.us] Sent: Saturday, June 02, 2012 11:15 PM To: Discussion list for OpenIndiana Subject: [OpenIndiana-discuss] ZFS restore from snapshot I have a file that shows as corrupted in the live file system and two snapshots. The file gives every indication of being valid in earlier snapshots. I've tried to restore it from the good snapshot but it doesn't seem to want to take. After several failed attempts to copy directly from the snapshot, I copied from the snapshot to my home directory. That copy appears to be good. (It's an image file and the image comes up fine.) I've deleted the file from the live directory and it seems to disappear. But every time I copy the file from my home directory into the target directory, the target directory copy appears corrupted. With most other file systems I'd suspect this indicates a problem with the directory rather than with the actual file, but I don't know enough about zfs to judge whether this makes sense or not. Any ideas what might be going on with this file and how I can get it restored from the good snapshot? The other odd thing, not directly related to getting it restored, is that neither the file nor the directory it's in has been purposely changed since the time of the good snapshot. Obviously something changed or there wouldn't be any difference between the live version and the snapshot, but I'm bewildered about how it might have happened. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What happens when a ZIL drive dies?
Everything you asked seems to be fully covered by our community. Just wanted to add the following; Not all SSDs are made for slog usage. Be aware that low end (and even some high endones) SSDs may not successfully commit a write operation to the flash write cell address boundary due to a power loss event. At a minimum the use of a UPS is advisable or SSDs that guaranty complete write operations in the event of a power loss. -Original Message- From: Nick Hall [mailto:darknovan...@gmail.com] Sent: Monday, June 04, 2012 10:25 AM To: OpenIndiana-discuss@openindiana.org Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies? I'm considering buying a separate SSD drive for my ZIL as I do quite a bit over NFS and would like the latency to improve. But first I'm trying to understand exactly how the ZIL works and what happens in case of a problem. I'll list my understanding here, and I'm hoping someone can correct me if I'm understanding this incorrectly: - In normal operation, the ZIL drive would just be written to but never read from. - In the case of a power failure, the ZIL will probably contain 5-10 seconds (maybe up to 30 seconds) worth of writes that didn't make it onto the main hard drives. The next time the system boots, ZFS will use what's in the ZIL to bring the main hard drives up to date. - I'm running ZFS version 28 -- in this version, if the ZIL drive were to die while the system were running, the system would switch back to using the main pool hard drives to store the ZIL, just as it currently does since I have no separate ZIL drive right now. So, now I have a couple of questions: - If the ZIL drive were to die while the system were running, I'm assuming no data would be lost? In order for this to work, the system would need to cache everything in the ZIL in RAM, so if the ZIL were to die, it would write the transactions that were on the ZIL from RAM to the main pool drives. Applications would not notice anything from their perspective. Is this what happens? - So far, assuming I'm understanding this correctly, none of the above scenarios involve any data loss. The scenario I can think of that would involve data loss is if there's a power failure and the ZIL drive at the same time. It seems likely that this scenario would be caused by a catastrophic hardware failure, and the main system drives would also die, but let's pretend that only the ZIL drive is affected. So any transactions stored in the ZIL are lost. I'm thinking that the system would boot up, note that the ZIL drive is dead and switch the ZIL back to the main pool drives, and the last 5-30 seconds or writes would be lost forever. But would the system be in a consistent state, that is, things would be the same as if you went back in time 30 seconds before the system died and just pulled the plug? So there's no corruption, just the loss of those seconds of data? - Are there any other scenarios I'm not thinking, specifically any other scenarios that would cause corruption or loss of data? My use is for a home server -- I would like higher NFS write performance, but not by making it more likely I have corrupted or majorly lost data, but for my use, if I only lost the last few seconds or writes and things were in a consistent state, it would be of little consequence. I understand that for a commercial server that would be huge issue, though, as banking transactions lost or something would be a major problem. Thanks. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows regularlyhangs.
Does the suspend event only occur on SMB clients or does it impact the
other storage clients when triggered by the Windows clients?
Any domain controller event errors?
dmsg output?
fmdump -eV output?
uname -a output?
Have you attempted a packet capture of the event?
snoop -o smb-client.cap
-Original Message-
From: John McEntee [mailto:jmcen...@stirling-dynamics.com]
Sent: Tuesday, June 12, 2012 8:52 AM
To: Discussion list for OpenIndiana
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows
regularlyhangs.
I am having problems with a openindiana storage server I have built am I
am trying to track down the cause to fix it. The current symptoms are
seen from all windows clients (both 7 and XP) that will report an error
stating.
Path File is not accessible. The specified network name is no longer
available.
Another symptom is windows explorer hangs and the user has to wait for
it to some back.
Just waiting a while ( a few minutes) and the box comes back.
I currently think the root cause is in openindiana somewhere but am at
a bit of a loss. I have tried many things and have still not fixed it. I
think the box is lightly loaded for the hardware spec but kernel load
increases to 40% when a zfssnap is taking place.
Hardware spec.
2 x Xeon E6520 cpus
48 GB RAM
Intel HC5520 motherboard
3 x LSI SAS 9211-8i cards
Currently on openindiana 148
The box is joined to a windows 2003 domain.
Zpool tank is 3 way mirror of 7 x 3TB hitachi disk (using 21 disks in
total,
zpool size of 19 TB, ) with 2 x SSD 8GB ZIL on each and 140GB L2ARC
on
each, default checksum, no dedup and no compression.
Server operates as a windows home directory for 58 users (some laptops
users so just a backup location), a main shared drive for the company of
120 users.
It is also a nfs server to a vmware vsphere 4 server hosting 10 virtual
machines.
There are only 8 active production file systems, and 12 backup file
systems from other hosts (done out of hours).
Zpool iostat peaks at about 35 MB for the pool mostly around the 0 to 7
MB level.
Turning of time-sliderd does not stop the problem. (backups run out of
hours)
A dtrace -n 'sched:::off-cpu { @[execname]=count()}'
Used to give a sched count in the 6 to 7 fiqures over 3 seconds, but
turing apci off with
#eeprom acpi-user-options=0x8
Reduced this to 5 figures.
What can I do to identify the problem to be able to fix it?
Thanks
John
Other information:
dtrace -n 'sched:::off-cpu { @[execname]=count()}'
dtrace: description 'sched:::off-cpu ' matched 3 probes
^C
gconfd-2 2
idmapd2
inetd 2
nscd 2
sendmail 2
svc.startd2
gnome-power-mana 3
fmd 4
sshd 4
devfsadm 6
fsflush 7
nfsmapid 7
ntpd 7
dtrace 13
Xorg 17
gdm-simple-greet 17
svc.configd 71
smbd113
time-sliderd138
zpool-rpool 597
nfsd918
zpool-tank 1968
sched 80542
# echo hz/D | sudo mdb -k
hz:
hz: 100
# echo apic_timer::print apic_timer_t | sudo mdb -k
{
mode = 0
apic_timer_enable_ops = oneshot_timer_enable
apic_timer_disable_ops = oneshot_timer_disable
apic_timer_reprogram_ops = oneshot_timer_reprogram
}
___
The contents of this e-mail and any attachment(s) are strictly
confidential and are solely for the person(s) at the e-mail address(es)
above. If you are not an addressee, you may not disclose, distribute,
copy or use this e-mail, and we request that you send an e-mail to
ad...@stirling-dynamics.com and delete this e-mail. Stirling Dynamics
Ltd. accepts no legal
Re: [OpenIndiana-discuss] Access to ZFS viz CIFS fromwindows regularlyhangs.
> Does the suspend event only occur on SMB clients or does it impact the other storage clients when triggered by the Windows clients? It does not seem to effect the vmware hosted machines via nfs. Next time it hangs I will try a nfs transfer to it. - If this is correct its a further indication of an AD/SMB issue, but not verified at this point. > Any domain controller event errors? Yes there are, I will go and resolve this first before I go any further. - Highly suspect this is where you need to focus. - This error is suspicious and does look like a issue on the domain. - Jun 12 11:26:07 ringwood smbd[6032]: [ID 702911 daemon.notice] smbd_dc_update: stirling-dynamics.com: located red - Jun 12 11:34:17 ringwood smbd[6032]: [ID 702911 daemon.error] smbrdr_exchange[4]: failed (INVALID_HANDLE) - I would look further back in time and see if it correlates with the suspended access event. That would define a clear resolution path. > dmsg output? Attached - is this the correct etiquette? - Jun 11 21:38:18 ringwood fmd: [ID 377184 daemon.error] SUNW-MSG-ID: SMF-8000-YX, TYPE: defect, VER: 1, SEVERITY: major - Jun 11 21:38:18 ringwood EVENT-TIME: Mon Jun 11 21:38:18 BST 2012 - Jun 11 21:38:18 ringwood PLATFORM: S5520HC, CSN: , HOSTNAME: ringwood - Jun 11 21:38:18 ringwood SOURCE: software-diagnosis, REV: 0.1 - Jun 11 21:38:18 ringwood EVENT-ID: cc9f2029-a779-cbd2-e425-8ffbaa19f639 - Jun 11 21:38:18 ringwood DESC: A service failed - a method is failing in a retryable manner but too often. - Jun 11 21:38:18 ringwood Refer to http://sun.com/msg/SMF-8000-YX for more information. - Jun 11 21:38:18 ringwood AUTO-RESPONSE: The service has been placed into the maintenance state. - Jun 11 21:38:18 ringwood IMPACT: svc:/application/time-slider:default is unavailable. - The time slider snapshot service failed? Or was it stopped manually? > fmdump -eV output? Also attached. - Nothing remarkable > uname -a output? SunOS ringwood 5.11 oi_148 i86pc i386 i86pc Solaris > Have you attempted a packet capture of the event? > snoop -o smb-client.cap Not yet, It could be caputureing for 4 hours before it happens, I will resolve the AD domain issue first. - Good approach. 4 hours of packet tracing is hard to digest! It would certainly need to be truncated down to the trigger event. - Mike ___ The contents of this e-mail and any attachment(s) are strictly confidential and are solely for the person(s) at the e-mail address(es) above. If you are not an addressee, you may not disclose, distribute, copy or use this e-mail, and we request that you send an e-mail to ad...@stirling-dynamics.com and delete this e-mail. Stirling Dynamics Ltd. accepts no legal liability for the contents of this e-mail including any errors, interception or interference, as internet communications are not secure. Any views or opinions presented are solely those of the author and do not necessarily represent those of Stirling Dynamics Ltd. Registered In England No. 2092114 Registered Office: 26 Regent Street, Clifton, Bristol. BS8 4HG VAT no. GB 464 6551 29 ___ This e-mail has been scanned for all viruses MessageLabs. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Very simple network speed testing tools inOpenIndiana?
You may want to look at http://www.speedtest.net/mini.php -Original Message- From: Hans J. Albertsson [mailto:hans.j.alberts...@branneriet.se] Sent: Monday, June 18, 2012 5:44 AM To: Discussion list for OpenIndiana Subject: [OpenIndiana-discuss] Very simple network speed testing tools inOpenIndiana? Are there any network testing tools that would be suitable to put in the hands of people with little or no real understanding of computers? I'm hoping for some (Web??)server package with client tools for Windows, Linux and Mac, or for any web browser. And I'm hoping for a single-click test to check for speed both ways, possibly response times, latency and variations in performance. I don't want to visit all 1400 residents to test their network connections. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] intermittent network? (rge device)
I have one system running an rge card. No issues at all, it's running 2 years now with 134 through 151a4. It a storage server and it's running light to medium load. What else do you have configured? NWAM? Layer 2 dladm elements? dmesg output? Does snoop reveal anything when it goes unresponsive? Shared irqs? echo ::interrupts | pfexec mdb -k pfexec intrstat seem normal during the event? -Original Message- From: ramble1035 @dslextreme.com [mailto:ramble1...@dslextreme.com] Sent: Sunday, June 17, 2012 3:16 PM To: Discussion list for OpenIndiana Subject: [OpenIndiana-discuss] intermittent network? (rge device) I've got a small PC with two rge networking interfaces (one on the motherboard, one on a separate pcie card). I'm seeing some intermittently flakey behavior, where the network just stops talking. Looking at it seems to indicate things are alive and well, and my internal LAN switch shows a hardware connection but no activity. This last episode, I experienced: a completely unresponsive local net connection on rge0 ifconfig showed correct values (possibly left over from when it *was* working) ping out got nothing ping in got request timeouts and no route to host errors the other network interface worked fine netstat -r produced (eventually) a routing table with a correct default route, but it took a while. a reboot produced a "failure to plumb rge0" message on the console a physical power cycle brought everything up just fine. It's all currently working as expected. Has anyone experienced intermittent network outages? Is it possible there are some issues with the rge driver? Are there any things I can try to identify an error condition and/or reset the network by hand? Thanks - -- C ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] recognizing disks
Hi Adam, Possibly the LSI controller was not matched to a driver. Check the controller model and verify it is on the HCL. Run: pfexec prtconf | grep driver to observer any devices that are not bound to a driver. http://illumos.org/hcl/ Typically I have found that the some RAID mode firmware within LSI cards and other vendors is not always compatible or matched to a driver. For example I have an IBM (LSI 1068) branded adaptor. It works fine when I load the Initiator/Target mode firmware image but not when it's running the RAID firmware image. Regards, Mike http://blog.laspina.ca/ -Original Message- From: Adam Gold [mailto:a...@gmx.com] Sent: Sunday, June 24, 2012 9:28 AM To: openindiana-discuss@openindiana.org Subject: [OpenIndiana-discuss] recognizing disks Hi there. I'm a linux user and have recently decided to switch to OpenIndiana using a x86_64 server. Somewhat embarrassingly I'm seem to be falling at one of the early hurdles. My server has 1 SSD where the O/S has been successfully installed and 4 X 3TB hard drives managed by an LSI RAID controller. I have configured the hard drives as JBOD so I can use ZFS with all its capabilities. Having booted up for the first time I ran 'format -e' but the 4 hard drives were not detected. Likewise when using 'cfgadm -alv' and 'devfsadm' + 'format' there was no sign of any unconfigured drives. Just to be sure there wasn't any legacy data/meta-data I booted to a rescue disk and erased the GPT labels at the beginning and end of the 3TB disks using 'dd'. Again no luck. These drives have always showed up automatically under linux so I'm wondering if I'm making some very obvious starting error with the new O/S, perhaps to do with labelling (although now there really are no labels) or something. I'm posting in the hope that this may be quickly apparent to veteran users (and apologies for the relatively trivial level of the inquiry). Thanks in advance for any responses. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] recognizing disks
Adam, As I suspected it did not find a driver match. There is a Solaris driver available from LSI for that card. pci1000,9240 (driver not attached) Try http://www.lsi.com/channel/products/storagecomponents/Pages/MegaRAIDSAS9 240-8i.aspx Or http://www.byte.nl/blog/2011/01/04/how-to-install-opensolaris-openindian a-on-an-m1015-lsi-9240-raid-controller/ Regards, Mike -Original Message- From: Adam Gold [mailto:a...@gmx.com] Sent: Sunday, June 24, 2012 12:15 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] recognizing disks Mike, Thanks a lot for the response. The controller model is LSI 9240-8i. I ran the command and received the following output: * pci15d9,6 (driver not attached) pci8086,3408 (driver not attached) pci8086,340a (driver not attached) pci8086,340e (driver not attached) pci1000,9240 (driver not attached) pci8086,342d (driver not attached) pci8086,342e (driver not attached) pci8086,3422 (driver not attached) pci8086,3438 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) input, instance #4 (driver not attached) motherboard (driver not attached) asy, instance #0 (driver not attached) asy, instance #1 (driver not attached) motherboard (driver not attached) ide (driver not attached) pci15d9,6 (driver not attached) ide (driver not attached) ioapics (driver not attached) ioapic, instance #0 (driver not attached) used-resources (driver not attached) agpgart, instance #0 (driver not attached) * I'm guessing it's one of the pci drivers - any pointers (or questions I can answer to help narrow it down). Also, am I correct in saying the loading of the Initiator/Target mode firmware image should be done in the BIOS before the O/S has loaded? Thanks for your help. Regards, Adam On 24 Jun 2012, at 17:24, Mike La Spina wrote: > Hi Adam, > > Possibly the LSI controller was not matched to a driver. Check the > controller model and verify it is on the HCL. > > Run: > > pfexec prtconf | grep driver > > to observer any devices that are not bound to a driver. > > > http://illumos.org/hcl/ > > Typically I have found that the some RAID mode firmware within LSI > cards and other vendors is not always compatible or matched to a driver. > For example I have an IBM (LSI 1068) branded adaptor. It works fine > when I load the Initiator/Target mode firmware image but not when it's > running the RAID firmware image. > > Regards, > Mike > > http://blog.laspina.ca/ > > > -Original Message- > From: Adam Gold [mailto:a...@gmx.com] > Sent: Sunday, June 24, 2012 9:28 AM > To: openindiana-discuss@openindiana.org > Subject: [OpenIndiana-discuss] recognizing disks > > Hi there. I'm a linux user and have recently decided to switch to > OpenIndiana using a x86_64 server. Somewhat embarrassingly I'm seem > to be falling at one of the early hurdles. My server has 1 SSD where > the O/S has been successfully installed and 4 X 3TB hard drives > managed by an LSI RAID controller. I have configured the hard drives > as JBOD so I can use ZFS with all its capabilities. > > Having booted up for the first time I ran 'format -e' but the 4 hard > drives were not detected. Likewise when using 'cfgadm -alv' and > 'devfsadm' + 'format' there was no sign of any unconfigured drives. > Just to be sure there wasn't any legacy data/meta-data I booted to a > rescue disk and erased the GPT labels at the beginning and end of the > 3TB disks using 'dd'. Again no luck. > > These drives have always showed up automatically under linux so I'm > wondering if I'm making some very obvious starting error with the new > O/S, perhaps to do with labelling (although now there really are no > labels) or something. I'm posting in the hope that this may be > quickly apparent to veteran users (and apologies for the relatively > trivial level of the inquiry). Thanks in advance for any responses. > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > > ___ > OpenIndiana-discuss mailing lis
Re: [OpenIndiana-discuss] recognizing disks
Adam, There is a possibility that the existing mega_sas driver will work correctly out of the box. Can't verify it for you but there are some simple ways to invoke a detection and or direct binding. The Initiator/Target mode can be applied using a utility from LSI. It can also be applied from a Linux/Windows OS etc. 1: Add the alias to /etc/driver_alias Edit the file and directly after this line: driver name=mega_sas class=scsi \ Add the following pci id strings - most likely the first one: alias=pci1000,0073.9240.1000 \ alias=pci1000,0073.3035.1054 \ alias=pci1000,0073.1054.1000 \ alias=pci1000,0073.1458.1002 \ 2: Or directly binding it with drv_add pfexec add_drv -i '"pci1000,73"' mega_sas -Original Message- From: Adam Gold [mailto:a...@gmx.com] Sent: Sunday, June 24, 2012 12:15 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] recognizing disks Mike, Thanks a lot for the response. The controller model is LSI 9240-8i. I ran the command and received the following output: * pci15d9,6 (driver not attached) pci8086,3408 (driver not attached) pci8086,340a (driver not attached) pci8086,340e (driver not attached) pci1000,9240 (driver not attached) pci8086,342d (driver not attached) pci8086,342e (driver not attached) pci8086,3422 (driver not attached) pci8086,3438 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) pci15d9,6 (driver not attached) input, instance #4 (driver not attached) motherboard (driver not attached) asy, instance #0 (driver not attached) asy, instance #1 (driver not attached) motherboard (driver not attached) ide (driver not attached) pci15d9,6 (driver not attached) ide (driver not attached) ioapics (driver not attached) ioapic, instance #0 (driver not attached) used-resources (driver not attached) agpgart, instance #0 (driver not attached) * I'm guessing it's one of the pci drivers - any pointers (or questions I can answer to help narrow it down). Also, am I correct in saying the loading of the Initiator/Target mode firmware image should be done in the BIOS before the O/S has loaded? Thanks for your help. Regards, Adam On 24 Jun 2012, at 17:24, Mike La Spina wrote: > Hi Adam, > > Possibly the LSI controller was not matched to a driver. Check the > controller model and verify it is on the HCL. > > Run: > > pfexec prtconf | grep driver > > to observer any devices that are not bound to a driver. > > > http://illumos.org/hcl/ > > Typically I have found that the some RAID mode firmware within LSI > cards and other vendors is not always compatible or matched to a driver. > For example I have an IBM (LSI 1068) branded adaptor. It works fine > when I load the Initiator/Target mode firmware image but not when it's > running the RAID firmware image. > > Regards, > Mike > > http://blog.laspina.ca/ > > > -Original Message- > From: Adam Gold [mailto:a...@gmx.com] > Sent: Sunday, June 24, 2012 9:28 AM > To: openindiana-discuss@openindiana.org > Subject: [OpenIndiana-discuss] recognizing disks > > Hi there. I'm a linux user and have recently decided to switch to > OpenIndiana using a x86_64 server. Somewhat embarrassingly I'm seem > to be falling at one of the early hurdles. My server has 1 SSD where > the O/S has been successfully installed and 4 X 3TB hard drives > managed by an LSI RAID controller. I have configured the hard drives > as JBOD so I can use ZFS with all its capabilities. > > Having booted up for the first time I ran 'format -e' but the 4 hard > drives were not detected. Likewise when using 'cfgadm -alv' and > 'devfsadm' + 'format' there was no sign of any unconfigured drives. > Just to be sure there wasn't any legacy data/meta-data I booted to a > rescue disk and erased the GPT labels at the beginning and end of the > 3TB disks using 'dd'. Again no luck. > > These drives have always showed up automatically under linux so I'm > wondering if I'm making some very obvious starting error with the new > O/S, perhaps to do with labelling (although now there really are no > labels) or something. I'm posting in the hope that this may be > quickly apparent to veteran use
Re: [OpenIndiana-discuss] Diagnosis help needed
I have observed the same SATA hard disk error wait behavior over many operating systems. It's a SATA hardware issue. I have even observed it on expensive high end storage servers. (HP, IBM, etc.) The SATA disk or subsystem is trying to correct/recover errors, it should not and just return the fault back to the caller (ZFS in this case). It can handle the issue much more diplomatically and will correct the data fault immediately. Don't blame ZFS, it is well designed, SATA on the other hand is trying hard to do a bad thing. -Original Message- From: michelle [mailto:miche...@msknight.com] Sent: Monday, June 25, 2012 2:31 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] Diagnosis help needed I did a hard reset and moved the drive to another channel. The fault followed the drive so I'm certain it is the drive, as people have said. The thing that bugs me is that this ZFS fault locked up the OS - and that's a real concern. I think I'm going to need to have a hard think about my options and possibly leave OI for FreeNAS, Nexenta or Schillix. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Diagnosis help needed
The error reported task_file_status = 0x4041 on port 3 is a result of an ATA response where the PxIS.TFES bit was set. The ahci driver must do a port reset at that point. The SATA disk failed to perform an operation and reported it. I suspect this is not a data error and may be more on the lines of a firmware fault on the SATA controller. So it may well be a faulty disk in the most unruly way, that is conditional e.g. could be anything around or on the ATA chain, a bad cable, running to hot, interference, mobo firmware ... etc. -Original Message- From: michelle [mailto:miche...@msknight.com] Sent: Monday, June 25, 2012 7:34 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] Diagnosis help needed Apologies, This went to an individual rather than back to the group. Thanks for the response. The thing that set of major alarms in my head is the fact that these errors caused OI to freeze up to the degree where it needed to be powered off. It would acknowledge the power switch instruction, but wouldn't power down. Messages is full of ... Jun 24 21:20:58 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0: ahci port 3 has task file error Jun 24 21:20:58 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0: ahci port 3 is trying to do error recovery Jun 24 21:20:58 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0: ahci port 3 task_file_status = 0x4041 Jun 24 21:21:00 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0: error recovery for port 3 succeed The fmdump gives loads of ... Jun 25 2012 17:20:59.709529495 ereport.fs.zfs.probe_failure nvlist version: 0 class = ereport.fs.zfs.probe_failure ena = 0x9af81a688900c01 detector = (embedded nvlist) nvlist version: 0 version = 0x0 scheme = zfs pool = 0xb4f18a4cb65803ce vdev = 0xe8c24676aa3c2a12 (end detector) pool = data pool_guid = 0xb4f18a4cb65803ce pool_context = 0 pool_failmode = wait vdev_guid = 0xe8c24676aa3c2a12 vdev_type = disk vdev_path = /dev/dsk/c2t3d0s0 vdev_devid = id1,sd@SATA_WDC_WD20EARS-00M_WD-WMAZA075/a parent_guid = 0x394c2bd12b4ffcfc parent_type = raidz prev_state = 0x0 __ttl = 0x1 __tod = 0x4fe88feb 0x2a4a8f97 iostat gives... mich@jaguar:~# iostat -Exn extended device statistics r/sw/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 0.11.13.48.4 0.0 0.00.50.5 0 0 c2t0d0 0.11.13.58.4 0.0 0.00.50.5 0 0 c2t1d0 332.16.6 29970.5 65.3 0.1 2.60.27.7 2 39 c2t2d0 261.36.6 23380.2 61.2 0.5 4.41.8 16.3 8 68 c2t3d0 373.47.8 29970.7 65.2 0.1 2.90.37.6 2 47 c2t4d0 c2t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: ATA Product: INTEL SSDSA2M040 Revision: 02HB Serial No: CVGB949301PH040 Size: 40.02GB <40020664320 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 36 Predictive Failure Analysis: 0 c2t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: ATA Product: INTEL SSDSA2M040 Revision: 02HB Serial No: CVGB949301PC040 Size: 40.02GB <40019582464 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 35 Predictive Failure Analysis: 0 c2t2d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: ATA Product: ST32000542AS Revision: CC34 Serial No: 5XW17ARW Size: 2000.40GB <2000398934016 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 36 Predictive Failure Analysis: 0 c2t3d0 Soft Errors: 0 Hard Errors: 795 Transport Errors: 0 Vendor: ATA Product: WDC WD20EARS-00M Revision: AB51 Serial No: WD-WMAZA075 Size: 2000.40GB <2000398934016 bytes> Media Error: 370 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 70 Predictive Failure Analysis: 0 c2t4d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: ATA Product: WDC WD20EARS-00M Revision: AB51 Serial No: WD-WMAZA0484508 Size: 2000.40GB <2000398934016 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 36 Predictive Failure Analysis: 0 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] "shareiscsi" and COMSTAR
Hi Jim, >1) Is COMSTAR still not-integrated with shareiscsi ZFS attributes? >Or can the pool use the attribute, and the correct (new COMSTAR) >iSCSI target daemon will fire up? COMSTAR is not integrated with ZFS and it will ignore the ZFS props. What is the release of the old host OS? I strongly suggest you record the old iqn target names and the LU's they are mapped to, as well the LU GUID is helpful. Snapshots on zvols are your friends! >2) What would be the best way to migrate iSCSI server configuration >(LUs, views, allowed client lists, etc.) - is it sufficient to >just export the SMF config of "stmf" service, or do I also need >some other services and/or files (/etc/iscsi, something else?) This really depends on your current configuration .. can you provide some specifics of the existing targets/initiators? Mike http://blog.laspina.ca Thanks, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] "shareiscsi" and COMSTAR
2012-06-27 4:51, Mike La Spina wrote: >> Hi Jim, >> >>> 1) Is COMSTAR still not-integrated with shareiscsi ZFS attributes? >>> Or can the pool use the attribute, and the correct (new COMSTAR) >>> iSCSI target daemon will fire up? >> >> COMSTAR is not integrated with ZFS and it will ignore the ZFS props. > >Well, that was the case a couple of years ago when we played with the newly released COMSTAR. We did not know whether the progress marched on (to integrate ZFS >with COMSTAR) - hence the questions ;) > >> What is the release of the old host OS? > > >SXCE snv_117... Well, it may be more than a couple of years :) Yes very early COMSTAR code :) >> >> I strongly suggest you record the old iqn target names and the LU's >> they are mapped to, as well the LU GUID is helpful. > >Probably so, if only to check that the SMF/file-based config migration attempt went well. > >> Snapshots on zvols are your friends! > >Unfortunately, they are not. The OS upgrade is part of the box's migration to larger new drives, and so far it is very restrained on free disk space in the pool. >ZVOL snapshots reserve the zvol size so as to guarantee the ability to rewrite the whole zvol contents safely, and the box can not afford that much wasted space. >Ability to do these snapshots is indeed one of the many reasons for the overall upgrade (HW+SW). Then I would at minimum suggest a VM VMFS file level backup outside the storage host scope. Other option is to thin it out and free up that unused space then snapshot it. zfs set refreservation=none pool/esx/vol0 >> >> >>> 2) What would be the best way to migrate iSCSI server configuration >>> (LUs, views, allowed client lists, etc.) - is it sufficient to >>> just export the SMF config of "stmf" service, or do I also need >>> some other services and/or files (/etc/iscsi, something else?) >> >> This really depends on your current configuration .. can you provide >> some specifics of the existing targets/initiators? > >The targets are now a few zvols on the snv_117 box, served by COMSTAR (svc:/system/stmf:default, svc:/network/iscsi/target:default). >The service svc:/network/iscsi/initiator:default is also online, but it was AFAIK used for testing and does not normally attach remote LUNs. > >Initiators that I know of are from free ESXi hosts, I'm uncertain about the version. It's fairly strait forward. You have two possible options. 1) Backup the manifest method. "It will migrate every property and attribute, be it good or bad for the new COMSTAR code" "Suggest you look at and keep a diff on the manifest files" "I have used this successfully from snv_134 to snv_148"" On the old host: svccfg export -a stmf > stmf.cfg note the -a parm "It will include the LU info and other elements." if your moving the pool vdevs or creating a clean OS image with importing (otherwise in-place = done) On the new host: svccfg export -a stmf > original-stmf.cfg svcadm disable stmf svccfg delete stmf svccfg import stmf.cfg svcadm refresh stmf svcadm enable stmf 2) Recreate the stmf properties method. "Need to ensure your LU numbers are correct before the ESX host scans them or you may have serious VMFS problems" "Ensures a healthy clean stmf manifest" "If you have more than one interface with an IP bound you should define which IP(s) should be associated to the target using a portal group." itadm create-tpg tpg1 ip? (assign the appropriate interfaces) itadm create-target previous.target.iqn.name -t tpg1 itadm create-initatitor esx.iqn.initiator.name stmfadm create-hg esx1 stmfadm add-hg-member -g esx1 esx.iqn.initiator.name stmfadm import-lu /dev/zvol/rdsk/sp/store0/vol0 stmfadm add-view -n lu# lu-naa ... Regards, Mike ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Office apps unable to write to ZFS overCIFS
There are some key elements missing from the presented Oracle document clip. e.g. *The primary rules of ACL access on a ZFS file follow: *ZFS processes ACL entries in the order they are listed in the ACL, from the top down. *Only ACL entries that have a "who" that matches the requester of the access are processed. *After an allow permission has been granted, it cannot be denied by a subsequent ACL deny entry in the same ACL permission set. *The owner of a file is granted the write_acl permission unconditionally, even if the permission is explicitly denied. Otherwise, any permission left unspecified is denied. *In cases of deny permissions or when an access permission for a file is missing, the privilege subsystem determines what access request is granted for the owner of the file or for superuser. This mechanism prevents owners of files from getting locked out of their files and enables superuser to modify files for recovery purposes. ACLs are processed primarily on the explicit entries first. Any explicit ACE will be acted on and will override an inherited one. This follows Microsoft defined rules for processing ACLs. The statement indicating "who" matches is the key definition of explicit. So in the case of an inherited permission the explicit deny will have precedence provided that the are no other explicit allow ACEs processed before it. http://technet.microsoft.com/en-us/library/cc783530(WS.10).aspx -Original Message- From: Gordon Ross [mailto:gordon.w.r...@gmail.com] Sent: Saturday, June 30, 2012 11:15 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] Office apps unable to write to ZFS overCIFS On Sat, Jun 30, 2012 at 7:00 PM, Martin Frost wrote: > Thanks to all for the replies. The Oracle Solaris documentation here: > > http://docs.oracle.com/cd/E19253-01/819-5461/ftyxi/index.html > > says: > > The primary rules of ACL access on a ZFS file follow: > > * ZFS processes ACL entries in the order they are listed > in the ACL, from the top down. > > * After an allow permission has been granted, it cannot be denied > by a subsequent ACL deny entry in the same ACL permission set. Interesting. That's not how MS defined the ACL evaluation algorithm. I thought the point of NFSv4/ZFS ACLs was to be Windows compatible, so I wonder if this was an intentional difference or an accident? (bug) -- Gordon Ross Nexenta Systems, Inc. www.nexenta.com Enterprise class storage for everyone ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Help debugging and replacing failed (maybe)hard drive
Some things to consider. Generally a RAID controller that is in virtual RAID0 presentation mode can hide a problem drive from ZFS. e.g. Just places the virtual drive offline. You need to make sure it's really dead. Without access to the PERC Raid management interface/app you may be out of luck when it comes to placing the virtual drive back online with or without a replacement disk. The controller tracks what state and ID are presented to the server. Running the PERC BIOS based management/configuration app may be required to correct the current behavior. (One of the many reasons ZFS should drive a JBOD array) Check your device messages Use pfexec dmesg or check /var/adm/messages.? Check the device configuration state Use pfexec cfgadm Once the disk device state is corrected and presuming c3t0d0 was replaced and remains presented as c3t0d0 you can simply issue: pfexec zfs replace c3t0d0 c3t0d0 ZFS will resilver the newly inserted disk since it does not have the missing device vdev signature. Regards, Mike http://blog.laspina.ca -Original Message- From: Wood Peter [mailto:peterwood...@gmail.com] Sent: Tuesday, July 03, 2012 1:54 PM To: OpenIndiana Discuss Subject: [OpenIndiana-discuss] Help debugging and replacing failed (maybe)hard drive Hi, I have OI-151a running on Dell PE R710 with 15 drives MD1000 DAS connected via PERC6/E controller. The controller is configured with 15 RAID0 virtual devices for each hard drive so the OS sees 15 drives. I know it's not ideal but Dell doesn't have a controller that will give direct access to the drives and work with MD1000. Anyway, here is what I found this morning: root@tzstor14:~# zpool status -v pool01 pool: pool01 state: DEGRADED status: One or more devices has been removed by the administrator. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Online the device using 'zpool online' or replace the device with 'zpool replace'. scan: resilvered 71.9G in 0h36m with 0 errors on Sun Jun 24 05:37:43 2012 config: NAME STATE READ WRITE CKSUM pool01 DEGRADED 0 0 0 raidz1-0 DEGRADED 0 0 0 spare-0REMOVED 0 0 0 c3t0d0 REMOVED 0 0 0 c3t14d0 ONLINE 0 0 0 c3t1d0 ONLINE 0 0 0 c3t2d0 ONLINE 0 0 0 c3t3d0 ONLINE 0 0 0 c3t4d0 ONLINE 0 0 0 c3t5d0 ONLINE 0 0 0 c3t6d0 ONLINE 0 0 0 raidz1-1 ONLINE 0 0 0 c3t7d0 ONLINE 0 0 0 c3t8d0 ONLINE 0 0 0 c3t9d0 ONLINE 0 0 0 c3t10d0ONLINE 0 0 0 c3t11d0ONLINE 0 0 0 c3t12d0ONLINE 0 0 0 c3t13d0ONLINE 0 0 0 logs mirror-2 ONLINE 0 0 0 c2t4d0 ONLINE 0 0 0 c2t5d0 ONLINE 0 0 0 cache c2t2d0 ONLINE 0 0 0 c2t3d0 ONLINE 0 0 0 spares c3t14d0 INUSE currently in use errors: No known data errors root@tzstor14:~# There is ton of information on the Internet about zpool failures but it's mostly outdated and in some cases contradicting. I couldn't find anything that applies to my case. - What state "REMOVED" means and why the drive was put in this state? "iostat -En" shows no errors for this drive. I can't find any indication that the drive is bad. - If the drive has to be replaced could somebody please confirm that the following steps are sufficient: * zpool offline pool01 c3t0d0 * zpool detach pool01 c3t0d0 * Physically replace the drive with a new one * zpool add pool01 spare c3t0d0 * zpool scrub pool01 Thank you for any hints and pointers. -- Peter ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Unable to upgrade from OS_snv_134
It may be processing http://pkg.openindiana.org/dev/ first, try removing it for now. I have encountered similar issues with elements that are available in multiple repos. -Original Message- From: M Lubratt [mailto:mplubr...@gmail.com] Sent: Tuesday, July 03, 2012 6:32 PM To: openindiana-discuss@openindiana.org Subject: [OpenIndiana-discuss] Unable to upgrade from OS_snv_134 Hello! I'm trying to upgrade a couple of my machines running OS 134 (and not go the Oracle route). I've followed the directions on the OI website regarding upgrading from OS to OI. It won't upgrade anything beyond 134. Below is a sample of my command and the current version/package publishers. mpl@webdevel:~$ uname -a SunOS webdevel 5.11 snv_134 i86pc i386 i86pc Solaris mpl@webdevel:~$ pfexec pkg publisher PUBLISHER TYPE STATUS URI openindiana.org (preferred) origin online http://pkg.openindiana.org/dev/ opensolaris.org (non-sticky) origin online http://pkg.openindiana.org/legacy/ mpl@webdevel:~$ pfexec pkg image-update -nv Solver: [ Variables: 7408 Clauses: 123032 Iterations: 1 State: Succeeded] Timings: [phase 1: 2.856, phase 2: 0.112, phase 3: 40.958, phase 4: 21.296, phase 5: 0.032] Maintained incorporations: None Package version changes: No updates available for this image. I understand that OI is beyond version 150, but I don't know what to do to upgrade my systems. Any help would be appreciated. Best regards, Mark ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows regularly hangs.
That symptom reflects browser election issues. Workstations should not have the browser service running. Domain controllers are the most appropriate location for browser name services unless it's a small workgroup. Running browsers on many workstations creates browser election storms. -Original Message- From: Bob Friesenhahn [mailto:bfrie...@simple.dallas.tx.us] Sent: Thursday, July 05, 2012 11:12 AM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows regularly hangs. On Thu, 5 Jul 2012, John McEntee wrote: > > I have had the suggestion of moving the samba as a more known quantity > and better logging. At least then I can see if my high kernel usage > (60%) is reduced or not. On my home network I observed that when I turned a Windows XP host off a Windows 7 host declared that it lost access to the Samba service hosted from a Solaris 10 system. It was then able to reconnect to the Samba service on that Solaris 10 system even though the Windows XP host remained turned off. It is a problem that Windows uses random hosts on the network as directory servers and then blames the problem on the host which is actually serving up the data (as if that host was lost) if that random directory server goes away. This behavior seems like it would make dignosing issues more difficult. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Mounting smb IN OI
Checkout http://docs.oracle.com/cd/E19963-01/html/821-1449/smbclientadmintaskstm. html -Original Message- From: michelle [mailto:miche...@msknight.com] Sent: Saturday, July 07, 2012 6:33 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] Mounting smb IN OI On 07/07/12 23:35, Yuri Pankov wrote: > It should be pretty straightforward, e.g. the following works for me: > sirius:root:~# svcadm enable -s idmap > sirius:root:~# svcadm enable -s smb/client sirius:root:~# mount -F > smbfs //yuri@altair/Videos /mnt > Password: > > And now I can browse the CIFS share mount on /mnt... > > Take a look at nsmbrc(4) to automate things a bit. > > HTH > Many thanks, it will help a lot. I'll give it a try in the morning; I'm just wondering how I insert a different user name in there, but I suspect it should be straightforward. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ZFS's vdev state transition
It may be prudent to consider a thermal hardware fault with the suspect disk. In this case it is possible that the disk was at a lower temp at the time the pool was defined to which it may have not exhibited a data fault. Can you confirm the fault occurs when the disk is hot verses cold? Regards, Mike -Original Message- From: Ichiko Sakamoto [mailto:i-sakam...@pb.jp.nec.com] Sent: Friday, July 20, 2012 4:29 AM To: openindiana-discuss@openindiana.org Subject: [OpenIndiana-discuss] ZFS's vdev state transition Hi, all I have a disk that has many bad sectors. I created zpool with this disk and expected that zpool told me the disk has meny errors. But zpool told me everything was fine until I scrubbed the zpool. Is this designed feature? Here's my test result. 1. Create raidz1 zpool. # zpool create -f pool1 raidz c2t4d0 c2t5d0 c2t6d0 c2t5d0 has many bad sectors. 2. Check status and scrub. # zpool status pool: pool1 state: ONLINE scan: none requested config: NAMESTATE READ WRITE CKSUM pool1 ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 c2t4d0 ONLINE 0 0 0 c2t5d0 ONLINE 0 0 0 c2t6d0 ONLINE 0 0 0 errors: No known data errors # zpool scrub pool1 # zpool status pool1 pool: pool1 state: ONLINE scan: scrub repaired 0 in 0h0m with 0 errors on Fri Jul 20 15:58:38 2012 config: NAMESTATE READ WRITE CKSUM pool1 ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 c2t4d0 ONLINE 0 0 0 c2t5d0 ONLINE 0 0 0 c2t6d0 ONLINE 0 0 0 errors: No known data errors 3. OK, write a large file. # dd if=/dev/urandom of=/pool1/file1 bs=$(( 1024 * 1024 )) count=$(( 1024 * 100 )) 102400+0 records in 102400+0 records out 107374182400 bytes (107 GB) copied, 2070.16 s, 51.9 MB/s 4. Check status again. # zpool status pool: pool1 state: ONLINE scan: scrub repaired 0 in 0h0m with 0 errors on Fri Jul 20 15:58:38 2012 config: NAMESTATE READ WRITE CKSUM pool1 ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 c2t4d0 ONLINE 0 0 0 c2t5d0 ONLINE 0 0 0 c2t6d0 ONLINE 0 0 0 errors: No known data errors No READ, WRITE errors. But FMA recv many SCSI layer errors like following TIME CLASS Jul 20 2012 16:33:19.290564446 ereport.io.scsi.cmd.disk.dev.rqs.merr nvlist version: 0 class = ereport.io.scsi.cmd.disk.dev.rqs.merr ena = 0x2227e44a13d01401 detector = (embedded nvlist) nvlist version: 0 version = 0x0 scheme = dev device-path = /pci@0,0/pci8086,340a@3/pci1000,3080@0/sd@5,0 devid = id1,sd@n5000c50026001d17 (end detector) devid = id1,sd@n5000c50026001d17 driver-assessment = fatal op-code = 0x2a cdb = 0x2a 0x0 0x5 0xc3 0x8c 0x8b 0x0 0x1 0x0 0x0 pkt-reason = 0x0 pkt-state = 0x3f pkt-stats = 0x0 stat-code = 0x2 key = 0x3 asc = 0xc ascq = 0x0 sense-data = 0xf0 0x0 0x3 0x5 0xc3 0x8c 0xde 0xa 0x0 0x0 0x0 0x0 0xc 0x0 0x1 0x80 0x0 0x0 0x0 0x0 lba = 0x5c38c8b __ttl = 0x1 __tod = 0x500909bf 0x1151a95e 5. Scrub the zpool to check errors. # zpool scrub pool1 # zpool status pool1 pool: pool1 state: DEGRADED status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://illumos.org/msg/ZFS-8000-9P scan: scrub repaired 8.57M in 0h13m with 0 errors on Fri Jul 20 16:52:28 2012 config: NAMESTATE READ WRITE CKSUM pool1 DEGRADED 0 0 0 raidz1-0 DEGRADED 0 0 0 c2t4d0 ONLINE 0 0 0 c2t5d0 DEGRADED 0 021 too many errors c2t6d0 ONLINE 0 0 0 errors: No known data errors I expected WRITE error was counted and c2t5d0's state changed to FAULTED when I wrote the file. Thanks, Ichiko ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman
Re: [OpenIndiana-discuss] Should I upgrade the pool?
Hi Robert, You do not need to enable the feature flags at this point however you will in the future need to consider the following: You have come to a fork in the road. You can chose one of two directions going forward. 1. Follow the illumos path which is open and has a community. 2. Follow the Horacle path and hold your position with the ability to move back to Solaris ZFS. You are running a home ZFS server so the risk is very small at this point and it's really a question of what you trust. Do you believe that Horacle will bring something to their closed works which could be more appealing than our community based illumos path offers? For example illumos can mount any version of ZFS with feature flags, Express/Solaris cannot. Regards, Mike -Original Message- From: Robert Soubie [mailto:robert.sou...@free.fr] Sent: Friday, August 17, 2012 1:53 PM To: Discussion list for OpenIndiana Subject: [OpenIndiana-discuss] Should I upgrade the pool? Bonjour, I just rebuilt my home ZFS server using openindiana (formerly Solaris Xpress 11) and napp-it, an configured it for Windows or Android clients. The boot pool (rpool) was built by OI's installer; the storage pool (tank, 9GB) was created by napp-it's "create pool" function, using the ashift=12 parameter (6 x WDEARS 1.5Tb disks in RAIDZ2 configuration). So far, everything works, as a couple of thorough tests have shown, and I have restored the whole server from a backup machine I built. Napp-it "dd" benchmarks reports nice figures, 125.02 MB/s Write and 323.88 MB/s Read. However, I have noticed that the pool status report (below) contains a suggestion to upgrade the pool, which is currently v28, which surprises me. Before proceeding, I would like to obtain informed opinions on the matter, including risks on the whole setup, if any. Many thanks for any help, Robert. Below is the information obtained from napp-it: My pools: Root Pool (ashift = 9): rpool5000 16454639525011445801 vdevs: 1 vdev 1: mirror 9 500.07 GB Storage pool (ashift = 12, obtained through napp-it "Create Pool" command): tank28 4308072134310677912 vdevs: 1 vdev 1: raidz2 12 9.00 TB zpool status (obtained from napp-it->jobs->scrub->pool status): pool: rpool state: ONLINE scan: resilvered 6.47G in 0h4m with 0 errors on Wed Aug 15 23:59:44 2012 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0ONLINE 0 0 0 c4t0d0s0 ONLINE 0 0 0 c4t1d0s0 ONLINE 0 0 0 errors: No known data errors pool: tank state: ONLINE status: The pool is formatted using an older on-disk format. The pool can still be used, but some features are unavailable. action: Upgrade the pool using 'zpool upgrade'. Once this is done, the pool will no longer be accessible on older software versions. scan: none requested config: NAMESTATE READ WRITE CKSUM tankONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 c5t0d0 ONLINE 0 0 0 c5t1d0 ONLINE 0 0 0 c5t2d0 ONLINE 0 0 0 c5t3d0 ONLINE 0 0 0 c5t4d0 ONLINE 0 0 0 c5t5d0 ONLINE 0 0 0 errors: No known data errors -- Éditions de l'Âge d'Or — Stanley G. Weinbaum http://www.lulu.com/robert_soubie http://www.smashwords.com/profile/view/StanleyGWeinbaum ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] COMSTAR iSCSI fail-over
I suspect you need to include the zfs properties with your zfs send, -p will provide them. Regards, Mike http://blog.laspina.ca -Original Message- From: Florian [mailto:flor...@acw.at] Sent: Sunday, September 02, 2012 6:40 AM To: openindiana-discuss@openindiana.org Subject: [OpenIndiana-discuss] COMSTAR iSCSI fail-over Hello, I have one another question. We use two equal OI Server with COMSTAR iSCSI devices and we want to backup them. I backup them with zfs send and receive to each other in a backup directory. Has anyone experience with such a setup and how could I get the best disaster recovery with this combination? My big problem is, that I can't import a received LU. I get the following error: /Error importing stmfadm: meta file error/ With /zfs get stmf_sbd_lu property tank/backup_raid/raid1-0 /I get the same data like on the sending side, only source is different. How can I send the meta file, too? Is there an other method to import the LU or do I need to create new LU with the received block devices? Best regards Florian ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ZFS remote receive
Hi Sebastian, Some examples using RBAC in my blog entry http://blog.laspina.ca/ubiquitous/provisioning_disaster_recovery_with_zf s could help. Regards, Mike -Original Message- From: Sebastian Gabler [mailto:sequoiamo...@gmx.net] Sent: Tuesday, October 23, 2012 6:53 AM To: openindiana-discuss@openindiana.org Subject: [OpenIndiana-discuss] ZFS remote receive Hi, I am facing a problem with zfs receive through ssh. As usually, root can't log on ssh; the log on users can't receive a zfs stream (rights problem), and pfexec is disabled on the target host (as I understand it is nowadays default for OI151_a...) What are the suggestions to solve this? I tried several approaches with sudo, and su to no avail. I had tried to enable pfexec on the target system, too and couldn't do it. Thanks for your help. BR Sebastian ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ZFS remote receive
Some additional example in this one http://blog.laspina.ca/ubiquitous/encapsulating-vt-d-accelerated-zfs-sto rage-within-esxi -Original Message- From: Sebastian Gabler [mailto:sequoiamo...@gmx.net] Sent: Tuesday, October 23, 2012 6:53 AM To: openindiana-discuss@openindiana.org Subject: [OpenIndiana-discuss] ZFS remote receive Hi, I am facing a problem with zfs receive through ssh. As usually, root can't log on ssh; the log on users can't receive a zfs stream (rights problem), and pfexec is disabled on the target host (as I understand it is nowadays default for OI151_a...) What are the suggestions to solve this? I tried several approaches with sudo, and su to no avail. I had tried to enable pfexec on the target system, too and couldn't do it. Thanks for your help. BR Sebastian ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Limit - 255 iSCSI targets
The maximum is actually 1024 on the iscsi port end: xref: /illumos-gate/usr/src/uts/common/io/comstar/port/iscsit/iscsit.h 55/* Max targets per system */ 56#define ISCSIT_MAX_TARGETS 1024 How have you determined it's 255? --Mike -Original Message- From: Richard Elling [mailto:richard.ell...@richardelling.com] Sent: Friday, March 29, 2013 11:51 AM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] Limit - 255 iSCSI targets On Mar 28, 2013, at 11:04 PM, "Shvayakov A." wrote: > I found this: https://www.illumos.org/issues/1437 > > But not sure that it will be without problem > > Anybody knows - what's the reason for this limitation? WAG. The old limit was 32 because nobody would ever need more than 32 targets, right? -- richard -- richard.ell...@richardelling.com +1-760-896-4422 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Limit - 255 iSCSI targets
Hi Geoff,
It looks like the itadm utility is limiting the number of targets. I have not
walked all the code but I do not see any reason this cannot be increased to
1024 in the itadm user utility.
http://src.illumos.org/source/xref/illumos-gate/usr/src/lib/libiscsit/common/libiscsit.h
43<http://src.illumos.org/source/xref/illumos-gate/usr/src/lib/libiscsit/common/libiscsit.h#43>#define
MAX_TARGETS<http://src.illumos.org/source/s?refs=MAX_TARGETS&project=illumos-gate>
255 /* maximum targets that may be created */
You could submit an RFE for this one, it does look like a simple change.
Normally I would say 255 is more that a server should have defined but if the
targets are largely idle then more than 255 would be a possible use case. Also
with the ever increasing hardware capability emerging 255 will soon become a
low limit.
Regards,
Mike
On 2013-04-01, at 7:59 AM, "Geoff Nordli"
mailto:geo...@gnaa.net>> wrote:
On 13-03-31 01:20 AM, Mike La Spina wrote:
The maximum is actually 1024 on the iscsi port end:
xref: /illumos-gate/usr/src/uts/common/io/comstar/port/iscsit/iscsit.h
55/* Max targets per system */
56#defineISCSIT_MAX_TARGETS1024
How have you determined it's 255?
Hi Mike.
I tested it using a for loop to create > 255
for i in {1..260}; do itadm create-target; done
then it will error out with the:
"Maximum of 255 iSCSI targets
itadm create-target failed with error 7
255 is a bit small, but 1024 would be enough for us; really it ought to be
enough for anyone :)
Geoff
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org<mailto:OpenIndiana-discuss@openindiana.org>
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
