Re: NFSv4 Kernel-server requires 2x manual restart after reboot? Maybe a timing problem?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Bruce,

On Fri, Oct 23, 2009 at 10:27 AM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote:
> On Fri, Oct 23, 2009 at 10:07:23AM -0700, Ben DJ wrote:
>> I've installed NFSv4 as nfs-kernel-server.
>
> What distro and versions are you using?

I'm currently working on Opensuse 11.2 RC1.

At the moment,

kernel-default-base-2.6.31.3-1.1.x86_64
kernel-default-2.6.31.3-1.1.x86_64
kernel-default-devel-2.6.31.3-1.1.x86_64

quota-nfs-3.17-3.1.x86_64
nfsidmap-0.21-3.14.x86_64
nfs-doc-1.1.3-20.1.x86_64
nfs-client-1.1.3-20.1.x86_64
nfs-kernel-server-1.1.3-20.1.x86_64


> Huh.  What filesystem is at /nfs/test?

I'm not entirely sure what you're asking for.

/nfs/test is on my "/" volume, which is ext3 (someday, ext4 -- but not yet).

Is that what you mean?

Also I found that switching from mounts in /etc/fstab to using autofs
gets rid of the mount-after-boot issues

cat /etc/auto.master
	/test /etc/auto.misc
cat /etc/auto.misc
	cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom
	nfs4_test -fstype=nfs4,rw 192.168.1.2:/
chkconfig autofs on
reboot

But now, immediately after reboot,

ls /test/nfs4_test/
	bin/  boot/  dev/  etc/  home/  lib/  lib64/  lost+found/  media/
mnt/  mnt.auto/  nfs/  opt/  proc/  root/  sbin/  selinux/  srv/  sys/
 tmp/  usr/  var/

which is mounted, and feels like progress.

But the mount is of 192.168.1.2's "/" root.  I expected the NFSv4
exported-root @ /nfs, instead.

Thanks for your time.

BenDJ



Thanks.

BedDJ
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux