Results 1 to 3 of 3
So I set up a NFS share to avoid redundantly downloading distfiles. And simple copying of files works to the network drive but when I actually try to emerge a ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 01-16-2012 #1
- Join Date
- Mar 2011
NFS and Portage not getting along
So I set up a NFS share to avoid redundantly downloading distfiles. And simple copying of files works to the network drive but when I actually try to emerge a new package it fails with a permissions issue that I need help figuring out.
My portage error:
>>> Emerging (1 of 2) kde-base/libkdeedu-4.7.3 * Fetching files in the background. To view fetch progress, run * `tail -f /var/log/emerge-fetch.log` in another terminal. bash: /usr/portage/distfiles/.__portage_test_write__: Read-only file system Traceback (most recent call last): File "/usr/lib64/portage/pym/_emerge/EbuildFetcher.py", line 186, in _spawn allow_missing_digests=allow_missing): File "/usr/lib64/portage/pym/portage/package/ebuild/fetch.py", line 494, in fetch if ensure_dirs(mydir, gid=dir_gid, mode=dirmode, mask=modemask): File "/usr/lib64/portage/pym/portage/util/__init__.py", line 1264, in ensure_dirs perms_modified = apply_permissions(dir_path, **kwargs) File "/usr/lib64/portage/pym/portage/util/__init__.py", line 914, in apply_permissions os.chown(filename, uid, gid) File "/usr/lib64/portage/pym/portage/__init__.py", line 230, in __call__ rval = self._func(*wrapped_args, **wrapped_kwargs) OSError: [Errno 22] Invalid argument: '/usr/portage/distfiles/' * Fetch failed for 'kde-base/libkdeedu-4.7.3', Log file: * '/var/tmp/portage/kde-base/libkdeedu-4.7.3/temp/build.log' >>> Failed to emerge kde-base/libkdeedu-4.7.3, Log file: >>> '/var/tmp/portage/kde-base/libkdeedu-4.7.3/temp/build.log' * Messages for package kde-base/libkdeedu-4.7.3: * Fetch failed for 'kde-base/libkdeedu-4.7.3', Log file: * '/var/tmp/portage/kde-base/libkdeedu-4.7.3/temp/build.log'
/usr/portage/distfiles 10.10.10.* (sync,rw,no_subtree_check,root_squash)
/dev/sda1 /boot ext2 noauto,noatime 1 2 /dev/sda5 / ext3 noatime 0 1 # /dev/SWAP none swap sw 0 0 /dev/cdrom /mnt/cdrom auto noauto,ro 0 0 # /dev/fd0 /mnt/floppy auto noauto 0 0 /dev/sda6 /home ext3 noatime 0 0 proc /proc proc defaults 0 0 shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 #/dev/sda7 /usr ext4 nodev 0 0 distfile:/usr/portage/distfiles /usr/portage/distfiles nfs noauto,rw 0 0 # tmpfs /tmp tmpfs defaults,noexec,nosuid,rootcontext=system_u:object_r:tmp_t 0 0 # udev /dev tmpfs rw,rootcontext=system_u:object_r:device_t,seclabel,nosuid,relatime,size=10m,mode=755 0 0 # none /selinux selinuxfs defaults 0 0
What puzzles me is that portage complains about a read-only file system but the options I gave on the server and client should have it set as read-write. Unless it is a file ownership issue?
Last edited by bleedingsamurai; 01-16-2012 at 04:18 AM. Reason: additional info
- 01-16-2012 #2
- Join Date
- Mar 2011
I ended up fixing this after work today, with a bit of luck.
On my server's /etc/exports file, it did two things; first I removed the spaced between the hostname/IP range section and the mount permissions. And then I also turned off root squashing.
- 01-18-2012 #3
- Join Date
- Jan 2012
Dude! I have same problems!
Sometime I just want to throw my computer out of the window! It irritates me so much. My life would be better if I had MAC though.