similar to: inconsistent file content after killing nfs daemon

Hi, I have an ext3 file system on top of LVM and i use journaled mode. I would like to make a snapshot of my filesystem while the application is running in order to backup on another physical storage. For that i have to create an LVM snapshot and then to mount it in read-only for copying the content. This is not possible as far as ext3 needs to do a log replay at mount time ( AFAIK). I would

Hi A new setup Windows client fails to authenticate to my Samba server (3.0.24-SerNet-RedHat). What I see in log at level 10 is: Got user=[SA-MC-SMSNS@corproot.net] domain=[] workstation=[MSISMSSRV01P] len1=24 len2=122 The empty domain seams to be origin of the problem, for other systems working OK this field is not empty. The Windows client is: NativeOS=[Windows Server 2003 R2 3790 Service

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Background: Large NFS/mail server. Dual PIII/1GHZ. 4GB memory. Mylex AcceleRAID 352 RAID controller (uses DAC960 driver). Intel eepro100 network cards. RedHat 7.3 with all errata. Kernel-2.4.18-5smp. 2GB of memory is used by a RAM disk for mail queue. ext3 filesystems (switched to ext2 to see if that helps). one large (100GB data partition).

On 08/31/2015 01:39 PM, Mark Selby wrote: > I have seen some talk about this but have not seen any answers. I know > this is a problem on CentOS 7.1 and I also think it is a problem on > CentOS 7.0. > > Basically if I have an NFS client only config - meaning that the > nfs-server.service is not enabled then I have to wait 60 seconds after > boot for the 1st NFSV3 mount to

Hi I have several Samba servers which have been running for almost two years without any problem. Recently I rebooted one of those servers and have the following problem: the join to the domain is OK but all user authentications fail. I mean nobody can "connect" a share. The system I rebooted is half of a two node cluster, the other node with exactly the same configuration, up 230 days,

I have seen some talk about this but have not seen any answers. I know this is a problem on CentOS 7.1 and I also think it is a problem on CentOS 7.0. Basically if I have an NFS client only config - meaning that the nfs-server.service is not enabled then I have to wait 60 seconds after boot for the 1st NFSV3 mount to succeed. What I can surmise is the following. I attempt to perform a NFS

That is the thing - rpc.statd does have rpcbind a pre-req. It looks like systemd is not handling this correctly. Just wondering if anyone knows a good way to fix. root at ls2 /usr/lib/systemd/system 110# grep Requires rpc-statd.service Requires=nss-lookup.target rpcbind.target On 8/30/15 7:45 PM, Rob Kampen wrote: > On 08/31/2015 01:39 PM, Mark Selby wrote: >> I have seen some talk

[ adding klibc ml to cc ] On Thu, Feb 01, 2007 at 09:29:52AM -0600, John Goerzen wrote: > > It appears to be largely undocumented, but a review of > /usr/share/initramfs/scripts/nfs shows that this package supports NFSv2 > and v3 only. I don't know why v4 isn't supported. yup, this needs nfs v4 support in klibc nfsmount. would be could to get that soon postetch, but someone

Hi, I've never been using NFS before, but I'm going to need it. I gathered some documentation (Deployment Guide, RHEL 5 Unleashed, general NFS docs) and I have a few machines to experiment with. After about two hours of reading and experimenting, I must admit the documentation is confusing, to say the least. Although some step-by-step tutorials are provided, none of them work. For

Hi, The following set of patches is intended mostly to improve ipconfig and nfsmount compatibility with glibc. The context: I'm working on yaird, an alternative to mkinitrd, and currently implementing nfs root file systems. This is based on ipconfig and nfsmount from klibc, with a rewritten version of kinit. Users should be able to build the package with vanilla glibc, since klibc is not

We have DELL 2650 server and I found recently /var/log/messages have following messages continue pop-up: =========================================== Dec 3 15:47:06 HOST1 kernel: Free pages: 17816kB (1664kB HighMem) Dec 3 15:47:06 HOST1 kernel: Active:7463815 inactive:656000 dirty:0 writeback:0 unstable:0 free:4454 slab:119979 mapped:730440 pagetables:63277 Dec 3 15:47:06 HOST1 kernel:

Just two fixes: - dovecot-uidlist file is now assumed to be changed if it's modify time is changed. before we relied on inode changing which isn't fully reliable. - mbox dotlocks sometimes incorrectly thought someone else had overridden them Known problems that I should fix: - mbox: we don't necessarily notice message flag changes by external programs (or another dovecot without

Hi, I've seen some chatter on NFS boards about kqueue being more reliable than inotify when used in NFSv3 and NFSv2. The chatter is a bit old so I don't know if it is true anymore. Anyone have pro/con experience with dovecot on the inotify/kqueue question when using NFS storage? I realize that kqueue is probably a bit slower and causes some delay with IDLE. Also, it may not really

I am facing dovecot authentication problems caused by unresponding NFS server. If there is even short break in communication with NFS server keeping maildirs, the dovecot generates the avalanche of processes (dovecot/imap and dovecot/pop3). The real number of connections was about 50 and after the problems occurs it rises to 1000. After about 3 hours the limit of connections is filled up:

Hello, I'm migrating from 1.1.16 running in 4 debian lenny servers virtualized with xenserver and 1 core and 5GB of RAM to 2.1.5 running in 4 ubuntu 12.04 servers with 6 cpu cores and 16GB of RAM virtualized with VMWare, but I'm having lots a performance problems. I don't think that virtualization platform could be the problem, because the new servers running in xenserver has

HI, I'm pulling my hair out a little trying to get dovecot to save it's index locally rather than in the NFS mount. No matter what I do it seems to save the indices in the Maildir on the NFS. I'm using dovecot 2.0.18 on CentOS 6.3. The relevant config I'm using: mmap_disable = no dotlock_use_excl = no # only needed with NFSv2, NFSv3+ supports O_EXCL and it's faster

I''m seeing some pretty pitiful performance using ZFS on a NFS server, with a ZFS volume exported (only with rw=host.foo.com,root=host.foo.com opts) and mounted on a Linux host running kernel 2.4.31. This linux kernel I''m working with is limited in that I can only do NFSv2 mounts... irregardless of that aspect, I''m sure something''s amiss. I mounted the zfs-based

A bit more detail. I have the following htb classes set up... class htb 1:356 parent 1:4 leaf 356: prio 4 quantum 1600 rate 12800bit ceil 51680bit burst 15Kb/8 mpu 0b overhead 0b cburst 1663b/8 mpu 0b overhead 0b level 0 class htb 1:357 parent 1:4 leaf 357: prio 4 quantum 1600 rate 12800bit ceil 51680bit burst 15Kb/8 mpu 0b overhead 0b cburst 1663b/8 mpu 0b overhead 0b level 0 class htb 1:2 root

I wrote a powershell script on a windows computer to write an ADS on a file on a FreeBSD server with streams_xattr enabled. If it's smaller than 64KB, it succeeds. If it's larger than 64KB, I get an "access denied message" and powershell crashes. FreeBSD actually allows creation of large extended attributes (at least on ZFS volumes). I've personally added ones of up to 3MB in

We are using Postfix as an MTA delivering via Dovecot's LDA (with sieve). We also use Dovecot as a POP/IMAP server. Mail storage is Maildir on NFS, indexes are stored locally. Quotas are FS quotas enforced by the NFS server. The Dovecot version is 1.2.11. Recently, for one user being over quota, some attempts to deliver mail bounced as expected while some others resulted in zero-sized Maildir