mountd suddenly stopped working
I have just rebooted an old system after 100 days of uptime and this came up: Jun 30 15:39:00 ghost mountd[1592]: can't change attributes for /tftpboot Jun 30 15:39:00 ghost mountd[1592]: bad exports list line /tftpboot -ro -mapall Both /etc/exports and /tftpboot are many years old and didn't cause any problems until today. I have tried fsck and rebooting but it didn't help. > uname -a FreeBSD ghost.pnet.one.pl 8.2-STABLE FreeBSD 8.2-STABLE #6: Sun Nov 13 05:32:38 CET 2011 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: mountd suddenly stopped working
On Sat, 30 Jun 2012 15:53:53 +0200, Marcin Wisnicki wrote: I have just rebooted an old system after 100 days of uptime and this came up: Jun 30 15:39:00 ghost mountd[1592]: can't change attributes for /tftpboot Jun 30 15:39:00 ghost mountd[1592]: bad exports list line /tftpboot -ro -mapall Both /etc/exports and /tftpboot are many years old and didn't cause any problems until today. Do you mean these were not edited/changed since the previous reboot? I have tried fsck and rebooting but it didn't help. uname -a FreeBSD ghost.pnet.one.pl 8.2-STABLE FreeBSD 8.2-STABLE #6: Sun Nov 13 05:32:38 CET 2011 Than probably somebody changed something else. Can you provide the content of your exports file? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: mountd suddenly stopped working
On Sat, 30 Jun 2012 16:21:18 +0200, Ronald Klop wrote: > On Sat, 30 Jun 2012 15:53:53 +0200, Marcin Wisnicki > wrote: > >> I have just rebooted an old system after 100 days of uptime and this >> came up: >> >> Jun 30 15:39:00 ghost mountd[1592]: can't change attributes for >> /tftpboot Jun 30 15:39:00 ghost mountd[1592]: bad exports list line >> /tftpboot -ro -mapall >> > > Than probably somebody changed something else. Can you provide the > content of your exports file? > OK, I've found the reason. There were two paths exported with same attributes: /tftpboot -ro -mapall=nobody /vol/tank1 -ro -mapall=nobody As long as there is a filesystem mounted on /vol/tank1, above exports will work. Since I've disconnected that drive, there was nothing mounted this time. Apparently mountd does not allow exporting multiple paths from a single filesystem on separate lines if they happen to have identical attributes. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: mountd suddenly stopped working
On Sat, Jun 30, 2012 at 09:07:17PM +, Marcin Wisnicki wrote: > On Sat, 30 Jun 2012 16:21:18 +0200, Ronald Klop wrote: > > > On Sat, 30 Jun 2012 15:53:53 +0200, Marcin Wisnicki > > wrote: > > > >> I have just rebooted an old system after 100 days of uptime and this > >> came up: > >> > >> Jun 30 15:39:00 ghost mountd[1592]: can't change attributes for > >> /tftpboot Jun 30 15:39:00 ghost mountd[1592]: bad exports list line > >> /tftpboot -ro -mapall > >> > > > > Than probably somebody changed something else. Can you provide the > > content of your exports file? > > > > OK, I've found the reason. > > There were two paths exported with same attributes: > > /tftpboot -ro -mapall=nobody > /vol/tank1 -ro -mapall=nobody > > As long as there is a filesystem mounted on /vol/tank1, above exports > will work. Since I've disconnected that drive, there was nothing mounted > this time. > > Apparently mountd does not allow exporting multiple paths from a single > filesystem on separate lines if they happen to have identical attributes. > Its been like that for a long time. I remember running into this way back on 6.X and 5.X. The solution is to: /tftpboot /vol/tank1 -ro -mapall=nobody -- - (2^(N-1)) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"