search for: nthere

...0) else if(r >= n) v[1:n] else rbind(cbind(v[1], Recall(n-1, r-1, v[-1])),Recall(n-1, r, v[-1])) } # Main function find.amount = function(amount,products) { if(sum(products)<amount) { cat("There is no solution.\n") return() } l = length(products) cat("\nThere are",l,"product prices\n\n") names(products) = paste("Product",1:l,sep="") products = sort(products) for(i in 2:l) { # If the sum of the i smallest prices is greater than amount, then stop if(sum(products[1:i])>amount) break # Look for matc...

I put this to the smp list and to stable but have had no takers from wither. nThere are both smp and other system issues and I am just wondering if anyoe would be willing to take a look at this output from dmesg and let me have some advice Thanks david ----- Original Message ----- From: "vizion communication" <vizion@ixpres.com> To: <freebsd-smp@freebsd.org&gt...

Does anyone know what program can be used to query the RAID status from the OS for an on-board LSI SAS 2308-4i? On this page: http://docs.avagotech.com/docs/12351997 there is a curious note on the left that reads: "Integrated MegaRAID support available upon request" After one mostly fruitless round of chatting with LSI/Avago/Broadcom and one completely fruitless round of chatting

On 1/30/2015 1:53 AM, Gordon Messmer wrote: > On 01/29/2015 05:07 AM, Jatin Davey wrote: >> Yes , it is a SATA disk. I am not sure of the speed. Can you tell me >> how to find out this information ? Additionally we are using RAID 10 >> configuration with 4 disks. > > What RAID controller are you using? > > # lspci | grep RAID [Jatin] [root at localhost ~]# lspci |

...Output(cmd) arraydisk = returnDiskInfo(output,controllerid,arrayid) for array in arraydisk: print 'disk '+array[0]+' | '+array[1]+' | '+array[2]+' | '+array[3] arrayid += 1 controllerid += 1 if bad: print '\nThere is at least one disk/array in a NOT OPTIMAL state.' sys.exit(1) *****************end of the script************** -- john r pierce 37N 122W somewhere on the middle of the left coast

...Output(cmd) arraydisk = returnDiskInfo(output,controllerid,arrayid) for array in arraydisk: print 'disk '+array[0]+' | '+array[1]+' | '+array[2]+' | '+array[3] arrayid += 1 controllerid += 1 if bad: print '\nThere is at least one disk/array in a NOT OPTIMAL state.' sys.exit(1) -- john r pierce, recycling bits in santa cruz

...nDiskInfo(output,controllerid,arrayid) > > for array in arraydisk: > print 'disk '+array[0]+' | '+array[1]+' | '+array[2]+' | > '+array[3] > arrayid += 1 > controllerid += 1 > > if bad: > print '\nThere is at least one disk/array in a NOT OPTIMAL state.' > sys.exit(1) > *****************end of the script************** > > Thanks John, I ran your script and here is the output for it: Start of the Output*************************** [root at localhost bin]# lsi-raidinfo sh: /opt/...

On Thursday 02 November 2017 14:10:25 Bowie Bailey wrote: > If you want raid 5 or 6, then you should get a hardware controller. For > raid 1, mdadm should work just fine.? I would suggest trying it before > buying a raid controller.? If it works for you, you save a few hundred > dollars and you have one less piece of hardware to worry about. > > I haven't looked at them in

I just had an IBM in a remote location with a hardware raid1 have both drives go bad. With local machines I probably would have caught it from the drive light before the 2nd one died... What is the state of the art in linux software monitoring for this? Long ago when that box was set up I think the best I could have done was a Java GUI tool that IBM had for their servers - and that seemed like

...("MEDIUM ORCHID")) - - @panelA = Wx::Window.new(self, -1, Wx::DEFAULT_POSITION, Wx::DEFAULT_SIZE, Wx::SIMPLE_BORDER) - @panelA.set_background_colour(Wx::BLUE) - txt = Wx::StaticText.new(@panelA, -1, "Resize the window and see\nwhat happens... Notice that\nthere is no OnSize handler.", - Wx::Point.new(5,5), Wx::Size.new(-1,50)) - txt.set_background_colour(Wx::BLUE) - txt.set_foreground_colour(Wx::WHITE) - - lc = Wx::LayoutConstraints.new() - lc.top.same_as(self, Wx::LAYOUT_TOP, 10)...

It turns out that RHEL 5 Xen conversions don't work if the source disk is located on a block device. See patch 1/4 for the gory details. This patch series proposes a new tool called virt-v2v-copy-to-local which essentially is a way to make new virt-v2v work like the old virt-v2v, ie. copy first, convert after. Of course this is very slow and would only be used as a last resort, but I

This patch is incomplete, but early feedback would be welcome. Rich.

Previously posted: https://www.redhat.com/archives/libguestfs/2018-November/msg00000.html https://www.redhat.com/archives/libguestfs/2018-November/msg00001.html This completes the split and rewrite of the virt-v2v manual to make it much simpler to understand and digest. Rich.