April 10, 2009 
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | >
April 10, 2009 NOTICE: This channel is no longer actively logged.
[00:00:10] *** teknoprep has joined ##nexenta[00:01:10] *** teknoprep has quit IRC[00:08:07] *** teknoprep has joined ##nexenta[00:08:16] <teknoprep> hey is anyone else using Nexenta 2.0 rc1 ?[00:08:22] <teknoprep> and comstar[00:08:39] <teknoprep> i am getting a ton of event id 20 error on windows machines connected to the iscsi targets[00:08:48] <teknoprep> they keep disconected and reconected right away[00:11:29] *** taltamir has quit IRC[00:11:36] <teknoprep> hmm[00:12:59] *** teknoprep has quit IRC[00:43:00] *** baitisj1 has joined ##nexenta[02:29:56] *** tsukasa` has joined ##nexenta[02:39:27] *** erast has joined ##nexenta[02:41:04] *** rich_____ has joined ##nexenta[02:44:17] *** taltamir has joined ##nexenta[02:46:12] *** tsukasa has quit IRC[03:06:56] *** RoyK has joined ##nexenta[03:10:07] *** RoyK has left ##nexenta[03:27:32] *** cto_nz has joined ##nexenta[03:28:22] *** alfism has quit IRC[03:39:08] *** rich_____ has quit IRC[03:59:46] <cto_nz> Hi everyone. While I have watched Nexenta from afar for a couple of years, I am now taking the plunge due to the solaris kernel goodness :) Have downloaded and installed ncp 2.0 rc1 into a VM and have now tried to create a devzone as I want to have a crack at packaging ZimbraCS and Openbravo for ncp. I have created devzone.conf and init'd the devzone system....as a normal user though when I devzone _create I get this "could not verify zf[04:00:05] <cto_nz> any ideas???[04:11:52] *** tsukasa__ has joined ##nexenta[04:24:56] *** tsukasa` has quit IRC[04:57:16] <rootard> cto_nz: your error message got cut off[04:57:26] <rootard> "could not verify zf ... ?[04:58:01] <cto_nz> could not verify zfs dataset syspool/users/joelm: dataset does not exist"[04:58:08] <cto_nz> sorry[04:58:52] <rootard> zfs create syspool/users;zfs create -o mountpoint=none syspool/users/joelm[05:00:04] <cto_nz> ahh... mountpoint=none.... I hadn't tried that.....excellent. Thanks for your help[05:10:55] <rootard> Does it work now?[05:14:27] *** alfism has joined ##nexenta[05:36:23] <cto_nz> rootard: worked a treat. thanks[05:58:13] *** rmod_ has joined ##nexenta[06:14:02] *** cto_nz has left ##nexenta[06:21:16] *** rmod has quit IRC[06:23:01] *** nprice has quit IRC[06:32:54] *** nprice has joined ##nexenta[06:46:52] *** anilg has joined ##nexenta[06:47:03] <anilg> lo all[07:29:34] *** fserve has joined ##nexenta[07:37:19] *** erast has quit IRC[07:49:15] *** SockPants has joined ##nexenta[07:49:17] <SockPants> hello[07:55:16] *** baitisj has quit IRC[08:02:21] <SockPants> hi[08:02:32] <SockPants> allow me to ask a newbie question[08:03:05] *** yuang has quit IRC[08:03:27] <SockPants> i've just installed nexenta 1.01 on my machine and it's booted to the terminal[08:03:55] <SockPants> when i type something like 'zfs' and hit enter the text spills over the screen and i can't read what's at the top[08:04:11] <SockPants> is there any way i can scroll up or get it to not scroll down?[08:08:10] <anilg> hi Sockpants.. screen should help you here..[08:08:28] <anilg> google and read up on screen.. or better yet look up hte zfs man pages online[08:08:35] <dtbartle> or 'zfs foo | less'[08:08:58] <anilg> Another option is sshing into the machine from a terminal with scrolling, like gnome-terminal or putty[08:09:22] <SockPants> ok[08:09:35] <SockPants> i know about screen, i can try that[08:09:50] <SockPants> | less and more dont seem to work here though[08:10:04] <SockPants> using ssh would be even easier, i guess i'll set that up first[08:10:24] <SockPants> PING 1239343949 292609[08:10:31] <SockPants> PING 1239343955 572446[08:11:28] <SockPants> thanks, is ssh set up by default or how do i set it up?[08:12:01] <anilg> it should be.. run svcs ssh to find out[08:12:05] <anilg> it should be online by default[08:12:14] <anilg> if not, run svcadm enable ssh[08:12:21] <SockPants> yep it seems to be working[08:12:34] <anilg> root logins are disabled by default.. but you can login as the account you created and then sudo[08:12:58] <SockPants> hmm[08:13:52] <SockPants> i don't think it's getting an ip address[08:14:47] <SockPants> ah there we go, cable is bad -_-[08:16:29] *** JetForMe has quit IRC[08:31:38] *** databeestje__ has joined ##nexenta[08:31:42] <databeestje__> Morning[08:31:55] <databeestje__> Anybody here that can help iperf testing?[08:33:58] <dtbartle> SockPants: if it outputs to stderr you can do something like 'zfs foo 2> /dev/stdout | less'[08:36:41] *** JetForMe has joined ##nexenta[08:38:21] <SockPants> ok[08:38:29] <SockPants> i've got a new problem now[08:38:45] <databeestje__> How does one open up a WD MyBook disk[08:39:27] <SockPants> i've connected 5 harddisks, 4 on sata and 1 on IDE. i boot from a 6th IDE harddisk. i want to create a zpool out of the 5, but how do i find the identifiers for the disks (like c1t1d1 ...)[08:40:45] *** JetForMe has quit IRC[08:40:57] *** JetForMe has joined ##nexenta[08:45:36] <databeestje__> Remove the rubber surrounding, then press 2 retention clips, one the bottom and one the top[08:45:49] <databeestje__> Then you can jiggle the 2 parts loose[08:51:39] <databeestje__> This WD drive doesn't appear to be very happy[08:53:23] <SockPants> what's the opposite of su[08:53:32] <databeestje__> ? The opposite?[08:53:39] <databeestje__> su - <user>[08:54:11] <SockPants> ok :P thanks[08:54:30] <databeestje__> This WD drive is burning up.[08:54:39] <databeestje__> I hope I can still get some data off.[08:55:34] <SockPants> :S[08:55:42] <SockPants> good luck[08:55:53] <databeestje__> This is/was a external disk from our Graphics Department[08:56:03] <databeestje__> And the fat32 fs got corrupted[08:56:17] <databeestje__> chkdsk hung forever at 0% percent as well.[08:56:37] <SockPants> how can I see the devices that are in a zpool?[08:56:58] *** rich____ has joined ##nexenta[09:01:06] <databeestje__> I have no idea[09:01:13] <databeestje__> I just use NexentaStor[09:02:22] <SockPants> hmm[09:02:33] <SockPants> i've got this[09:02:36] <SockPants> 0. c0d0 <drive type unknown>[09:02:37] <SockPants> /pci@0,0/pci-ide@6/ide@0/cmdk@0,0[09:02:37] <SockPants> 1. c0d1 <DEFAULT cyl 4995 alt 2 hd 255 sec 63>[09:02:37] <SockPants> /pci@0,0/pci-ide@6/ide@0/cmdk@1,0[09:03:02] <SockPants> one of those is a 40gb drive, which is in use as the boot disk. the other one isn't used atm[09:03:13] <SockPants> how can i tell them apart[09:05:13] <SockPants> ah found it nevermind :) zpool status[09:07:20] <SockPants> i tried to create the pool and got this:[09:07:22] <SockPants> cannot open 'c0d0': no such device in /dev/dsk[09:07:23] <SockPants> must be a full path or shorthand device name[09:08:03] <SockPants> in /dev/dsk everything ends in s0 or p0 or some other number, do i just add s0 onto everything or..?[09:09:11] <dtbartle> the s* are slices[09:09:19] <dtbartle> p* are partitions[09:09:22] <dtbartle> i think[09:09:46] <codestr0m> morning![09:09:49] <codestr0m> dtbartle: that's correct[09:10:18] <SockPants> so to make a vdev out of the entire physical drives what do I put?[09:10:46] <SockPants> i tried adding s0 to the end but it failed, saything there is no such device, even though it is listed in /dev/dsk[09:12:44] <dtbartle> /dev/dsk/c5d0 and /dev/dsk/c6d0 is what i have[09:13:42] <SockPants> hm, those arent even listed in /dev/dsk here. everything ends in s-something or p-somethinhg[09:14:47] <SockPants> hmm, nevermind :) it didn't work because i wasnt root, but that's not what it said[09:14:50] <SockPants> hehe[09:14:53] <SockPants> thansk[09:15:53] <dtbartle> np[09:22:33] <SockPants> hmm, the capacity of a raidz is determined by the smallest drive isnt it?[09:22:49] <SockPants> it doesn't just use all the space on all the drives does it?[09:23:02] <dtbartle> probably not[09:23:21] <dtbartle> it can't for raid{0,1,5,6}[09:23:53] <dtbartle> you can partition the drives though[09:24:03] <SockPants> yeah, though i thought there were some software raid solutions that could make more effective use of space and assumed raidz was one of them :P[09:24:06] <SockPants> oh, that might work[09:24:07] <dtbartle> so you don't actually waste any space[09:24:08] *** Fosforo has quit IRC[09:24:40] <SockPants> so if the smallest one is 120gb i could make 120 gb partitions across all the drives, raidz those, then use the rest of the space for something else[09:29:07] <SockPants> what's the best way to go about formatting and managing drives in nexenta[09:29:08] <SockPants> ?[09:29:27] *** lesterc has quit IRC[09:31:00] <anilg> SockPants: read up on partitions and slices[09:31:22] <anilg> fdisk and format are the commands you'll be using[09:31:32] <anilg> slices are kinda like partitions inside partitions[09:32:08] <SockPants> ok[09:33:40] <SockPants> what is the best thing to do? make as many 120 GB slices/partitions as I can and then add them all to one vdev, or making one partition/slice on each physical drive and making a vdev out of those and making another vdev out of the remainder, and adding both vdevs to the same zpool?[09:37:35] <dtbartle> you want to distribute the load oon the disks evently[09:37:37] <dtbartle> *evenly[09:38:06] *** alfism has quit IRC[09:40:17] <SockPants> i'm not too worried about the load distribution as long as the performance isn't dramatically affected, i do want to get the maximum capacity though.[09:40:36] <SockPants> also, if i do this, would it still be possible to replace the disks with bigger ones?[09:41:37] <SockPants> i assume i'd have to jsut repartition them with bigger partitions (ie 240 instead of 120 gb) and that would work in the same way as upgrading the entire drives if actual drives are used... right?[09:43:24] <dtbartle> you generally can't resize the raid array after the fact[09:44:46] <SockPants> if i had 3 250 GB drives in a raidz and i replaced each one with a 500GB drive one by one wouldnt that double the capacity of the array?[09:45:03] <dtbartle> no[09:45:15] <dtbartle> i don't think you can resize the array like this[09:45:22] <dtbartle> you would need to create a new array across the new dsks[09:45:27] <SockPants> hmm, i think i jsut read something like that somewhere[09:45:28] <dtbartle> then rsync the old data from the old to new array[09:45:50] <dtbartle> i could be wrong though[09:46:29] <SockPants> hm it might be possible according to this: Capacity expansion is normally achieved by adding groups of disks as a vdev (stripe, RAID-Z, RAID-Z2, or mirrored). Newly written data will dynamically start to use all available vdevs. It is also possible to expand the array by iteratively swapping each drive in the array with a bigger drive and waiting for ZFS to heal itself — the heal time will depend on amount of stored information, not the d[09:47:04] <dtbartle> interesting[09:47:35] <SockPants> but I don't see that working if I use partitions, because if I take out one drive that happens to store 2 partitions then i would need at least a raidz2 in order for it to work at all, and in case it stores 3 of the partitions it would never work[09:48:14] <SockPants> and if I then put a new drive in, i doubt it would make the partitions itself. I'd probably have to partition the new drive, and hope ZFS sees the 2 new partitions and heals itself. if not, it might not work at all[09:48:15] <dtbartle> is this goiong to be raid1,2, or 5?[09:48:17] <dtbartle> er[09:48:19] <dtbartle> 0, 1, or 5[09:48:21] <SockPants> raidz2[09:48:23] <SockPants> 6[09:48:42] <dtbartle> you probably just take a disk or partition offline[09:48:46] <dtbartle> and add the new disk to the pool[09:49:05] *** twifkak has joined ##nexenta[09:49:06] <SockPants> but you can't alter the actual disks in a raid, only in the pool itself afaik[09:49:18] <dtbartle> right[09:49:22] <dtbartle> so you take the disk offline[09:49:25] <dtbartle> insert the new one[09:49:28] <dtbartle> and add the full disk[09:49:47] <dtbartle> you can take disks offline in a pool afaik[09:50:04] <dtbartle> the raid araray goes into a degraded state[09:50:07] <dtbartle> or whatever[09:50:10] <SockPants> that would work with disks, but if the array is composed of partitions and not disks, would it still work?[09:50:26] <dtbartle> shouldn't matter[09:50:33] <dtbartle> it will mmaybe be trickier[09:50:57] <dtbartle> you can't remove more than 2 members of a raid6 array[09:51:01] <SockPants> yaeh[09:51:08] <dtbartle> so you could remove one partition[09:51:10] <dtbartle> add new disk[09:51:14] <dtbartle> remove the other partition[09:51:14] <SockPants> so i'd have to make sure no physical disk carries more than 2 of the partitions in one array[09:51:16] <dtbartle> remove disk[09:52:07] <dtbartle> tbh, adding multiple partitions to a pool seems really strange[09:53:39] <databeestje__> rsyncing 400 Gigs of data is a pain[09:54:32] <dtbartle> anyway, that info is interesting[09:54:37] <SockPants> hm, i think i'll play around with it after i finish reading this[09:54:42] <dtbartle> i wanted to expand a raid0 array[09:54:50] <dtbartle> and assumed i would need to rsync the files[09:54:50] <SockPants> thanks for the help[09:55:16] <SockPants> raid0 is striping though right?[09:55:28] <dtbartle> yes[09:55:32] <dtbartle> er[09:55:34] <dtbartle> raid1[09:55:54] <dtbartle> (i'm a bit tired)[09:55:54] <SockPants> yeah, should work then...[09:55:58] <SockPants> :P[09:56:17] *** __ms_ is now known as __ms[10:06:25] <SockPants> hmm, should I use solaris2 partitions then?[10:09:23] <SockPants> urrr[10:09:26] <SockPants> fdisk: Error writing master boot record to /dev/rdsk/c2t0d0.[10:09:27] <SockPants> root@Jnas:/dev/dsk# fdisk /dev/rdsk/c2t0d0[10:09:27] <SockPants> fdisk: Cannot stat device /dev/rdsk/c2t0d0.[10:09:33] *** andy_js has joined ##nexenta[10:12:30] <anilg> SockPants: perhaps oyu need to add a p0 to the end[10:14:02] *** lesterc has joined ##nexenta[10:17:27] <SockPants> format doesnt work either[10:18:41] *** rich____ has quit IRC[10:20:20] *** tsukasa__ is now known as tsukasa[10:23:11] <SockPants> hmm something went pretty wrong on that drive[10:26:13] <databeestje__> Indeed, it's practically unreadable. And WD have sabotaged the drive for use with a normal usb to sata cradle.[10:29:24] *** [JT] has quit IRC[10:30:58] <SockPants> hmm wow i was referring to my own drive though :P it said there was no more defect list on it, so i have to go make one which takes ages[10:31:46] *** Laevar has joined ##nexenta[10:31:52] <Laevar> hi[10:32:13] <Laevar> how can i configure the solaris-samba to use an ldap-backend ?[10:33:50] <Laevar> and it seems it doesn't have any config-file..[10:34:11] <Laevar> can i install the "gnu" samba packages ? at least they exist on nexenta 2[10:38:54] *** lesterc has quit IRC[10:44:14] <databeestje__> Seems like the disk is a total loss[10:49:19] *** anilg has quit IRC[10:53:14] *** taltamir has quit IRC[10:57:30] <SockPants> how do i make it go graphical?[11:01:45] *** andy_js has quit IRC[11:04:49] *** andy_js has joined ##nexenta[11:12:58] <SockPants> urr...[11:12:59] <SockPants> root@Jnas:/dev/dsk# apt-get install xorg[11:12:59] <SockPants> Reading package lists... Done[11:12:59] <SockPants> Building dependency tree... Done[11:12:59] <SockPants> E: Couldn't find package xorg[11:22:16] <SockPants> nvm[11:22:27] <SockPants> can i get gnome on nexenta 1.01[11:27:55] *** JT_ has joined ##nexenta[11:34:59] *** JetForMe has quit IRC[11:41:00] *** JetForMe has joined ##nexenta[12:11:51] *** baitisj1 has quit IRC[12:19:50] <codestr0m> rootard: ping[12:20:14] <codestr0m> I need a sanity check on this repo http://pkg.osunix.org/osunix/dists/dancing-chicken-unstable/[12:30:34] *** tsukasa has quit IRC[12:36:27] *** andy_js has quit IRC[12:37:04] *** andy_js has joined ##nexenta[12:38:14] <Laevar> ok, i got "gnu" samba working so far that it doesn't match passwords via pam. This is related to the problem that i have all users visible via ldapclient (getent passwd works) but i can't login[12:38:23] <rootard> codestr0m: pong[12:38:40] <Laevar> is there something i am missing for correct ldap-user login ? (pam.conf is adapted..)[12:39:15] <codestr0m> rootard: what debian tool adds a new repo? how can I sanity check my repo from above?[12:42:17] <rootard> codestr0m: echo[12:42:28] <rootard> echo "deb http://pkg.osunix.org/osunix dancing-chicken-unstable main" >> /etc/apt/sources.list[12:42:35] <rootard> aptitude update[12:42:51] <rootard> :)[12:43:02] <codestr0m> rootard: did it work for you? I don't have an aptitude[12:43:14] <rootard> apt-get update[12:43:32] <rootard> What packages should I be able to see in the repo?[12:44:00] <codestr0m> printf-1.deb ps-107.deb sed-4.1.5.deb[12:44:13] <codestr0m> those are in osunix/dists/dancing-chicken-unstable/main/binary-solaris-i386[12:46:06] <rootard> nope, doesn't work properly[12:46:16] <codestr0m> rootard: can you tell me what's wrong with it?[12:46:20] <rootard> what are you using to generate the Packages file?[12:46:54] <codestr0m> rootard: dpkg-scanpackages ./dancing-chicken/ /dev/null | gzip -c -9 > Packages.gz and then hand edit because the paths are wrong[12:47:12] <codestr0m> and the md5sums are generated by hand as well[12:47:24] <codestr0m> in re to the Release file[12:48:51] <databeestje__> Gotta move these gigabytes[12:49:17] <rootard> run it like this: dpkg-scanpackages dists/dancing-chicken /dev/null > dists/dancing-chicken/binary-solaris-i386/Packages[12:49:27] <rootard> and then create a .gz and a .bz2 version[12:51:50] <codestr0m> rootard: was that a typo? or should I change the paths? dpkg-scanpackages dists/dancing-chicken-unstable/ /dev/null > dists/dancing-chicken-unstable/main/binary-solaris-i386/Package[12:52:15] <rootard> you should change the cwd and use my example[12:52:16] <codestr0m> try again[12:52:40] <codestr0m> ok. I changed, but dancing-chicken != dancing-chicken-unstable[12:53:14] <codestr0m> I updated if you want to try again.. if that fails I'll mv -f the directories to exactly match your example[12:53:52] <rootard> well, its a question of how you want to call the repository...[12:54:23] <codestr0m> dancing-chicken-unstable is fine[12:54:31] <codestr0m> lets people know what to expect[12:54:57] <rootard> ok, so cd into the directory that contains dists[12:55:15] <rootard> dpkg-scanpackages dists /dev/null > dists/dancing-chicken-unstable/binary-solaris-i386/Packages[12:55:29] <rootard> then your paths should be right the first time[12:55:41] <rootard> don't put an extra / on the end of dists[12:56:37] <codestr0m> rootard: ok. dists/dancing-chicken-unstable/main/binary-solaris-i386 != dists/dancing-chicken-unstable/binary-solaris-i386[12:56:41] <codestr0m> should I drop the main?[12:56:45] <codestr0m> (sorry for all these questions)[12:57:08] <rootard> no, you are right, keep the main[12:57:26] <rootard> I copied/pasted too quickly last time[12:57:39] <codestr0m> rootard: ok. try now sir[12:58:36] <rootard> alright, still not working and the problem is that the arch is set to solaris[12:58:53] <rootard> the deb packages themselves need to be solaris-i386[13:00:11] <rootard> Here is a good sources.list to look at: http://apt.nexenta.org/dists/hardy-unstable/main/binary-solaris-i386/Packages[13:00:25] <rootard> er, not sources.list... you know what I meant[13:00:32] * rootard slaps brain[13:01:41] <codestr0m> rootard: ok. I'll update[13:03:29] <rootard> The deb packages themselves are not named correctly either[13:03:51] <rootard> they should be in the form of name_version_arch.deb[13:03:58] <rootard> not name-version.deb[13:05:09] <codestr0m> ok. I'll adjust and generate[13:05:11] <codestr0m> thanks[13:06:59] <rootard> no prob :)[14:07:10] *** hocke has quit IRC[14:07:10] *** mxpx- has quit IRC[14:07:55] *** twifkak has quit IRC[14:07:55] *** ChanServ has quit IRC[14:07:57] *** hocke has joined ##nexenta[14:07:57] *** mxpx- has joined ##nexenta[14:08:26] *** ChanServ has joined ##nexenta[14:08:26] *** twifkak has joined ##nexenta[14:08:26] *** irc.freenode.net sets mode: +o ChanServ[14:16:57] *** geek65535 has joined ##nexenta[14:21:06] <geek65535> has anyone seen a problem with aptitude where STDIN doesn't get connected? I've got a fresh install of the OS, and when I fire up aptitude in interactive mode, anything I type falls through to the shell.[14:21:31] *** geek65535 has left ##nexenta[14:22:08] *** geek65535 has joined ##nexenta[14:22:48] <geek65535> (sorry if I missed a reply...my client crashed.)[14:37:55] *** tsukasa has joined ##nexenta[14:40:33] <rootard> geek65535: I've heard of that but its working for me.[14:40:43] <rootard> To work-around you might try apt-get[14:50:41] *** rootard is now known as rootard_away[14:53:38] *** anilg has joined ##nexenta[15:02:12] *** Fosforo has joined ##nexenta[15:07:37] *** wurlitzer has joined ##nexenta[15:14:01] *** nixphreak has joined ##nexenta[15:14:45] <nixphreak> looking for more information on solaris zone contaniers and what you can and can't do with them[15:21:55] *** geek65535 has left ##nexenta[15:48:56] <SockPants> helloo again[15:49:20] <SockPants> ive run into this[15:49:21] <SockPants> zpool create -n tank raidz c2t0d0p1 c2t1d0p1 c3t0d0p1 c3t1d0p1 raidz c2t1d0p2 c3t0d0p2 c3t1d0p2[15:49:25] <SockPants> invalid vdev specification[15:49:27] <SockPants> use '-f' to override the following errors:[15:49:30] <SockPants> mismatched replication level: both 4-way and 3-way raidz vdevs are present[15:49:57] <SockPants> does that mean i actually can't make a pool using both 3- and 4-way raidz vdevs, or is it just whining?[15:52:05] <SockPants> ok ive found that it's just whining but that its 'not recommended' to do this... why?[15:53:23] *** databeestje__ has quit IRC[16:01:53] *** codestr0m is now known as codestr0m|afk[16:37:27] <SockPants> hmm, i can't seem to get to the zfs volumes i just made using nfs[16:37:35] <SockPants> i put sharenfs=on[16:37:51] <SockPants> but it won't let me connect to the server at all[16:48:00] *** lesterc has joined ##nexenta[16:51:16] <koan> SockPants: try showmount -e server on the client to look if it finds the share[16:52:20] <SockPants> yeah that seems to work now[16:53:13] <SockPants> i've connected now[16:53:20] <SockPants> but I don't have write priveleges[16:54:38] *** martinkl has joined ##nexenta[17:07:31] <martinkl> Hi all, I'm trying to install an OpenSolaris package (VirtualBox) on Nexenta 2.0 RC1, but troubled by this bug: https://bugs.launchpad.net/nexenta/+bug/350935[17:07:48] <martinkl> looks like the sun pkg tools are linked against the wrong version of libssl[17:08:12] <martinkl> Does anybody have an idea for a work-around? e.g. rebuilding from source?[17:16:01] *** SockPants has quit IRC[17:22:09] *** koan has quit IRC[17:22:13] *** koan has joined ##nexenta[17:27:02] *** fserve has quit IRC[17:50:51] *** twifkak has quit IRC[17:51:48] *** twifkak has joined ##nexenta[18:04:10] *** viridari has joined ##nexenta[18:06:53] *** rmod_ has quit IRC[18:07:12] *** martinkl has quit IRC[18:08:41] *** andy_js has quit IRC[18:10:13] *** viridari_ has joined ##nexenta[18:13:03] *** andy_js has joined ##nexenta[18:19:38] *** rmod has joined ##nexenta[18:23:14] *** viridari has quit IRC[18:28:54] *** anilg1 has joined ##nexenta[18:29:13] *** rmod has quit IRC[18:30:57] *** RoyK has joined ##nexenta[18:39:23] *** Laevar has quit IRC[18:43:32] *** alfism has joined ##nexenta[18:52:28] *** alfism has quit IRC[18:53:48] *** anilg has quit IRC[18:57:27] *** rmod has joined ##nexenta[18:57:43] *** andy_js has quit IRC[18:58:30] *** andy_js has joined ##nexenta[19:04:36] *** nixphreak has left ##nexenta[19:14:48] *** codestr0m|afk is now known as codestr0m[19:31:15] *** RoyK has quit IRC[19:36:58] *** anilg1 has quit IRC[19:40:51] *** fredantrobus has joined ##nexenta[19:44:43] *** fredantrobus has left ##nexenta[19:46:45] *** fredantrobus has joined ##nexenta[19:47:05] *** fredantrobus has left ##nexenta[19:50:48] *** JetForMe has quit IRC[19:52:42] *** rootard_away is now known as rootard[20:08:11] *** rmod has quit IRC[20:09:34] *** rmod has joined ##nexenta[20:11:52] *** JetForMe has joined ##nexenta[20:14:48] *** rmod has quit IRC[20:15:38] *** rmod has joined ##nexenta[20:18:07] *** RoyK has joined ##nexenta[20:19:06] *** rmod has quit IRC[20:20:10] *** rmod has joined ##nexenta[20:20:16] *** rmod has quit IRC[20:22:40] *** rmod has joined ##nexenta[20:24:51] *** codestr0m is now known as codestr0m|afk[20:27:04] *** alfism has joined ##nexenta[21:05:50] *** rootard is now known as rootard_away[21:15:18] *** andy_js has quit IRC[21:16:15] *** andy_js has joined ##nexenta[21:40:18] *** rmod has quit IRC[21:40:46] *** rmod has joined ##nexenta[21:47:22] *** Dagger` has quit IRC[21:47:50] *** Dagger` has joined ##nexenta[22:15:42] *** NCommander has quit IRC[22:42:19] *** RoyK has left ##nexenta[22:43:37] *** __ms_ has joined ##nexenta[22:43:45] *** __ms has quit IRC[22:46:04] *** andy_js has quit IRC[23:34:35] *** teknoprep has joined ##nexenta[23:34:37] <teknoprep> hi all[23:35:10] <teknoprep> anyone else have any issues with Comstar iSCSI with windows attached to it.. i keep getting event errors that say's it keeps disconnecting and then reconnecting[23:37:03] *** teknoprep has quit IRC