Tag Info

Hot answers tagged

32

In a closed network (where you know every device), NFS is a fine choice. With a good network, throughput it disgustingly fast and at the same time less CPU intensive on the server. It's very simple to set up and you can toggle readonly on shares you don't need to be writeable. I disagree with Anders. v4 can be just as simple as v3. It only gets complicated ...


26

Stefan led me down the right track. This will work on any system 12.04 and newer. Your filesystem will also need extended attribute support. If you're using EXT4 you're fine, if you're using EXT3 you'll need to ensure your filesystem is mounted with the user_xattr attribute. Here's how I set it up on the client machine, you don't need to do anything on ...


10

There is pyNeighborhood which is a gui for mounting samba shares and available in the software centre for download. There is a good article located here on how to set it up and use it. Alternatively the basic terminal command is mount -t cifs -o username=USERNAME,password=PASSWD //192.168.1.88/shares /mnt/share Have a read through the Samba documentation ...


10

You can use umount -f -l /mnt/myfolder, and that will fix the problem. -f Force unmount (in case of an unreachable NFS system). (Requires kernel 2.1.116 or later.) -l Lazy unmount. Detach the filesystem from the filesystem hierarchy now, and cleanup all references to the filesystem as soon as it is not busy anymore. (Requires kernel 2.4.11 or later.) ...


8

I'm not sure if there is any way to do this currently with Ubuntu 10.04 LTS. However, the newer versions of the Linux kernel include a feature called FS-Cache & CacheFS, which sounds exactly like what you (and I) want. Also see Local Caching For Network Filesystems.


8

Whenever fsck goes through the system and tries to recover damaged files, it will put them into the lost+found folder. I guess this is basically a problem with fsck creating that folder even if there's nothing to put in. As Ubuntu periodically runs those checks on your partitions, those folders will always be re-created, so deleting it won't work. If you ...


7

Lets say that «boris» is my logon such as /home/boris is my home folder. 1. set the «server» computer: install nfs-kernel-server and nfs-common $ sudo apt-get install nfs-kernel-server $ sudo apt-get install nfs-common in /etc/exports, define the folder to be shared by adding this: /home/boris ...


7

Per this discussion on the Ubuntu Forums, install dconf-tools and then run the dconf editor (a launcher installed to "System Tools" on my machine). Navigate to org > gnome > desktop > media-handling and then check the "autorun-never" box. Then simply close the dconf editor.


7

I think you might be able to accomplish what you want using network block devices (NBD). Looking at the wikipedia page on the subject there is mention of a tool called nbd. It's comprised of a client and server component. Example In this scenario I'm setting up a CDROM on my Fedora 19 laptop (server) and I'm sharing it out to an Ubuntu 12.10 system ...


6

The error message mentions: (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount. helper program) This is relevant given that you are trying to mount NFS. The /sbin/mount.nfs helper program is provided by nfs-common.


6

try sudo umount -l {mountPoint} to do a "lazy unmount". Lets you move on with your life without waiting for the plumber to arrive.


6

I did some more research into this. Ubuntu is using the UFW, which is extremely easy to configure, yet very potent, at least for soho needs. So, the rpc.mountd listens on multiple ports by default thus you have to bind rpc.mountd to one port, then you can add an additional UFW rule to accept incoming connection on that particular port. To do so, open ...


6

That article is over 6 years old and shouldn't be followed. You can set up NFS sharing by following the documentation here: https://help.ubuntu.com/community/SettingUpNFSHowTo


5

NFS (version 3) will give higher performance and is quite easy to set up. The main problem is the complete lack of decent security. NFS (version 4) gives security but is almost impossible to set up. Samba will probably be a bit slower but is easy to use, and will work with windows clients as well..


5

Neither NFS nor LDAP support disconnected operation: i.e., when the laptop cannot reach the servers, it will not be able to access any NFS-mounted directories, nor will it be able to perform user lookups. Basically, it will be stuck. A couple of workarounds could be the following. Instead of mouting home directories via NFS, you could keep local ...


5

