Your message dated Mon, 21 Dec 2015 18:18:13 +0100 with message-id <[email protected]> and subject line Re: Bug#808380: mount: unknown filesystem type 'vfat' has caused the Debian Bug report #808380, regarding mount: unknown filesystem type 'vfat' to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 808380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808380 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mount Version: 2.25.2-6 Severity: important Dear Maintainer, My system does not allow me to mount 'vfat' formatted devices any more: # LANG=C mount -t vfat /dev/sdc1 /media/rgncm ; echo $? mount: unknown filesystem type 'vfat' 32 # Earlier it has worked perfectly fine. The change in behaviour appears to be related to a batch of security updates I installed (yesterday?), but I don't remember 'mount' being on the list of updated packages. /Jacob -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fo_FO.ISO-8859-1, LC_CTYPE=fo_FO.ISO-8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages mount depends on: ii libc6 2.19-18+deb8u1 ii libmount1 2.25.2-6 ii libselinux1 2.3-2 ii libsmartcols1 2.25.2-6 mount recommends no packages. Versions of packages mount suggests: pn nfs-common <none> -- no debconf information
--- End Message ---
--- Begin Message ---On 2015-12-21 17:32 +0100, Jacob Sparre Andersen wrote: > On 21/12-2015 17:20, Phil Susi wrote: >> On 12/21/2015 10:58 AM, Sven Joachim wrote: >>> Yes, but after a kernel upgrade the new modules might not be compatible >>> with the running kernel, e.g. they might have picked up new symbols. >>> This seems to be the case here. >> Yes, but modutils loads the module from the version you are *running*, >> not the latest you have installed. It can't do that if the new kernel has the same ABI as the old one, since the new module has replaced the old on disk. > I can at least confirm that a reboot solved the problem. > > I feel a bit embarrassed about having spent your time on this problem. > I should remember to reboot whenever I install a new kernel image. > > Thanks for the help. You're welcome. I have taken the liberty to close this bug. Cheers, Sven
--- End Message ---
