similar to: stale file handle issue

Hi, I usually run "rsync -av" so I can see all the files that have been modified. However, "rsync -av" always claims to be updating write protected directories, even when they have not been changed. I do not understand why. Here is an example using rsync version 2.6.3 on FreeBSD 5.3. I get similar results with rsync 2.6.0 on Gentoo Linux. -------- $ mkdir dir0 $ touch

*sigh* The answer is that the large exported filesystem is a very large XFS... and at least through CentOS 6, upstream has *never* fixed an NFS bug that I find, googling, being complained about in '09: it gags on inodes > 32bit (not sure if that's signed, or unsigned, but....). The answer was to either create, or find an unneeded directory with a < 32bit inode, rename the

Hi all, I'm trying to setup this scenario on NFS and autofs on Centos 4.3: - useradd nfstest on an NFS server (192.168.1.247) - Setting up this NFS server /etc/exports: /home/nfstest 192.168.1.252/255.255.255.0(rw,sync,no_root_squash) - useradd nfstest on a client machine (192.168.1.252) - make sure that the uid and gid are the same on the server and the client - setting up

Hi, we have a problem with permissions migrating from a custom 2.4 kernel Linux distro with Samba 2.2.5 to OpenSuSE 10.3 (with samba 3.0.26). We used to have directories like this (relative to the Samba share): /root/dir0/dir1/dir2/dir3/userdir1-1/userdir1-2 'root' and all it's parent directories have '0755' Linux permission. dir0-dir3 all have '0711' permissions

On Wed, November 4, 2015 11:59 am, m.roth at 5-cent.us wrote: > *sigh* > > The answer is that the large exported filesystem is a very large XFS... > and at least through CentOS 6, upstream has *never* fixed an NFS bug that > I find, googling, being complained about in '09: it gags on inodes > 32bit > (not sure if that's signed, or unsigned, but....). Mark, are you

this seems to be a bug and not a security issue having two shares on a samba server but on different disks it is possible to copy/delete a file from one share to another but not to move (using a win98 workstation). Using the same disk moving is possible. Some time before it was possible and Windows made the copy. Now it seems the samba-server has to copy and doesnt. this is samba 2.2.0.15,

We'll ignore that the group name for KDE changed, and so, since we had it on the same line as X, neither was installed. However, more of an annoyance: to get nfs working, I had to install: pam-krb5 ncsd then fix /etc/init.d/autofs (when I did a service restart, it told me automount was running, and did not stop it), then after some research, found I had to manually start rpcbind, *then*

I'm having a problem with automount (autofs) from a server running CentOS 5.4 to clients (example is CentOS 5.4). Client pulls automount maps from NIS. THIS particular server is also used for login so it is NIS bound as well (other servers are NOT). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NIS Server Side... (content shortened)

I added Domain = ourdomain to /etc/idpmapd.conf, and restarted rpc-idmapd, then autofs. And nfslock, for good measure. service nfs-idmap status Redirecting to /bin/systemctl status nfs-idmap.service nfs-idmap.service - NFSv4 ID-name mapping daemon Loaded: loaded (/usr/lib/systemd/system/nfs-idmap.service; disabled) Active: active (running) since Thu 2015-04-23 11:23:24 EDT; 2min 59s ago

Hi all. I have one server with problem in maillog: Feb 6 06:46:26 host1 postfix/qmgr[24296]: fatal: qmgr_move: update active/4DE015AC536 time stamps: Stale NFS file handle Feb 6 06:46:27 host1 postfix/master[4487]: warning: process /usr/libexec/postfix/qmgr pid 24296 exit status 1 Feb 6 06:46:27 host1 postfix/master[4487]: warning: /usr/libexec/postfix/qmgr: bad command startup -- throttling

I have an odd automount problem. The first time I look in an automounted filesystem (when the mount is requested), it is empty; the second time it is not. Moreover, I only see this behavior on Centos 4.x systems, but not on Centos 5.0 systems going to the same fileserver. Here's an example, with some details simplified to clarify. In this example, fileserver1 is exporting fs1.

Hello all, I have a few strange errors in my messages log I can't fix. My system works great, it just bugs me that I have error (or apparent errors) that I don't know about. I get automount errors regurlarly (daily) that are reflected in the last four lines of the log file excerpt below. My misc and net directories are there, but I can't write to them either. The properties say that

I have an issue with CentOS 6.2's autofs/automount. When I issue "service autofs start (or restart)" the automount daemon starts as expected, however, I am not able to access any of the exports nfs directories; but if I shutdown the automount daemon and start it by just issuing "/usr/sbin/automount", I am able to access all of the nfs directories. If the system reboots,

On Wed, Aug 23, 2017 at 12:03:12PM -0700, Gordon Messmer wrote: > On 08/21/2017 07:23 PM, Fred Smith wrote: > >so, in my case, the USB drive contains an xfs filesystem. would I > >do something like this: > > > >in /etc/auto.master: > >backup /etc/auto.backup > > > >and in /etc/auto.backup > >backup -fstype=xfs,defaults,noauto,users

I haven't seen this on the linux-security list so I thought I'd forward it on for your review. It was pulled from Bugtraq by one of our sys admins. Dan _______________________________________________________________________________ Dan Yocum | Phone: (630) 840-8525 Computing Division OSS/FSS | Fax: (630) 840-6345 .~. L Fermi National

Alle, I'm following the instructions in section 19.3.3.2 of the docs @ http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s2-nfs-config-autofs-LDAP.html, but I cannot add the following entry in LDAP: dn: automountMapName=auto.home,dc=subaru,dc=nao,dc=ac,dc=jp objectClass: top objectClass: automountMap automountMapName: auto.home After looking at the schemas in /etc/openldap/schema,

Hi, What is the magic juju that I have to put in /etc/sysconfig/autofs to get autofs to default to using NFSv4, rather than NFSv3, for mounting file systems? I don't want to place these flags into the automount maps themselves because we have a varied network with Sun, CentOS, RedHat and Macintosh systems, and the flags that have to get added to automount maps (which we distribute centrally

Hi, We've been using autofs and LDAP automount maps for years now, and it has worked well. We run an environment that has CentOS, RHEL, Solaris and FreeBSD servers and clients. Historically, all our automount maps have looked like this: -vers=3 server:/export/home/& However, we're switching to NFSv4 and therefore we need to remove the -vers=3 flag. For CentOS 6.3, Solaris and

To get the automount schema to work with the git checkout of samba 4 I had to modify the automount schema files and separate the attributes from the classes. I also discovered that it's required to have the ntSecurityDescriptor , instanceType, and objectCategory attributes. Without these it will crash whenever you try to browse... I did alot of stopping samba, tarring of /usr/local/samba and

Hello all This patch tries to remove a few bugs from smbmount. It would be nice to get some testing+feedback on this from others using smbmount and possibly get these things fixed for the next release of samba. It does the following: * Change lib/debug.c to allow changing your mind on being interactive. A second call to setup_logging should now replace the effects of a previous call. (hmm,