Tag Info

Hot answers tagged

12

sync and async have different meanings for the two different situations. sync in the client context makes all writes to the file be committed to the server. async causes all writes to the file to not be transmitted to the server immediately, usually only when the file is closed. So another host opening the same file is not going to see the changes made by ...


5

The issue you're highlighting is not a flaw, it's a feature! Yes it's a feature of the SSH protocol and giving that improperly configured SSH service can be used for a wide range of exploits like: Bypassing host firewalls Bypassing IP restrictions Remotely accessing services which listens only on 'localhost' interfaces [mysql?] As an example of common ...


4

yum -y install nfs-utils portmap Prepare and modify /etc/exports for sharing files, that would similar to as shown below /home/NFS-files 192.168.100.0/24(ro,sync) /home/NFS-share */26(rw,sync) /ISO 192.168.100.0/24(ro,sync) service portmap start service nfs start


4

Did you issue the command using sudo so you have elevated privileges? Rsync might also work better for something like that. I'd caution against considering it a backup, as it's just a copy. Backups protect against corruption issues or deleted files. Making copies is more like protecting availability of resources.


4

That's a very old document your looking at it talks about kernel version 2.4 which came out in 2001, a lot have changes have happened in the last 12 years. Although some things remain the same. I only have CentOS 6.x boxes to play with which uses nfsv4 by default. To allow the connection via an intermediate machine I had to export the filesystem with ...


3

Problem solved. Looks like the /etc/syconfig/network file had dos characters in it.. dos2unix /etc/sysconfig/network solved it.


3

lookup(program) means automount thinks your map is an executable, does it have the executable bit set? lookup(file) is what you should be seeing See http://www.squarebox.co.uk/cgi-squarebox/manServer/automount.8.


3

Mac OS X 10.4 Tiger uses NetInfo database, which was discontinued in 10.5 Leopard. For 10.4: nicl . -delete 116 clients 172.18.150.130 nicl . -delete 116 clients 172.18.150.138 nicl . -append 116 clients 172.18.150.132 nicl . -append 116 clients 172.18.150.134 Then restart the NFS server.


3

I found the answer to this here: http://sophiedogg.com/?p=141 /var/lib/nfs/statd/sm/ - directory containing statd monitor list /var/lib/nfs/statd/sm.bak/ - directory containing statd notify list Before removing these files, you should stop the rpcbind, statd, and lockd services. Below is a list of commands to run to fix this issue on a RPM based ...


3

It's more of a hindsight suggestion, but in general you should place snapshots of directory dir residing in a parentdir in parentdir or in subdirectory of parentdir, not in dir. So that you'd have directory hierarchy similar to this: parentdir ├── dir │   ├── Apps │ └── Clients └── snapshots    ├── @GMT-2012.01.30-13.00.01 │   ├── Apps │ └── ...


3

No, this is not possible with a single NFS export on kernel based nfs server. As exports(5) manual says: The file /etc/exports contains a table of local physical file systems on an NFS server that are accessible to NFS clients. However you can export parts of the tree and reassemble them on the clients with bind. Symbolic links Another palliative ...


2