You can try eBox for the server, it has a very straightforward web interface, you can install it from the repositories, and has all the functionality you need. The whole process is documented in the Ubuntu Server Guide, check https://help.ubuntu.com/10.04/serverguide/C/ebox.html. However you still would have to take care of the configuration in the client ...


5

I finally manged to solve it. Here are the steps: Add mount.nfs from Ubuntu 10.04 to the initramfs image (copy it into the /usr/lib/klibc/bin folder.) Change the nfsmount line in /usr/share/initramfs-tools/scripts/nfs to: mount.nfs ${NFSROOT} ${rootmnt} -o nolock ${roflag} ${NFSOPTS} Update the initramfs image with either mkinitramfs or update-initramfs. ...


5

The value 0 has a special meaning when use with NFSv4. NFSv4 has a concept of a root of the overall exported filesystem. The export point exported with fsid=0 will be used as this root. Therefore include fsid=0 into /etc/exports and then do the following: mount -t nfs4 <serverip>:/ /localmount/point and not mount -t nfs4 <serverip>:/exports ...


5

It appears that nfs-common package should be installed in order to be able to mount NFS directories. When it's not, the mounting of an NFS directory results in the error I've got.


4

The mount.cifs command is provided by cifs-utils and mount.nfs by nfs-common. In general, when you're looking for a particular file and don't know which package provides it, you can search in the Ubuntu Repositories or in synaptic. Alternatively, you can use apt-file. If it is not installed, install it with sudo apt-get install apt-file and then update its ...


4

How to netboot using ELILO How to get EFI to netboot? You do not need any additional software to get EFI to start a netboot session. Any EFI machine can be configured to start a PXE/DHCP session IF it has a network adapter that has support for the UNDI/PXE protocol. Most modern cards do have such support. To enable netbooting, you need to go into the ...


4

[Having a] lost+found directory with a large enough size to contain a large number of unlinked files puts less of a burden on e2fsck to create the directory and grow it to the appropriate size. [fsck will attempt to create lost+found if it doesn't exist], but in the face of a corrupt filesystem, it can be more risky. Very old fsck's for other ...


4

Most Ubuntu users will be sharing there network with at least one Windows or Apple machine and samba is the only fully featured sharing service which is capable of being accessed by the majority of computers what ever operating system they happen to be using. Also the GUI method of setting up shares is the easiest to do for someone new to Ubuntu which means ...


4

It looks like the fstab format changed slightly. The following is a working line for the root partition: 192.168.0.1:/nfs-root / nfs rw,noatime,nolock,vers=3 0 0


4

Is your NFS server still up when you shut down your machine? If so, that seems to be a bug in the shutdown ordering in 10.10; the network interface must still be up in order to unmount NFS. I don't use 10.10 yet, so I can't confirm whether that's the case. But as a stopgap, you might try doing a soft mount instead of a hard one. Soft mounts allow the NFS ...


4

This question is a bit old but I thought I might share what solved this problem for me. I had this same issue after following the 12.04 server guide. Everything has worked well since I changed my /etc/fstab entry options to include nfsvers=3 per comment #6 in this bug report. My current fstab entry (working on three clients) is as below. ...


4

http://unfs3.sourceforge.net/ UNFS3 is a user-space implementation of the NFSv3 server specification. It provides a daemon for the MOUNT and NFS protocols, which are used by NFS clients for accessing files on the server UNFS3 being user space based, and not widely deployed, I wouldn't really trust it. nfs-kernel-server is linux's standard nfs server


3

Sharing UIDs Assuming that the NAS is running a variant of Linux, and you have root access (if not I guess you need to ask QNAP), you have three options: Manually sync /etc/passwd between the two boxes (passwd is the file that contains the username/userid mapping). LDAP NIS If there are just a few users that don't change very often, the manual sync is ...


3

You should change the permissions of /import folder (as you mentioned 12.04 box) so that you can have write access.


3

I was experiencing a similar problem after upgrading to 12.04 and solved it by adding the nfsvers=3 option to the fstab entry for the NFS mount. The NFS filesystem was being exported using version 3 and there appears to be a problem in Ubuntu 12.04 and 11.10 with detecting that since version 4 is tried first. See the following bug report: ...



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