search for: mits

On Fri, Jun 23, 2017 at 9:10 AM, Pranith Kumar Karampuri < pkarampu at redhat.com> wrote: > > > On Fri, Jun 23, 2017 at 2:23 AM, Pat Haley <phaley at mit.edu> wrote: > >> >> Hi, >> >> Today we experimented with some of the FUSE options that we found in the >> list. >> >> Changing these options had no effect: >> >>

On Fri, Jun 23, 2017 at 2:23 AM, Pat Haley <phaley at mit.edu> wrote: > > Hi, > > Today we experimented with some of the FUSE options that we found in the > list. > > Changing these options had no effect: > > gluster volume set test-volume performance.cache-max-file-size 2MB > gluster volume set test-volume performance.cache-refresh-timeout 4 > gluster

Hi All, Decided to try another tests of gluster mounted via FUSE vs gluster mounted via NFS, this time using the software we run in production (i.e. our ocean model writing a netCDF file). gluster mounted via NFS the run took 2.3 hr gluster mounted via FUSE: the run took 44.2 hr The only problem with using gluster mounted via NFS is that it does not respect the group write permissions which

Are you sure using conv=sync is what you want? I normally use conv=fdatasync, I'll look up the difference between the two and see if it affects your test. -b ----- Original Message ----- > From: "Pat Haley" <phaley at mit.edu> > To: "Pranith Kumar Karampuri" <pkarampu at redhat.com> > Cc: "Ravishankar N" <ravishankar at redhat.com>,

William Law <law@tc.cornell.edu> wrote: > resolve_hosts: Attempting host lookup for name ctcfsrv9.tc.cornell.edu\tc_q\users<0x20> > Connection to ctcfsrv9.tc.cornell.edu\tc_q\users failed > Unable to follow dfs referral [//ctcfsrv9.tc.cornell.edu\tc_q\users/law] > ... NT_STATUS_PATH_NOT_COVERED Hello, Early February mail from William Law and Jeremy Allison caught my eye,

On Mon, Jun 26, 2017 at 7:40 PM, Pat Haley <phaley at mit.edu> wrote: > > Hi All, > > Decided to try another tests of gluster mounted via FUSE vs gluster > mounted via NFS, this time using the software we run in production (i.e. > our ocean model writing a netCDF file). > > gluster mounted via NFS the run took 2.3 hr > > gluster mounted via FUSE: the run took

> -----Ursprüngliche Nachricht----- > Von: samba [mailto:samba-bounces at lists.samba.org] Im Auftrag von > Rowland penny > Gesendet: Sonntag, 5. Juni 2016 12:49 > An: samba at lists.samba.org > Betreff: Re: [Samba] inconsistent DNS information, windows domain > member issues.. > > On 05/06/16 10:05, Jo wrote: > > I joined a Windows 10 Pro system to my (still

Hi Guys, I was wondering what our next steps should be to solve the slow write times. Recently I was debugging a large code and writing a lot of output at every time step. When I tried writing to our gluster disks, it was taking over a day to do a single time step whereas if I had the same program (same hardware, network) write to our nfs disk the time per time-step was about 45 minutes.

Hi Ben, Sorry this took so long, but we had a real-time forecasting exercise last week and I could only get to this now. Backend Hardware/OS: * Much of the information on our back end system is included at the top of http://lists.gluster.org/pipermail/gluster-users/2017-April/030529.html * The specific model of the hard disks is SeaGate ENTERPRISE CAPACITY V.4 6TB

Hi, Today we experimented with some of the FUSE options that we found in the list. Changing these options had no effect: gluster volume set test-volume performance.cache-max-file-size 2MB gluster volume set test-volume performance.cache-refresh-timeout 4 gluster volume set test-volume performance.cache-size 256MB gluster volume set test-volume performance.write-behind-window-size 4MB gluster

Can you post the following files: /etc/resolv.conf /etc/hostname /etc/hosts /etc/krb5.conf pi at fs1:/var/log/apache2 $ cat /etc/resolv.conf # Generated by resolvconf search samdom.example.com nameserver 192.168.1.229 nameserver 192.168.1.228 nameserver X.X.X.X nameserver X.X.X.X nameserver 8.8.8.8 pi at fs1:/var/log/apache2 $ cat /etc/hostname fs1 pi at fs1:/var/log/apache2 $ cat /etc/hosts

Le 16/10/2019 ? 09:33, Rowland penny via samba a ?crit?: > On 16/10/2019 07:56, nathalie ramat via samba wrote: >> Hello, >> >> I need help you to understand my error. >> >> I have juste generate samba ad with the following command >> >> samba-tool domain provision --use-rfc2307 --interactive >> Realm:?? SAMBADOM.CALAIS.FR >> Domain

??Can you also post the output of bind from the point its starting up until samba has started?? I am not certain how to obtain this. -- Barry Collected config --- 2018-11-27-14:54 ----------- Hostname: Sambadc1 DNS Domain: Mydomain.com FQDN: Sambadc1.Mydomain.com ipaddress: ##.##.##.## ----------- Samba is not being run as a DC or a Unix domain member. Checking file: /etc/os-release

Hi Rowland, I made the change you suggested to auto refresh kerberos. It didn't seem to fix the issue unfortunately, even after a machine restart. Following your line of reasoning that it is a Kerberos issue, I then tried to grab a new kerberos ticket on the server in question which appears to fail though. Perhaps this gives some further insight? pi at fs1:~ $ kinit administrator at

On 05/06/16 13:43, Jo wrote: >> Your DCs really need to be running at all times, so that replication >> can work properly, also each DC should use the other for their DNS >> server, anything unknown to the DNS servers on the DCs should be >> forwarded to an external DNS that does know or can find out. > I understand that they need to be up simultaneously for

I joined a Windows 10 Pro system to my (still experimental) domain. The windows system actually hosts DC2 as a VM, and another Windows (Server 2008 R2) at another location hosts DC1 also as a VM. The two locations are connected via a VPN, both systems run only when needed. The windows system does not directly use DC2 for DNS but instead talks to a DNS resolver that delegates the samba Domain to

Samba 4.7.6 Ubuntu /etc/hosts: 127.0.0.1 localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts /etc/resolv.conf: # This file is managed by man:systemd-resolved(8). Do

See reply below. (Sent from home location.) Bob Wooden On 6/11/20 7:29 AM, Rowland penny via samba wrote: > If you had a previous AD domain, you must have had a FQDN, but having > said that, it does look like In my previous AD domain, my FQDN was a non-registered (fake) domain that has worked for years. For example "fakedomainname.intials", like "domain.dt". This

Hi Rowland, On Wed, Nov 08, 2017 at 09:45:48AM +0000, Rowland Penny wrote: > On Wed, 8 Nov 2017 09:24:30 +0100 > Ervin Hegedüs via samba <samba at lists.samba.org> wrote: > > > Hi folks, > > > > there are two Samba4 DC server. The first one is the "PDC", and > > after I finished to set up that, I've joined the second one. > > I am a

On 10/5/2020 2:52 PM, Rowland penny via samba wrote: > On 05/10/2020 19:29, Jason Keltz via samba wrote: >> >> On 10/5/2020 12:44 PM, Rowland penny via samba wrote: >>> On 05/10/2020 17:27, Jason Keltz via samba wrote: >>>> >>>> Hi Roland, >>>> >>>> I'm glad you brought that up.? This is a piece of the puzzle I have