search for: nolocks

Greetings, I made some search on Google regarding this matter and found many diverse information, some dated back to 2004, and would like to update and clarify this issue. The question is: "what's the problem on re-sharing a NFS filesystem with Samba?". The only way I found to share a NFS mount point on Samba without apparent problem is to disable file locking on NFS mount by

This idea is from ext4. By this patch, we can make the dio write parallel, and improve the performance. We needn''t worry about the race between dio write and truncate, because the truncate need wait untill all the dio write end. And we also needn''t worry about the race between dio write and punch hole, because we have extent lock to protect our operation. I ran fio to test the

Hello, We have a VM (under KVM - a VPS service by our ISP) running CentOS 7. On it we have 2 NFS mounts, one for backup and one as a live file system (where there are two user homes as well): ----------------------------------------------------------------------------------------------------------------------- # cat /etc/fstab /dev/mapper/centos-root / xfs defaults

In order to do some custom stuff after starting shorewall, I found that I wanted a "started" hook, as well as the "start" one. This small patch adds it to the firewall script. I didn''t include a started script in the patch but it can be copied from /etc/shorewall/start. I hope this is useful to you, Nick

On 2/6/2017 1:46 ??, Nikolaos Milas wrote: > After a bit of search, I found the associated reports: > > https://bugs.centos.org/view.php?id=13351 > https://bugzilla.redhat.com/show_bug.cgi?id=1454876 > > No solution yet, but -as a workaround- it seems that -at least- nfs > problems are indeed solved with downgrading. I have been working fine with CentOS 7.3, since I

Hi, I created a modification (more like a hack) to shorewall that backups a configuration after succesfully (re)starting it. In case a future (re)start fails it will use this backup configuration. (instead of stopping the firewall and generating a massive ammount phonecalls ;) I didn''t pay too much attention to the ramifications of this patch, so let me know if i screwed anything up.

> -----Original Message----- > From: JR Richardson [mailto:jmr.richardson@gmail.com] > Sent: Saturday, June 17, 2006 2:30 PM > To: asterisk-users@lists.digium.com; Douglas Garstang > Subject: Voicemail with NFS (working, I think) > > I'm using a stand-alone VM server and exporting the VM files ro for > MWI function only. All my registration servers mount the remote

Hi, everybody! My pxelinux.0/default file is: LABEL linux KERNEL vmlinuz-2.6.16 APPEND initrd=initrd-2.6.16.img root=192.168.4.110:/clients/192.168.4.100/root When mounting I get: switchroot: mount failed: 22 Kernel panic - not syncing: Attempted tp kill init! Before it I get some messages about: Can't find /dev/console. /clients/192.168.4.100/root/dev was empty. I've copied my

hey, Ive got your syslinux booting a floppy disk that boots an image via NFS just fine and dandy.. default linux-jason prompt 1 display boot.msg timeout 100 label linux-jason kernel vmlinuz append append=root=/dev/nfs rw nfsroot=xx.xx.xx.xx:/var/local/user/thinpc,rw,v3,rsize=32768,wsize=32768,hard,udp,nolock,posix vga=792 ip=dhcp label linux-egg kernel vmlinuz

Hello all, I have observed a problem with a diskless PXE client I am attempting to configure. PXE/NFS/DHCP/TFTPd server is running CentOS5.1 and the Diskless workstation's root and kernel was extracted from a CentOS5.1 (custom kernel due to setting to enable Root File System support). Problem: When the diskless client boots and logs in I notice that my root user is being squashed, even if I

On 07 Apr 2016, at 14:49, Tom Sommer <mail at tomsommer.dk> wrote: > > On 2016-04-06 21:09, Tom Sommer wrote: >> On 2016-04-06 20:38, Timo Sirainen wrote: >>> On 06 Apr 2016, at 13:43, Tom Sommer <mail at tomsommer.dk> wrote: >>>> I'm switching quota backend to redis (from maildir++), so all my current usages are reset. >>>> I get that

Hi I am hitting this Warning reproducible, the workload is a ceph osd, kernel ist 3.1.0-rc5. Best Regards, martin [ 5472.099766] ------------[ cut here ]------------ [ 5472.099833] WARNING: at fs/btrfs/inode.c:2193 btrfs_orphan_commit_root+0xb0/0xc0 [btrfs]() [ 5472.099838] Hardware name: MS-96B3 [ 5472.099842] Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit psmouse sp5100_tco

On 3/5/2017 10:41 ??, Marcelo Roccasalva wrote: > Does the UUID of root filesystem in /etc/fstab match the actual UUID > as reported by blkid? And remove/etc/lvm/cache/.cache if it exists Thank you Marcelo for replying, The directory /etc/lvm/cache/ is empty. And, yes, the UUID matches: # blkid /dev/vda1: UUID="297e2939-d6f5-431a-9813-9848368ee306" TYPE="xfs"

Hi all We are using a 2 node cluster with drbd 8 (primary/primary state) and ocfs2. Reading a file on one node while it will be written on the other node is very slow. Reading a file on node while it will be written on the same node is fast. In the first case the node which wants to read the file has to ask the other to downgrade the locklevel. In my opinion this is a bottleneck, if the files are

So, I have a test domain set up with rfc2307 = yes . Now I'm trying to figure out if a) my nfs automount data came over from OpenLDAP, and b) if not, how to get it into samba 4's ldap, or something else??? Do I need to rethink my approach? Mount locations are pretty consistent based on primary group/userid Needs to work on Linux. Existing entries look like this... # /u,

Hello nuters, FreeBSD, Ellipse USBS 800, serial line, nut 2.02 everything works fine. But I'm only able to get an automatic shutdown when reaching the built-in 30% level. I the "lowbatt parameter" is set to anything, it's simply ignored. This is a problem as I want to shutdown around 90% to avoid the battery to drain out when multiple shutdowns occur. Any idea ?

libxkbfile is used by the X servers and utilities to parse the XKB configuration data files. This release adds support for the NoLock, NoUnlock, and genKeyEvent flags. Alan Coopersmith (5): Remove obsolete B16 & B32 tags in struct definitions Update README for gitlab migration Update configure.ac bug URL for gitlab migration Add description of libxkbfile to README.md

On 22/9/2017 2:58 ??, Nikolaos Milas wrote: > ... > or through /etc/fstab: > > ? 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2?? nfs > auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 Correction: the /etc/fstab nfs mount line has one more zero: ? 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2?? nfs

Hello I'm trying to mount a nfs system. But i receive this message: mount -t nfs <IP>:/backup /backupnfs mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified After a fews searchs on google i tried to execute the files: sbin/rpc.statd

Hi there, I'm getting a lot of this message in production log: Created dotlock file's timestamp is different than current time (1232468644 vs 1232468524): /path/to/dovecot.index.log The IT guy swears the clocks are sincronized. Whe even have made a test in the machine running dovecot, inside the user's mailbox: # > foo; ls -l --time-style=full-iso foo; date -rw-r--r-- 1 root root