search for: spectralogic

...drew.cooper3@citrix.com> Attilio Rao <attilio.rao@citrix.com> George Dunlap <george.dunlap@eu.citrix.com> Ian Campbell <Ian.Campbell@citrix.com> Ian Jackson <ian.jackson@eu.citrix.com> Jean Guyader <jean.guyader@eu.citrix.com> Justin T. Gibbs <justing@spectralogic.com> Keir Fraser <keir@xen.org> Olaf Hering <olaf@aepfle.de> Stefano Stabellini <stefano.stabellini@eu.citrix.com> Tim Deegan <tim@xen.org> ------------------------------------------------------------ jobs: build-amd64...

...This would let me lose up to two drives per shelf and still be operational. My only concern with this is if a shelf fails (SCSI card failure, etc) the whole system is down, however the MTBF for a SCSI card is WAAAAY higher than the MTBF of a hard drive... FWIW, we do have a backup strategy onto a SpectraLogic tape loader, so losing the whole array, while bad, won''t put us out of business, though I''d prefer it didn''t happen :) Obviously there are dozens of other ways to carve this storage up, and I''d like some recommendations on what others have done with this amount...

...nbits.xen.org/staging/xen-unstable.hg *** Found and reproduced problem changeset *** Bug is in tree: xen http://xenbits.xen.org/staging/xen-unstable.hg Bug introduced: a59c1dcfe968 Bug not present: f9789db96c39 changeset: 24875:a59c1dcfe968 user: Justin T. Gibbs <justing@spectralogic.com> date: Thu Feb 23 10:03:07 2012 +0000 blkif.h: Define and document the request number/size/segments extension Note: As of __XEN_INTERFACE_VERSION__ 0x00040201 the definition of BLKIF_MAX_SEGMENTS_PER_REQUEST has changed. Drivers must be...

...o <attilio.rao@citrix.com> George Dunlap <george.dunlap@eu.citrix.com> Ian Campbell <Ian.Campbell@citrix.com> Ian Jackson <ian.jackson@eu.citrix.com> Jan Beulich <jbeulich@suse.com> Jean Guyader <jean.guyader@eu.citrix.com> Justin T. Gibbs <justing@spectralogic.com> Keir Fraser <keir@xen.org> Olaf Hering <olaf@aepfle.de> Stefano Stabellini <stefano.stabellini@eu.citrix.com> Tim Deegan <tim@xen.org> ------------------------------------------------------------ jobs: build-amd64...

Almost everyone here has probably read this by now. If so, move along, nothing new here. But just in case you haven't, please take the time to read this. Here it is, in their own words: what Redhat thinks of Centos, and it's plans for the future of Centos. Can you read between the lines? In this case, it isn't very hard to do, IMHO. community.redhat.com/centos-faq

...queeze in 44kB per request. The ring can hold 32 (next power of two below 36) requests, meaning we can do 1.4M of outstanding requests. Nowadays that is not enough. The problem in the past was addressed in two ways - but neither one went upstream. The first solution to this proposed by Justin from Spectralogic was to negotiate the segment size. This means that the ‘struct blkif_sring_entry’ is now a variable size. It can expand from 112 bytes (cover 11 pages of data - 44kB) to 1580 bytes (256 pages of data - so 1MB). It is a simple extension by just making the array in the request expand from 11 to a va...

I've configured a domain member server using version 4.4.7 on FreeBSD. I'm able to manage groups and shares from the Computer Management tool on a Windows 2008 server, but when I connect to the samba member server the following error occurs: Event Viewer cannot connect to computer 'XXXXXX'. The error reported is : The RPC server is unavailable. Clicking OK allows me to proceed.

I'm using zfsacl on samba 4.6.6 on FreeBSD. File system ACLs work correctly, and Computer Management allows me to set share permissions (permissions are updated and displayed back correctly), but access doesn't appear to honor the configured share permissions. For example, users with file level ACLs that grant write permission are allowed to write even when share level permissions

> The workaround may be to have the client log out and log back in after > making the changes. :-)  I just tested on a FreeBSD system. The permissions > work as expected once the client establishes a fresh connection. It appears that when a user has SeDiskOperatorPrivilege​ they always have full access regardless of the share permissions. When I attempt access using credentials