summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-October/019117.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2012-October/019117.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-dev/2012-October/019117.html')
-rw-r--r--zarb-ml/mageia-dev/2012-October/019117.html93
1 files changed, 93 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-October/019117.html b/zarb-ml/mageia-dev/2012-October/019117.html
new file mode 100644
index 000000000..bd3ad2d25
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-October/019117.html
@@ -0,0 +1,93 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Any progress on the NFS mount problem? - SOLVED
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Any%20progress%20on%20the%20NFS%20mount%20problem%3F%20-%20SOLVED&In-Reply-To=%3C9b144deb1139469428f039a5a45bfcc1.squirrel%40mail.rmail.be%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="019113.html">
+ <LINK REL="Next" HREF="019119.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Any progress on the NFS mount problem? - SOLVED</H1>
+ <B>AL13N</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Any%20progress%20on%20the%20NFS%20mount%20problem%3F%20-%20SOLVED&In-Reply-To=%3C9b144deb1139469428f039a5a45bfcc1.squirrel%40mail.rmail.be%3E"
+ TITLE="[Mageia-dev] Any progress on the NFS mount problem? - SOLVED">alien at rmail.be
+ </A><BR>
+ <I>Tue Oct 2 12:18:15 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="019113.html">[Mageia-dev] Any progress on the NFS mount problem? - SOLVED
+</A></li>
+ <LI>Next message: <A HREF="019119.html">[Mageia-dev] Any progress on the NFS mount problem? - SOLVED
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#19117">[ date ]</a>
+ <a href="thread.html#19117">[ thread ]</a>
+ <a href="subject.html#19117">[ subject ]</a>
+ <a href="author.html#19117">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>&gt;<i> 'Twas brillig, and Guillaume Rousse at 01/10/12 21:41 did gyre and gimble:
+</I>&gt;&gt;<i> With NFSv4, the server remaps its actual filesystem (/home, for
+</I>&gt;&gt;<i> instance) in a pseudo-filesystem, which is seen by clients as a root
+</I>&gt;&gt;<i> filesystem (/ here). Consider it as some kind of implicit chroot.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> With earlier implementations, you had to explicitely mark one of the
+</I>&gt;&gt;<i> filesystem as the root one, and make sure every other filesystem was
+</I>&gt;&gt;<i> reachable from it, using bind mount if needed. You've got some more
+</I>&gt;&gt;<i> detailed explanations here:
+</I>&gt;&gt;<i> <A HREF="https://wiki.archlinux.org/index.php/NFS">https://wiki.archlinux.org/index.php/NFS</A>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> According to official NFS wiki, it seems this is no longer needed, and
+</I>&gt;&gt;<i> than the implementation handle it automagically for you:
+</I>&gt;&gt;<i> <A HREF="http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration#Exporting_directories">http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration#Exporting_directories</A>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> I removed 'fsid=0', restarted, and all is well. I
+</I>&gt;&gt;&gt;<i> can see all my data!
+</I>&gt;&gt;<i> Well, you'd better check if you're actually using NFSv4, and not a older
+</I>&gt;&gt;<i> version, if you want optimal performances.
+</I>&gt;<i>
+</I>&gt;<i> FWIW, I found I needed fsid=0 on my media center's chroot export when
+</I>&gt;<i> using an NFS root boot (server + client both mga2).
+</I>&gt;<i>
+</I>&gt;<i> Without fsid=0 root was mapped to 65534 which caused numerous issues
+</I>&gt;<i> when booting :)
+</I>&gt;<i>
+</I>&gt;<i> Never did work out the full reasons, so I probably need to read those
+</I>&gt;<i> specs a bit.
+</I>
+FWIW: my mga2 server and mga1 chrooted client don't need fsid=0 . but then
+i'm using nfsver=3; don't want to be using nfsv4
+
+</PRE>
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="019113.html">[Mageia-dev] Any progress on the NFS mount problem? - SOLVED
+</A></li>
+ <LI>Next message: <A HREF="019119.html">[Mageia-dev] Any progress on the NFS mount problem? - SOLVED
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#19117">[ date ]</a>
+ <a href="thread.html#19117">[ thread ]</a>
+ <a href="subject.html#19117">[ subject ]</a>
+ <a href="author.html#19117">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>