From owner-freebsd-questions Tue Jan 23 0:46: 6 2001 Delivered-To: freebsd-questions@freebsd.org Received: from stjohn.stjohn.ac.th (stjohn.stjohn.ac.th [202.21.144.1]) by hub.freebsd.org (Postfix) with ESMTP id 1E95B37B69B for ; Tue, 23 Jan 2001 00:45:37 -0800 (PST) Received: from granite ([203.151.134.100]) by stjohn.stjohn.ac.th (8.9.3+Sun/8.9.3) with SMTP id PAA06358 for ; Tue, 23 Jan 2001 15:43:52 +0700 (ICT) Message-Id: <3.0.6.32.20010123154534.007a8ba0@stjohn.stjohn.ac.th> X-Sender: mcrogerm@stjohn.stjohn.ac.th X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 23 Jan 2001 15:45:34 +0700 To: freebsd-questions@FreeBSD.ORG From: Roger Merritt Subject: Re: cd9660: device busy Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 22:31 22-01-01 -0500, you wrote: >This may seem silly (and I haven't seen the whole thread), but are you sure >that /dev/acd0c isn't mounted? If it is and the process that automounted it >has died (/stand/sysinstall is known to do this) then try a umount -f >/dev/acd0c, and then try mounting the CD again. > >-- >Matt Emmerton > > It's a good suggestion, but was one of the first things I tried. However, I have found another, apparently related, error that may help someone figure this out. I figured the most likely culprit was mountd, so I tried 'killall -HUP mountd', and found the following in /var/log/messages: Jan 23 15:37:07 ceres mountd[121]: could not remount /cdrom: Invalid argument Jan 23 15:37:07 ceres mountd[121]: bad exports list line /cdrom -alldirs -ro grendel poppy Now, the actual line in /etc/exports is: /cdrom -alldirs -ro grendel poppy The other exported filesystem has the line: /usr/home -alldirs grendel poppy and doesn't seem to generate an error message from mountd. I've checked the man page for exports over and over again and I'm damned if I can see what the invalid argument might be. A few months ago the mount command was also giving me an error message based on an invalid argument in /etc/exports, but it's not doing that any more, just the 'device busy', but I suspect this has something to do with it. The frustrating thing is it was working a couple of months ago, before we took our two-week Xmas break, and I was able to access the cdrom from the other server (indeed, all over the subnetwork which depends on the other server). -- Roger The way I drive I don't have to worry about cholesterol. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message