[opensuse] NFS server exports fail ("does not support NFS export" ??) immediately after reboot; OK after running 'exportfs -r' twice. Help?
I've installed nfs-kernel-server nfs-kernel-server-1.1.3-21.1.x86_64 on 11.2. It's enabled chkconfig --list | grep nfs nfs 0:off 1:off 2:off 3:on 4:off 5:on 6:off nfsserver 0:off 1:off 2:off 3:on 4:off 5:on 6:off and configured as, cat /etc/sysconfig/nfs NFS_START_SERVICES="yes" USE_KERNEL_NFSD_NUMBER="3" NFS4_SUPPORT="no" MOUNTD_PORT="" REEXPORT_NFS="no" NFS_SECURITY_GSS="no" SM_NOTIFY_OPTIONS="" cat /etc/exports /usr/local/exports 192.168.1.7(ro,no_root_squash,sync,subtree_check) Everything works fine when I've set it up manually, but after each reboot, the dir is NOT exported. To get it to work, I have to exec twice,
exportfs -r exportfs: Warning: /usr/local/exports does not support NFS export. exportfs -r
then, at this point, the dir can be subscribed/mounted at the client, 192.168.1.7. The boot log shows grep -i nfs /var/log/boot.msg <notice -- Dec 16 03:33:02.613052000> service nfs start <notice -- Dec 16 03:33:03.362462000> service nfs done <notice -- Dec 16 03:33:06.862887000> service nfsserver start <notice -- Dec 16 03:33:08.504914000> Starting kernel based NFS server: mountd statd nfsd sm-notifydone <notice -- Dec 16 03:33:09.378610000> service nfsserver done Which isn't telling me anything that I understand :-/ Any ideas what I need to do to get the exports right immediately after boot? Thanks, BedDJ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ben DJ wrote:
I've installed nfs-kernel-server
nfs-kernel-server-1.1.3-21.1.x86_64
on 11.2. It's enabled
chkconfig --list | grep nfs nfs 0:off 1:off 2:off 3:on 4:off 5:on 6:off nfsserver 0:off 1:off 2:off 3:on 4:off 5:on 6:off
and configured as,
cat /etc/sysconfig/nfs NFS_START_SERVICES="yes" USE_KERNEL_NFSD_NUMBER="3" NFS4_SUPPORT="no" MOUNTD_PORT="" REEXPORT_NFS="no" NFS_SECURITY_GSS="no" SM_NOTIFY_OPTIONS=""
cat /etc/exports /usr/local/exports 192.168.1.7(ro,no_root_squash,sync,subtree_check)
Everything works fine when I've set it up manually, but after each reboot, the dir is NOT exported.
To get it to work, I have to exec twice,
exportfs -r exportfs: Warning: /usr/local/exports does not support NFS export. exportfs -r
then, at this point, the dir can be subscribed/mounted at the client, 192.168.1.7.
The boot log shows
grep -i nfs /var/log/boot.msg <notice -- Dec 16 03:33:02.613052000> service nfs start <notice -- Dec 16 03:33:03.362462000> service nfs done <notice -- Dec 16 03:33:06.862887000> service nfsserver start <notice -- Dec 16 03:33:08.504914000> Starting kernel based NFS server: mountd statd nfsd sm-notifydone <notice -- Dec 16 03:33:09.378610000> service nfsserver done
Which isn't telling me anything that I understand :-/
Any ideas what I need to do to get the exports right immediately after boot?
Thanks,
BedDJ
Where is your fsid setup? cat /etc/exports /export *.milkyway(fsid=0,rw,root_squash,sync,no_subtree_check) /export/home0 *.milkyway(rw,root_squash,sync,no_subtree_check) /export/home1 *.milkyway(rw,root_squash,sync,no_subtree_check) I believe this is a new requirement for nfs v4 requirement. -- Joseph Loo jloo@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, On Tue, Dec 15, 2009 at 9:05 PM, Joseph Loo <joseph.loo@dslextreme.com> wrote:
cat /etc/exports /export *.milkyway(fsid=0,rw,root_squash,sync,no_subtree_check) /export/home0 *.milkyway(rw,root_squash,sync,no_subtree_check) /export/home1 *.milkyway(rw,root_squash,sync,no_subtree_check)
I believe this is a new requirement for nfs v4 requirement.
I'm not using NFSv4,
NFS4_SUPPORT="no"
These are 'just' v3 exports. BenDJ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-12-15 at 20:15 -0800, Ben DJ wrote:
I've installed nfs-kernel-server
nfs-kernel-server-1.1.3-21.1.x86_64
The easiest way is to use the YaST nfs... module to do the initial setup.
on 11.2. It's enabled
chkconfig --list | grep nfs nfs 0:off 1:off 2:off 3:on 4:off 5:on 6:off nfsserver 0:off 1:off 2:off 3:on 4:off 5:on 6:off
...
Everything works fine when I've set it up manually, but after each reboot, the dir is NOT exported.
Check the logs to find out why.
To get it to work, I have to exec twice,
exportfs -r exportfs: Warning: /usr/local/exports does not support NFS export. exportfs -r
No. Just run "rcnfsserver start". - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkso08oACgkQtTMYHG2NR9UL0ACgkgeD9yuWPwxMFb7Qisi8fxqr SqkAniwx+SNzrftOrm0fH6yRTCvS6kzE =6SV2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Check the logs to find out why.
I did check the logs; nfs-related output was included above. Here it is again, cd /var/log egrep -i "nfs|export|rpc" messages warn xinetd.log boot.msg messages:Dec 16 17:22:16 server kernel: [ 52.732529] RPC: Registered udp transport module. messages:Dec 16 17:22:16 server kernel: [ 52.732531] RPC: Registered tcp transport module. messages:Dec 16 17:22:17 server kernel: [ 52.876301] FS-Cache: Netfs 'nfs' registered for caching messages:Dec 16 17:22:20 server kernel: [ 56.593151] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). messages:Dec 16 17:22:22 server rpc.statd[4784]: Version 1.1.3 Starting messages:Dec 16 17:22:22 server rpc.statd[4784]: Flags: messages:Dec 16 17:22:22 server rpc.statd[4784]: statd running as root. chown /var/lib/nfs/sm to choose different user messages:Dec 16 17:22:22 server kernel: [ 58.340840] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory messages:Dec 16 17:22:22 server kernel: [ 58.390305] NFSD: starting 90-second grace period warn:Dec 16 17:22:22 server kernel: [ 58.340840] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory boot.msg: <notice -- Dec 16 17:22:16.300545000> service rpcbind start boot.msg: <notice -- Dec 16 17:22:16.403054000> startproc: execve (/sbin/rpcbind) [ /sbin/rpcbind ], [ DO_FASTBOOT=no CONSOLE=/dev/console SELINUX_INIT=YES ROOTFS_FSTYPE=ext4 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 DO_BLOGD=yes REDIRECT=/dev/xvc0 COLUMNS=80 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x31a DO_CONFIRM=no RUNLEVEL=3 resume=/dev/VG0/SWAP PWD=/ SPLASHCFG= DO_QUIET=no PREVLEVEL=N LINES=24 HOME=/ SHLVL=2 DO_FORCEFSCK=no splash=silent SPLASH=no ROOTFS_BLKDEV=/dev/VG0/ROOT _=/sbin/startproc DAEMON=/sbin/rpcbind ] boot.msg:Starting rpcbind done boot.msg: <notice -- Dec 16 17:22:16.535920000> service rpcbind done boot.msg: <notice -- Dec 16 17:22:16.537364000> service nfs start boot.msg: <notice -- Dec 16 17:22:16.625064000> checkproc: /sbin/rpcbind 3786 boot.msg: <notice -- Dec 16 17:22:16.917116000> service nfs done boot.msg: <notice -- Dec 16 17:22:20.283317000> service nfsserver start boot.msg: <notice -- Dec 16 17:22:20.374815000> startproc: execve (/usr/sbin/xinetd) [ /usr/sbin/xinetd -pidfile /var/run/xinetd.init.pid ], [ DO_FASTBOOT=no CONSOLE=/dev/console SELINUX_INIT=YES ROOTFS_FSTYPE=ext4 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 DO_BLOGD=yes REDIRECT=/dev/xvc0 COLUMNS=80 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x31a DO_CONFIRM=no RUNLEVEL=3 resume=/dev/VG0/SWAP PWD=/ SPLASHCFG= DO_QUIET=no PREVLEVEL=N LINES=24 HOME=/ SHLVL=2 DO_FORCEFSCK=no splash=silent SPLASH=no ROOTFS_BLKDEV=/dev/VG0/ROOT _=/sbin/startproc DAEMON=/usr/sbin/xinetd ] boot.msg: <notice -- Dec 16 17:22:21.816270000> service ntp start boot.msg: <notice -- Dec 16 17:22:21.854281000> startproc: execve (/usr/sbin/rpc.mountd) [ /usr/sbin/rpc.mountd --no-nfs-version 4 ], [ DO_FASTBOOT=no CONSOLE=/dev/console SELINUX_INIT=YES ROOTFS_FSTYPE=ext4 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 DO_BLOGD=yes REDIRECT=/dev/xvc0 COLUMNS=80 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x31a DO_CONFIRM=no RUNLEVEL=3 resume=/dev/VG0/SWAP PWD=/ SPLASHCFG= DO_QUIET=no PREVLEVEL=N LINES=24 HOME=/ SHLVL=2 DO_FORCEFSCK=no splash=silent SPLASH=no ROOTFS_BLKDEV=/dev/VG0/ROOT _=/sbin/startproc DAEMON=/usr/sbin/rpc.mountd ] boot.msg: <notice -- Dec 16 17:22:22.125461000> startproc: execve (/usr/sbin/rpc.statd) [ /usr/sbin/rpc.statd --no-notify ], [ DO_FASTBOOT=no CONSOLE=/dev/console SELINUX_INIT=YES ROOTFS_FSTYPE=ext4 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 DO_BLOGD=yes REDIRECT=/dev/xvc0 COLUMNS=80 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x31a DO_CONFIRM=no RUNLEVEL=3 resume=/dev/VG0/SWAP PWD=/ SPLASHCFG= DO_QUIET=no PREVLEVEL=N LINES=24 HOME=/ SHLVL=2 DO_FORCEFSCK=no splash=silent SPLASH=no ROOTFS_BLKDEV=/dev/VG0/ROOT _=/sbin/startproc DAEMON=/usr/sbin/rpc.statd ] boot.msg: <notice -- Dec 16 17:22:22.157848000> service smartd done boot.msg: mountd statd nfsd sm-notifydone boot.msg: <notice -- Dec 16 17:22:22.474996000> service nfsserver doneStarting xend (already running pid 4041) done boot.msg: <notice -- Dec 16 17:22:27.398996000> startproc: execve (/usr/sbin/rpc.rquotad) [ /usr/sbin/rpc.rquotad ], [ DO_FASTBOOT=no CONSOLE=/dev/console SELINUX_INIT=YES ROOTFS_FSTYPE=ext4 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 DO_BLOGD=yes REDIRECT=/dev/xvc0 COLUMNS=80 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x31a DO_CONFIRM=no RUNLEVEL=3 resume=/dev/VG0/SWAP PWD=/ SPLASHCFG= DO_QUIET=no PREVLEVEL=N LINES=24 HOME=/ SHLVL=2 DO_FORCEFSCK=no splash=silent SPLASH=no ROOTFS_BLKDEV=/dev/VG0/ROOT _=/sbin/startproc DAEMON=/usr/sbin/rpc.rquotad ] As I said in my OP -- "Which isn't telling me anything that I understand" Do you see anything instructive?
To get it to work, I have to exec twice,
exportfs -r exportfs: Warning: /usr/local/exports does not support NFS export. exportfs -r
No. Just run "rcnfsserver start".
The issue is NOT that the server isn't running after boot, service nfsserver status Checking for kernel based NFS server: mountd running statd running nfsd running the issue is that the exports aren't exported. Running your suggestion results in similar error message,
rcnfsserver start exportfs: Warning: /usr/local/exports does not support NFS export. mountd statd nfsd sm-notify
done
rcnfsserver start mountd statd nfsd sm-notify
done at which point, as before, the exports are correctly exported. My original question remains ... BenDJ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ben DJ wrote:
exportfs: Warning: /usr/local/exports does not support NFS export.
Is /usr/local/exports also a mounted filesystem? What does 'exportfs' say after your 2nd attempt? /Per -- Per Jessen, Zürich (0.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, On Wed, Dec 16, 2009 at 10:08 AM, Per Jessen <per@opensuse.org> wrote:
exportfs: Warning: /usr/local/exports does not support NFS export.
Is /usr/local/exports also a mounted filesystem?
No, it's not. It's just a dir that I wish to export. Would it matter if it was?
What does 'exportfs' say after your 2nd attempt?
exportfs /usr/local/exports 192.168.1.7
, that's it. BenDJ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-12-16 at 10:18 -0800, Ben DJ wrote:
On Wed, Dec 16, 2009 at 10:08 AM, Per Jessen <> wrote:
exportfs: Warning: /usr/local/exports does not support NFS export.
Is /usr/local/exports also a mounted filesystem?
No, it's not. It's just a dir that I wish to export.
Post your /etc/exports file, please. And perhaps the mount options of whatever filesystem holds /usr/local/exports. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkspKAkACgkQtTMYHG2NR9XowwCcDhnaA7eI/WHW5sAau8+HO+is r0IAnA6rE8U2YhsrOLN1S6nY52UKXZwR =RWTS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Dec 16, 2009 at 10:33 AM, Carlos E. R. <robin.listas@telefonica.net> wrote:
Post your /etc/exports file, please.
As posted in the OP, cat /etc/exports /usr/local/exports 192.168.1.7(ro,no_root_squash,sync,subtree_check)
And perhaps the mount options of whatever filesystem holds /usr/local/exports.
cat /etc/fstab LABEL=BOOT /boot ext3 noatime,acl,user_xattr 1 2 LABEL=HOME /home ext4 relatime,acl,user_xattr,journal_checksum,barrier=1 1 2 LABEL=ROOT / ext4 relatime,acl,user_xattr,journal_checksum,barrier=1 1 1 LABEL=SWAP swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 BenDJ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ben DJ wrote:
Hi,
On Wed, Dec 16, 2009 at 10:08 AM, Per Jessen <per@opensuse.org> wrote:
exportfs: Warning: /usr/local/exports does not support NFS export.
Is /usr/local/exports also a mounted filesystem?
No, it's not. It's just a dir that I wish to export. Would it matter if it was?
We had a thread just recently where loop-mounted ISOs were being exported, and there was something that reminded me of that. Somting about reexport.
What does 'exportfs' say after your 2nd attempt?
exportfs /usr/local/exports 192.168.1.7
Looks good, so clearly your 2nd exportfs does work - something happens between the 1st and the 2nd. /Per -- Per Jessen, Zürich (0.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, On Wed, Dec 16, 2009 at 10:49 AM, Per Jessen <per@opensuse.org> wrote:
We had a thread just recently where loop-mounted ISOs were being exported, and there was something that reminded me of that. Somting about reexport.
Doesn't seem to be the case here, but probly a good read anyway. I'll dig for it. Thanks.
exportfs /usr/local/exports 192.168.1.7
Looks good, so clearly your 2nd exportfs does work - something happens between the 1st and the 2nd.
As well as something NOT happening at boot, it seems. BenDJ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ben DJ wrote:
Hi,
On Wed, Dec 16, 2009 at 10:49 AM, Per Jessen <per@opensuse.org> wrote:
We had a thread just recently where loop-mounted ISOs were being exported, and there was something that reminded me of that. Somting about reexport.
Doesn't seem to be the case here, but probly a good read anyway. I'll dig for it. Thanks.
exportfs /usr/local/exports 192.168.1.7
Looks good, so clearly your 2nd exportfs does work - something happens between the 1st and the 2nd.
As well as something NOT happening at boot, it seems.
I was deliberately ignoring that - there are usually all kinds of special or unique circumstances that apply during the boot-up sequence, so I prefer to leave that alone until the regular situation is okay. Which filesystem is /usr/local/exports ? I was googling a bit and came across someone mentioning that FUSE file-system are not exportable by NFS. /Per -- Per Jessen, Zürich (0.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
Which filesystem is /usr/local/exports ? I was googling a bit and came across someone mentioning that FUSE file-system are not exportable by NFS.
I saw in your other post that it's ext4 - I don't have any ext4 filesystems, but might there be a possibility that that is causing an issue? /Per -- Per Jessen, Zürich (0.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Dec 16, 2009 at 11:39 AM, Per Jessen <per@opensuse.org> wrote:
I saw in your other post that it's ext4
Yep, crossed in the mail :-)
- I don't have any ext4 filesystems, but might there be a possibility that that is causing an issue?
I'd be really surprised, but it's clear I don't currently have much of a clue about what IS causing the issue :-/ BenDJ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ben DJ wrote:
On Wed, Dec 16, 2009 at 11:39 AM, Per Jessen <per@opensuse.org> wrote:
I saw in your other post that it's ext4
Yep, crossed in the mail :-)
- I don't have any ext4 filesystems, but might there be a possibility that that is causing an issue?
I'd be really surprised, but it's clear I don't currently have much of a clue about what IS causing the issue :-/
I'd be quite surprised too, but ext4 _is_ brand new. Maybe you need a newer nfs server or something? I would try googling that some more - I'm rapidly running out of clues too ;-) /Per -- Per Jessen, Zürich (0.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Dec 16, 2009 at 12:03 PM, Per Jessen <per@opensuse.org> wrote:
I'd be quite surprised too, but ext4 _is_ brand new.
It's certainly old enough to be declared as stable by @kernel and ship as default FS in @opensuse 11.2 ... Your point's taken, though.
Maybe you need a newer nfs server or something?
I'm already using the newest provided @ http://download.opensuse.org/distribution/11.2/repo/oss/suse/, I.e., rpm -qa | grep -i nfs-kernel-server nfs-kernel-server-1.1.3-21.1.x86_64 The only newer option seems to be, http://download.opensuse.org/repositories/home:/neilbrown:/branches:/openSUS...
I would try googling that some more -
Really think I haven't been ? ;-D
I'm rapidly running out of clues too ;-)
Perhaps someone else will chime in as well. Thanks, BenDJ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 16/12/09 20:12, Ben DJ wrote:
On Wed, Dec 16, 2009 at 12:03 PM, Per Jessen <per@opensuse.org> wrote:
I'd be quite surprised too, but ext4 _is_ brand new.
It's certainly old enough to be declared as stable by @kernel and ship as default FS in @opensuse 11.2 ...
Your point's taken, though.
I am able to export ext4 filesystems using nfs-kernel-server - but using nfsv4. Haven't tried nfsv3, but I can't see why there would be a problem. my ext4 mount options are /mnt/backup ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered my /etc/exports /mnt/backup *(fsid=0,crossmnt,rw,root_squash,sync,no_subtree_check) I know that doesn't really help, but you might try using nfsv4 just to see ... Regards, Tejas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, On Wed, Dec 16, 2009 at 12:33 PM, Tejas Guruswamy <masterpatricko@gmail.com> wrote:
I know that doesn't really help, but you might try using nfsv4 just to see ...
I'm using NFSv3 because NFSv4 was/is problematic: http://linux-nfs.org/pipermail/nfsv4/2009-October/011479.html :-( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-12-16 at 12:45 -0800, Ben DJ wrote:
I'm using NFSv3 because NFSv4 was/is problematic: http://linux-nfs.org/pipermail/nfsv4/2009-October/011479.html
I export to a single machine and it works. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkssn2QACgkQtTMYHG2NR9Xl2gCeLsyrAbNYHgS9UFdrY7a7ag/m iT0An2isZc5T7qTxt20ioMCZPR6szo9p =2l4F -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ben DJ wrote:
On Wed, Dec 16, 2009 at 12:03 PM, Per Jessen <per@opensuse.org> wrote:
I'd be quite surprised too, but ext4 _is_ brand new.
It's certainly old enough to be declared as stable by @kernel and ship as default FS in @opensuse 11.2 ...
Your point's taken, though.
Purely my personal opinion, that's all.
I would try googling that some more -
Really think I haven't been ? ;-D
Apologies, I can tell you have.
I'm rapidly running out of clues too ;-)
Perhaps someone else will chime in as well.
I'm really tempted to have a look at the exportfs source code. I'd like to understand what that error message really means. I suspect it's a result of a lower level file-system operation. /Per -- Per Jessen, Zürich (0.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi,
Maybe you need a newer nfs server or something?
Fwiw, with upgrade to, 'newer(est?)', nfs-kernel-server-1.1.3-26.1.x86_64 same issue :-/
I'm really tempted to have a look at the exportfs source code. I'd like to understand what that error message really means. I suspect it's a result of a lower level file-system operation.
I did check my syslog @ & between the 2 execs of 'exportfs -r'. Simply nothing there :-/ BenDJ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, On Wed, Dec 16, 2009 at 11:34 AM, Per Jessen <per@opensuse.org> wrote:
As well as something NOT happening at boot, it seems.
I was deliberately ignoring that - there are usually all kinds of special or unique circumstances that apply during the boot-up sequence, so I prefer to leave that alone until the regular situation is okay.
Ok.
Which filesystem is /usr/local/exports ? I was googling a bit and came across someone mentioning that FUSE file-system are not exportable by NFS.
Acdording to what I've assigned in my /etc/fstab, it's "under" "/", which is just ext4, LABEL=ROOT / ext4 relatime,acl,user_xattr,journal_checksum,barrier=1 1 1 BenDJ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-12-16 at 11:41 -0800, Ben DJ wrote:
On Wed, Dec 16, 2009 at 11:34 AM, Per Jessen <> wrote:
Which filesystem is /usr/local/exports ? I was googling a bit and came across someone mentioning that FUSE file-system are not exportable by NFS.
Acdording to what I've assigned in my /etc/fstab, it's "under" "/", which is just ext4,
If you have diskspace, even small, try creating another type of filesystem there, and exporting just that. Or you could try nfs4 once, to see if that is the issue. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkspTpwACgkQtTMYHG2NR9WeOwCdFxLRivEmqJWK6Yjblfr1XbsC 2vUAniGtJZlBoJsZslWGs7LVmhpQvGaQ =x3bN -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Dec 16, 2009 at 1:18 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
If you have diskspace, even small, try creating another type of filesystem there, and exporting just that.
lvcreate -n TEST -L 10M /dev/VG0 mkfs.ext2 /dev/VG0/TEST echo "/dev/VG0/TEST /usr/local/exports ext2 defaults 1 2" >> /etc/fstab cat /etc/exports /usr/local/exports 192.168.1.7(ro,no_root_squash,sync,subtree_check) shutdown -r now ... mount | grep TEST /dev/mapper/VG0 on /usr/local/exports type ext2 (rw) same problem as before, requiring 2x 'exportfs -r' ...
Or you could try nfs4 once, to see if that is the issue.
Unlike ext4 which is declared stable, I'm not certain that NFSv4 is @ http://nfs.sourceforge.net/ "A Linux implementation of NFS Version 4 is under development at the University of Michigan's Center for Information Technology Integration under the direction of Andy Adamson. This version is available now in the Linux 2.6 kernel. Although this is a reference implementation of an NFS Version 4 client and server, one of two such implementations required as part of the IETF's standards process, it is still missing some features. These features are currently under development and should appear soon. For more information, visit CITI U-M's NFSv4 project web site." Also, as mentioned above, I've had documented problems with it already. Not sure that I'd trust what I see from it anyway. BenDJ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Ben DJ -
Carlos E. R. -
Joseph Loo -
Per Jessen -
Tejas Guruswamy