similar to: Isilon OneFS storage

Hi, We are in the process of testing a migration of our current setup which contains Samba 4 as Classic DC with LDAP backend, Isilon OneFS bulk storage serving NFS/SMB shares and Windows/Mac/Linux clients to a more modern Samba 4 AD. We need to migrate to Samba AD because of Windows 10 and macos 10.13.x (and for several other reasons). But we run into an issue with authenticating the clients

Hi everyone. Since yesterday we started experiencing very weird problem with our samba AD server and our Isilon storage. This seems to affect only the storage, as our Windows workstations are fine. Suddenly the storage lost connectivity to the AD and so it's unable to provide access to the SMB shares. I've tried rejoining without success and whatnot. Today I even created second AD dc for

.. it would be great if btrfs could be expended about abilities that OneFS file system has (FS by Isilon) .. there is ceph open source clustered/distributed storage system that is using btrfs, maybe work with those people would be a good start http://ceph.newdream.net/about/ http://ceph.newdream.net/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body

Hello Timo, I'm running a single instance of dovecot-2.1.15 on a single host running 8.3-RELEASE-p3 FreeBSD amd64 mailboxes (Maildir), control files and indexes are on NFS (v3,tcp) mail_nfs_storage = yes lock_method = fcntl [didn't touch the following] # Mail index files also exist in NFS. Setting this to yes requires # mmap_disable=yes and

Hi, On Mon, 2019-03-25 at 12:28 +0000, Rowland Penny via samba wrote: > On Mon, 25 Mar 2019 11:24:03 +0000 > "Deventer-2, M.S.J. van via samba" <samba at lists.samba.org> wrote: > > > Hi, > > > > we now have an old Windows NT4.0 domain served by Samba 4.2.x > > (using > > Samba and LDAP) and want to move to Windows AD. > > The reason

We're running dovecot 2.3.10 on two different servers (two different environments). Both very similarly configured (sendmail and procmail for mail delivery); same OS and patch levels. One environment has nearly 10,000 users and hasn't seen problems. The other environment has just a handful of users, but one user is very active with email and has a fairly complicated procmail

On Mon, 25 Mar 2019 11:24:03 +0000 "Deventer-2, M.S.J. van via samba" <samba at lists.samba.org> wrote: > Hi, > > we now have an old Windows NT4.0 domain served by Samba 4.2.x (using > Samba and LDAP) and want to move to Windows AD. > The reason we need to do that is because of the clients (Windows 10 > and MacOS) and because of a third party device which does

Great information, thank you. Could you remark on GPFS services hosting mail storage over a WAN between two geographically separated data centers? ----- Reply message ----- From: "Jan-Frode Myklebust" <janfrode at tanso.net> To: "Stan Hoeppner" <stan at hardwarefreak.com> Cc: "Timo Sirainen" <tss at iki.fi>, <dovecot at dovecot.org> Subject:

Hi, we now have an old Windows NT4.0 domain served by Samba 4.2.x (using Samba and LDAP) and want to move to Windows AD. The reason we need to do that is because of the clients (Windows 10 and MacOS) and because of a third party device which does not want to talk to Samba AD (Isilon OneFS). I did a 'classicupgrade' to Samba AD from our Samba/LDAP config and then I use this guide :

We've been running dovecot director setup using MAILDIR++ spools on NFS served by 4 (aging) Netapp clustered filers and are considering modernizing our storage. There's nothing particularly wrong with the existing storage except the age, density and power consumption don't compare well when against new systems. Refreshing the Netapps is an option but they come at a substantial cost.

Hi, I have question about username map and ACL. I'm using samba 3.0.11( with winbind) on FreeBSD 5.3. samba is AD member and that server provide NFS service. NFS user uses NIS. Because each user's windows's username and NIS username is different, we use username map like following. unix0001 = win0001 unix0002 = win0002 When win0001 makes file, that file is created as

I saw some interesting mails from TImo back in 2009 talking about the idea of using something like Cassandra db or similar as a storage platform for both email and index/logs. I was wondering if this has been discussed since then, and if there are any plans to support something like this in the future? I have been playing with Cassandra and found that their RackAwareStrategy gives you the

As of late our four node dovecot 1.2.13 cluster has been experiencing a massive number of these dotlock errors: Created dotlock file's timestamp is different than current time (1295480202 vs 1295479784): /mail/user/Maildir/dovecot-uidlist These dotlock errors correspond with very high load averages, and eventually we have to turn off all but one server to stop them from occurring. We first

We have been communicating with the mailling list on another thread regarding dotlocking on the dovcot-uidlist over an NFS share, and I was hoping to get some ideas on whether or not a sql database would be a suitable location for storing the dovecot index files. Our though process so far has been that storing the index files on NFS with the maildir has not worked very effectively when we are

On 2018-11-16 07:24, Adrian Minta wrote: > Yes, multiple imap servers using one shared nfs storage. With the same > config on 2.2.13 the public interface traffic was similar to the > storage interface, around 100 mbps. > > After we switch to 2.2.27 the storage interface traffic jumped 10 > times while the public interface stayed the same. This make us > thinking that

>On Mon, Oct 15, 2018 at 08:50:21AM +0000, Raymond Sellars wrote: > > Hi > > Looking for some insight into mdbox index file management and recovery from corruptions. > What version of dovecot and what OS are you running? Is NFS linux/bsd/netapp/etc? [Raymond] Linux 2.6.32-279.19.1.el6.x86_64 Red Hat Enterprise Linux Server release 6.7 (Santiago) - its selectively patched

Hi, we start to run out of diskspace soon as our users start to keep mails for longer time periods. That's fine, but space consuming. The maildirs are about 1 TB in total, and not long ago we enabled zlib which is very nice. Now I have some thoughts about the next steps: a) Migrating the whole system to a new server with more storage? b) Install a virtual server for the mailsystem and an

Are you connecting to the same mailbox over NFS from multiple IMAP servers? If not and, at any given time, any mailbox will be accessed from a single NFS client, try to "dupe" Dovecot into thinking it's not using NFS. We're running quite successfully such setup with NFSv3 over TCP, which turned out to be the fastest and most reliable throughout the years. Here are the mount

Yes, multiple imap servers using one shared nfs storage. With the same config on 2.2.13 the public interface traffic was similar to the storage interface, around 100 mbps. After we switch to 2.2.27 the storage interface traffic jumped 10 times while the public interface stayed the same. This make us thinking that something is wrong and each time a user logs in the whole Inbox content is read

Is it possible to setup the following: 1. Primary mailserver with SMTP solutions and Dovecot. 2. Primary server will store recent mails. 3. Secondary server for archival storage and Solr. So I'm not looking for a distributed cluster - simply a splitting of designated functions. Clients would only be connecting to the primary server. I know Dovecot supports an alternate storage location -