Date: Thu, 05 Nov 1998 00:42:45 +0800 From: Peter Wemm <peter@netplex.com.au> To: Brian Feldman <green@unixhelp.org> Cc: "George W. Dinolt" <george.w.dinolt@lmco.com>, current@FreeBSD.ORG Subject: Re: mount_msdos is dead :( Message-ID: <199811041642.AAA00847@spinner.netplex.com.au> In-Reply-To: Your message of "Wed, 04 Nov 1998 11:23:13 EST." <Pine.BSF.4.05.9811041122380.17234-100000@zone.syracuse.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Brian Feldman wrote:
> I completely rebuilt an ELF kernel and all modules yesterday. I verify
> that this problem did not exist on 3.0-RELEASE.
>
> Cheers,
> Brian Feldman
Hmm, it works for me..
# mount -tmsdos /dev/fd0 /mnt
# df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/da0s1a 31775 28613 620 98% /
/dev/da0s1e 297423 204048 69582 75% /usr
/dev/da0s1f 78975 5092 67565 7% /var
/dev/da0s1g 3521630 3067266 172634 95% /home
procfs 4 4 0 100% /proc
spinner:/usr/X11R6 1214255 899466 217649 81% /usr/X11R6
spinner:/home 1589119 1211184 250806 83% /spinner/home
spinner:/home2 1214255 899466 217649 81% /spinner/home2
haywire:/home 3098894 2563044 287939 90% /haywire/home
/dev/fd0 1423 102 1321 7% /mnt
#
I can't for the life of me imagine what might be causing this.. ENOTBLK
comes from the per-FS mount code and it's a result of discovering the
device vnode is not type VBLK. The mount_msdos code is essentially the
same as the ffs mount code.
I assume this is with a statically configured kernel.. ELF? aout? Can
you do a 'kldstat -v' and see what's loaded?
>
>
> On Tue, 3 Nov 1998, George W. Dinolt wrote:
>
> > I
> > Brian Feldman wrote:
> >
> > > I'm attaching a script that shows this.
> > >
> > > Brian Feldman
> > >
> > > Script started on Tue Nov 3 22:07:44 1998
> > > {"/home/green"}# mount_msdos /dev/fd0 /m^H ^Hfloppy^M^M
> > > mount_msdos: /dev/fd0: Block device required^M
> > > {"/home/green"}# ls -l /dev/fd0^M^M
> > > brw------- 1 root operator 2, 0 Nov 3 20:47 /dev/fd0^M
> > > {"/home/green"}# dd if=/dev/rfd0 of=flop^M^M
> > > 2880+0 records in^M
> > > 2880+0 records out^M
> > > 1474560 bytes transferred in 52.781845 secs (27937 bytes/sec)^M
> > > {"/home/green"}# vnconfig -c /dev/vn0 /home/green/flop^M^M
> > > {"/home/green"}# mount_msdos /dev/vn0 /floppy^M^M
> > > mount_msdos: /dev/vn0: Block device required^M
> > > {"/home/green"}# ls -l /dev/vn0^M^M
> > > brw-r----- 1 root operator 15, 0x00010002 Jul 24 08:52 /dev/vn0^M
> > > {"/home/green"}# ^D^M^M
> > >
> > > Script done on Tue Nov 3 22:11:16 1998
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-current" in the body of the message
> >
> > I ran into similar problems several days ago after some large changes to
> > the kernel were committed. I think that if you rebuild your lkm modules
> > so they match the kernel you are running things will work. At least they
> > did for me. I haven't tried an elf kernel for a while, but I suspect the
> > same would happen if the '.ko' modules were not in sync with the kernel.
> >
> > Regards,
> > George Dinolt
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811041642.AAA00847>