ok, the error message issue is reported as bug 504224.
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
I was having a difficult time getting a root over nfs system to boot
after several attempts to distro upgrade to 9.10. Having it explicitly
stated that nfs core mounts are not broken, I gave it a few more tries,
but finally today got 9.10 booting by first doing a fresh install and
full update onto
Alvin,
Please file a separate bug report against mountall for this.
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
Maybe they don't, but there's definitely a difference. I quote a boot
with NFS mounted /home
mount.nfs4: DNS resolution failed for leto: Name or service not known
mountall: mount /home [901] terminated with status 32
mountall: Filesystem could not be mounted: /home
One or more of the mounts listed
The changes in karmic /don't/ break the ability to mount core
filesystems via nfs shares.
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
Steve Langasek wrote "It is a design decision that a missing /home
blocks the boot; this is unlikely to be changed."
So what about folks who boot root over nfs? If the changes in Karmic
break systems with core filesystems mounted via nfs shares, what is the
logic of the "design decision"?
--
NFS
Yes, this one is fixed. I think the bug you're looking for is Bug
#461133. It has similar symptoms. (crashing the boot process if you
mount /home over NFS.)
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notification because you are a member of Ubuntu
Bugs, which
You've followed up to a bug that has already been fixed. If you think
there's still a problem, you should file a new bug report.
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
We also have this problem, it is really annoying, as boot takes quite a
long time. Any fix for it coming soon?
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
John,
It is a design decision that a missing /home blocks the boot; this is
unlikely to be changed.
However, with the latest mountall, you can opt to mark your /home
filesystem with the 'nobootwait' option, indicating to mountall not to
wait for this before proceeding with the boot.
Problems wit
Quick update, I rebooted yesterday after doing a bunch of updates, into
linux kernel 2.6.32-rc3 (my own compiled version) and it hung on bootup
again, not being able to mount /home and /local via NFS. It sat there
for *hours* since I did the reboot remotely.
It would be really much nicer if moun
Hi Jonas,
No, your issue is probably not related to bug #447654. I believe your
problem is fixed with the latest upload of nfs-utils, which arranges for
statd to be started (if not already running) whenever we are asked to
mount an NFS filesystem.
nfs-utils (1:1.2.0-2ubuntu5) karmic; urgency=lo
I have a hunch that the resolution to bug #447654 will also resolve the
issue that I reported above as a "timing issue". Can't test until
Monday, though, so I'll get back with more info then.
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notification because you
There's still a problem somewhere... seems to be a timing issue.
Occasionally NFS mount still fails because rpc.statd is not running
yet happens about half the time. I'll attach a screenshot.
** Attachment added: "Screenshot of failure to mount due to rpc.statd not
running"
http://launch
Thanks for the fixes, reboots when /home or other filesystems are
mounted via NFS now works properly. I still see a bunch of errors on
startup, but they must be ignored or re-tried. Maybe I'll see how it
works when the network is unplugged on bootup, whether it hangs the
system still or not.
Tha
Yes, this upgrade issue has been reported as bug #441055, and a fix is
in progress (will be uploaded as version -2ubuntu2).
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
I'm seeing configuration errors after upgrading to this new version:
Setting up nfs-common (1:1.2.0-2ubuntu1) ...
* Stopping NFS common utilities
...done.
Removing any system startup links for /etc/init.d/nfs-common ...
/etc/rc0.d/K20nfs-common
/etc/rc1.d/K20nfs-common
/etc/rc2.d/S20
On Sat, Oct 03, 2009 at 02:09:38AM -, l8gravely wrote:
> I must be stupid, but I don't see the nfs-utils package anywhere. I did
> install nfs-kernel-server package, which is now at version: nfs-kernel-
> server/karmic uptodate 1:1.2.0-2
> But it didn't make any difference. NFS directories d
I must be stupid, but I don't see the nfs-utils package anywhere. I did
install nfs-kernel-server package, which is now at version: nfs-kernel-
server/karmic uptodate 1:1.2.0-2
But it didn't make any difference. NFS directories don't mount properly
on bootup still. And I've done a full update a
** Branch linked: lp:ubuntu/nfs-utils
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
** Branch linked: lp:ubuntu/portmap
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
This bug was fixed in the package nfs-utils - 1:1.2.0-2ubuntu1
---
nfs-utils (1:1.2.0-2ubuntu1) karmic; urgency=low
* Drop nfs-common init script in favor of new upstart jobs. LP: #431248.
* Build-depend on debhelper (>= 7.3.15ubuntu3) for correct upstart init
handling.
* D
This bug was fixed in the package portmap - 6.0-10ubuntu1
---
portmap (6.0-10ubuntu1) karmic; urgency=low
* Convert portmap to upstart. LP: #431248.
-- Steve LangasekTue, 29 Sep 2009
09:27:48 +
** Changed in: portmap (Ubuntu Karmic)
Status: Triaged => Fix Released
** Changed in: nfs-utils (Ubuntu Karmic)
Milestone: ubuntu-9.10-beta => ubuntu-9.10
** Changed in: portmap (Ubuntu Karmic)
Milestone: ubuntu-9.10-beta => ubuntu-9.10
** Changed in: portmap (Ubuntu Karmic)
Assignee: Scott James Remnant (scott) => Steve Langasek (vorlon)
--
NFS not m
Updated nfs-utils patch superseding the previous, now with bugs shaken
out so upstart is able to actually manage the jobs. :)
** Attachment added: "nfs-utils-431248.patch"
http://launchpadlibrarian.net/32763198/nfs-utils-431248.patch
** Attachment removed: "nfs-utils-431248.patch"
http://la
And here is a patch for the nfs-common side of things. This is
dependent on debhelper and upstart changes so that we get sensible
restart-after-upgrade behavior for these services.
The problem of when to stop the service is also not completely solved
here and needs more attention.
** Attachment
Here's a preliminary patch to upstartify portmap.
The 'stopped nfs-common' is incorrect, both because there are multiple
daemons involved with nfs-common that will each need their own upstart
job (AFAICS), and because it should be stopped in cases where nfs-common
is not available.
Also, this ups
Ooops, I'm a moron. When I have /local enabled in my /etc/fstab, it
does NOT mount properly, but the mount process doesn't hang either.
It's complains about rpc.statd not being started properly, but I need to
enable bootlogd and do some testing to get better logs of the boot
process and what happ
I've run into this issue too, but I mount two paths from my home NFS
server, which is a Debian Testing box. I mount /home and /local. If I
comment out /home from my /etc/fstab, but leave in /local, the system
will boot.
But if I put in just /home, or both /home and /local, then it won't boot
pro
Note that mountall is just here for tracking, the fix is needed for the
nfs and portmap packages
** Changed in: mountall (Ubuntu Karmic)
Milestone: ubuntu-9.10-beta => None
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notification because you are a member o
same problem after migration in a "standard" computer
it seems to be a bad order in the boot sequence
nfs is not mounted at boot time
I have to launch /etc/init.d/nfs-common restart
and
mount manually
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notificatio
** Also affects: nfs-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nfs-utils (Ubuntu Karmic)
Importance: Undecided => High
** Changed in: nfs-utils (Ubuntu Karmic)
Status: New => Triaged
** Changed in: nfs-utils (Ubuntu Karmic)
Milestone: None => ubuntu-
** Changed in: mountall (Ubuntu Karmic)
Milestone: None => ubuntu-9.10-beta
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
** Also affects: mountall (Ubuntu Karmic)
Importance: High
Status: Triaged
** Changed in: mountall (Ubuntu Karmic)
Assignee: (unassigned) => Scott James Remnant (scott)
** Tags added: ubuntu-boot
--
NFS not mounted
https://bugs.launchpad.net/bugs/431248
You received this bug noti
Well, I don't really need this network drive at boot time. After all,
it's the home directory.
I didn't change anything in the boot process. I largly lack the skill to
do so. It's just a plain Karmic install and update.
My system might be a bit unusual though. I boot it from an SSD, which
gives m
Same problem with NFS mountpoints from fstab here.
Upon booting the message "couldn't resolve " appears.
After that, nfs-common, and thus rpc.statd, is started, so it looks like
mountall is
a) running too early in the boot process
or
b) requires a 2nd run when requirements are fulfilled
--
NFS
The problem isn't so much that mountall doesn't mount them, but it seems
to be related to portmap and nfs-common services. Since your NFS mount
is one that mountall considers required for boot, it will wait for it
before allowing the boot to proceed.
** Summary changed:
- nfs not resolved in fst
37 matches
Mail list logo