Add the hostnames that will connect to your server to the /etc/hosts file. Make sure the /etc/nsswitch.conf file lists 'file' in the dns line (it's the default). There is no way to tell the code NOT to look up hostnames so you must "cheat" by forcing it in /etc/hosts.


2

the only thing I can tell you is that we have some NFS servers running lenny without any problems at all. The hardware is old (proliants g4, if I recall correctly, I am not at work now) but the disks are fast scsi 15krpm, so that's what basically matters. Debugging nfs problems can be frustrating. I found that this helps you get more info from the logs: * ...


2

You can try using umount -f to forcibly unmount. Depending on disk activity, it hasn't always worked for me; sometimes I've had to cycle the machine (unless I could restore the service). For the future, you can look into whether mount_nfs arguments -i (interruptible), -s (soft mount), or -Rn (maximum retry count) are appropriate for your environment. I ...


2

There's been some work recently to speed up directory access, which will be in Cygwin 1.7.8. That's expected to be released some time in January, but you could try the latest snapshots at http://www.cygwin.com/snapshots. Also, you might want to avoid symlinks in the path, as they cause additional overhead. You could mount the directories in question ...


2

On scaling up, the EBS volume and its data will not be "cloned". To have this behavior you'd want to automate it at boot. Grab the latest snapshot of WS-1 EBS volume Create and attach the volume Another method, depending on how much data is on the EBS, is to pull it down from S3. With the security group, you can allow any server in the ...


2

Large MSDOS filesystems are not supported as NFS exports on FreeBSD due to some implementation limitations. You could try if you can successfully mount the FS without the -o large option, but if that fails, you will be out of luck with NFS (but maybe you could try Samba instead).


2

in case anyone comes across this... I had the exact same symptoms with oracle / red hat 6.4 install and basic nfs setup. service start rpcbind, no response and service always stopped. Same with service nfs start. echo $? gave back a 6. This link led me to look at the startup script and in my case was failing at: # Check that networking is up. [ ...


2

Great questions, highlights a bigger point with the documentation IMO. Here is an attempt at a complete answer: What does "subsequent exports on that line only" mean? An example's probably easiest here: /export/stuff -rw 10.0.0.54 10.0.0.55 is equivalent to: /export/stuff 10.0.0.54(rw) 10.0.0.55(rw) Is fsid=0 not required anymore? This depends on ...


2

The spammy log messages you see are coming from the ocf:heartbeat:exportfs resource agent. They appear every 30 seconds, which corresponds to the monitoring interval you specified in the exportfs primitive definitions. The resource agent is a bit too verbose, IMHO, but this should not be a problem. Just make sure you logrotate often enough that the logs ...


2

You can use either lsof or ftop (the last one is on EPEL repo) For example: lsof -N /mnt/nfs/* HTH


2

That document is rather old (2006!). In the absence of better security mechanisms (i.e. NFSv4 + GSS) adding a host to exports means you implicitly trust that host, its users and processes. SSH port-forwarding isn't your only problem, you can disallow it (sshd's AllowTcpForwarding no), but as sshd_config(5) says Note that disabling TCP forwarding does ...


2

Simple solution i use at work working well and no security problem so far: autofs You can find a lot of information about 'autofs' on the Net easily. Make sure each user folder are 'chmod 700' and owned by them. :-) Here is a quick sample of the config i use: Start NFS home directory automount: Now, on the NIS client, set up automount to handle /home. In ...


2

You can do this on the server in Crossbow using IPQoS to limit bandwidth in increments of 150KiB/s. You can do this on the client using the Linux tc command: Sources http://docs.oracle.com/cd/E23823_01/html/816-4554/ipqostm-1.html http://lartc.org/manpages/tc.txt


2

You should try the noatime option when mounting the remote filesystem in the client. From man 8 mount noatime - Do not update inode access times on this filesystem (e.g., for faster access on the news spool to speed up news servers). In my case, it improved write performance a lot.


2

The overlay fs provides a possibility to mount one filesystem on top of other one. You can use your nfs mount as lower fs and some local directory as upper fs. The local change will not be sent to the NFS server. More info: https://git.kernel.org/cgit/linux/kernel/git/mszeredi/vfs.git/tree/Documentation/filesystems/overlayfs.txt?h=overlayfs.current


2

In that case first match wins since the two expressions are of the same type. (A single host expression would win even if it came after the IP subnet expression because it has precedence.) See exports(5) for details.


2

If you set up Quotas in the shared file system (on the server side), the clients can't use more space than the quota set.


2

If you want to limit the amount of disk space each user (or group) is using, then you can set up disk quotas on the NFS server (as mentioned in another answer already). You can easily find tutorials about how to do that. Once disk quotas are enabled, you can set the maximum disk space each user is able to use (the default is not to have any limit, so you ...


1

Read the error message again. It says "euid is not dir owner" which means "the user with the id 5000 is not the owner of the directory". Correct that. Authentication is not the problem here. Authorization is. On the other hand: Don't do NFS that way with Dovecot! See http://wiki2.dovecot.org/NFS for details. And then NFS is no native service on Windows, ...



Only top voted, non community-wiki answers of a minimum length are eligible