Re: how to debug this fuse problem

[Warrick Baijius]

I've been having the same/similar issue, but with Jungle Disk software 
attempting to mount a network folder (webdav). This started some time (right 
after? didn't notice. Jungle Disk log is daily, does not extend back) after a 
kernel upgrade (dist-upgrade on April 9 included:

Upgrade: mailman:amd64 (2.1.18-1~bpo70+1, 2.1.18-2~bpo70+1), 
linux-image-3.16.0-0.bpo.4-amd64:amd64 (3.16.7-ckt4-3~bpo70+1, 
3.16.7-ckt7-1~bpo70+1), linux-libc-dev:amd64 (3.16.7-ckt4-3~bpo70+1, 
3.16.7-ckt7-1~bpo70+1))


"Warning Details (Jungle Disk Desktop 3.16 Linux Console x64)

Failed to mount volume
Exception Code: xDriveMapFailed (53)
Time: 17/04/15 09:34:28 AM (GMT-6)
Detailed Message: fuse_mount(/home//jd_wb) failed: fuse: device not found, 
try 'modprobe fuse' first"

root@wb-host:~# modprobe fuse
ERROR: could not insert 'fuse': Unknown symbol in module, or unknown parameter 
(see dmesg)

root@wb-host:~# dmesg

[  595.346552] fuse: Unknown symbol pagecache_get_page_fixed (err 0)

root@wb-host:~# insmod /lib/modules/3.16.0-0.bpo.4-amd64/kernel/fs/fuse/fuse.ko
Error: could not insert module 
/lib/modules/3.16.0-0.bpo.4-amd64/kernel/fs/fuse/fuse.ko: Unknown symbol in 
module

root@wb-host:~# ls -l /lib/modules/3.16.0-0.bpo.4-amd64/kernel/fs/fuse/
total 184
-rw-r--r-- 1 root root  17752 Apr  8 11:23 cuse.ko
-rw-r--r-- 1 root root 164272 Apr  8 11:23 fuse.ko


root@wb-host:~# uname -r
3.16.0-0.bpo.4-amd64

root@wb-host:~# dpkg-query -W 'linux-image-3.16.0-0.bpo.4-amd64'
linux-image-3.16.0-0.bpo.4-amd643.16.7-ckt7-1~bpo70+1

root@wb-host:~# dpkg -l | grep fuse
ii  fuse 2.9.0-2+deb7u1 amd64 Filesystem in Userspace
ii  libfuse-dev 2.9.0-2+deb7u1 amd64 Filesystem in Userspace 
(development)
ii  libfuse2:amd64 2.9.0-2+deb7u1 amd64 Filesystem in Userspace 
(library)

Tried depmod -a
and checked debsums to no avail.

Reinstalled kernel through apt-get, rebooted, no progress.
dpkg-reconfigure fuse - no change
Removed (purge), reinstalled fuse, reboot, no change.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150417100645.1628f7df3242db56c9db2...@gmail.com

Re: how to debug this fuse problem

[Harry Putnam]

Guanqing.lu  writes:

> Hi
>
>   I met the same error message today and got it fixed in following way:
>
> root@myhost01 grub]# dmesg |grep fuse
> [5174104.384024] fuse: disagrees about version of symbol iov_iter_get_pages
> [5174104.384027] fuse: Unknown symbol iov_iter_get_pages (err -22)
> [5174118.853162] fuse: disagrees about version of symbol iov_iter_get_pages
> [5174118.853166] fuse: Unknown symbol iov_iter_get_pages (err -22)
> ...
>
> [root@myhost01 grub]# modprobe fuse
> ERROR: could not insert 'fuse': Invalid argument
>
> [root@myhost01 grub]# uname -r
> 3.16.0-0.bpo.4-amd64
>
> [root@myhost01 grub]# dpkg-query -W 'linux-image-3.16.0-0.bpo.4-amd64'
> linux-image-3.16.0-0.bpo.4-amd643.16.7-ckt4-3~bpo70+1

No such output here:
uname -r
  3.16.0-4-586

[...]

> [root@myhost01 ~]# dpkg -l |grep fuse
> ii  libfuse2:amd64 2.9.0-2+deb7u1amd64
> Filesystem in Userspace (library)

aptitude search ^fuse$
   i A fuse
  So it is installed here

   As well as:
   i A libfuse2

[...]

Not sure what else to do here


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87twwsiwww@reader.local.lan

Re: Re: how to debug this fuse problem

[Guanqing . lu]

Hi

  I met the same error message today and got it fixed in following way:

root@myhost01 grub]# dmesg |grep fuse
[5174104.384024] fuse: disagrees about version of symbol iov_iter_get_pages
[5174104.384027] fuse: Unknown symbol iov_iter_get_pages (err -22)
[5174118.853162] fuse: disagrees about version of symbol iov_iter_get_pages
[5174118.853166] fuse: Unknown symbol iov_iter_get_pages (err -22)
...

[root@myhost01 grub]# modprobe fuse
ERROR: could not insert 'fuse': Invalid argument

[root@myhost01 grub]# uname -r
3.16.0-0.bpo.4-amd64

[root@myhost01 grub]# dpkg-query -W 'linux-image-3.16.0-0.bpo.4-amd64'
linux-image-3.16.0-0.bpo.4-amd643.16.7-ckt4-3~bpo70+1

The following command shows that we should not concern about what is 
ckt4, which can be considered a group of package

[root@myhost01 grub]# dpkg -l |grep 3.16.7-ckt4-3
ii  linux-compiler-gcc-4.6-x86 3.16.7-ckt4-3~bpo70+1 
amd64Compiler for Linux on x86 (meta-package)
ii  linux-headers-3.16.0-0.bpo.4-amd64 3.16.7-ckt4-3~bpo70+1 
amd64Header files for Linux 3.16.0-0.bpo.4-amd64
ii  linux-headers-3.16.0-0.bpo.4-common 3.16.7-ckt4-3~bpo70+1 
amd64Common header files for Linux 3.16.0-0.bpo.4
ii  linux-image-3.16.0-0.bpo.4-amd64 3.16.7-ckt4-3~bpo70+1 
amd64Linux 3.16 for 64-bit Pcs



[root@myhost01 grub]# strace modprobe fuse
execve("/sbin/modprobe", ["modprobe", "fuse"], [/* 18 vars */]) = 0
brk(0)  = 0x7fb341646000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7fb340dcb000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)

open("/etc/ld.so.cache", O_RDONLY)  = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=37031, ...}) = 0
mmap(NULL, 37031, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb340dc1000
close(3)= 0
...
open("/sys/module/fuse/initstate", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No 
such file or directory)
stat("/sys/module/fuse", 0x7fffd899d190) = -1 ENOENT (No such file or 
directory)
open("/sys/module/fuse/initstate", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No 
such file or directory)
stat("/sys/module/fuse", 0x7fffd899d190) = -1 ENOENT (No such file or 
directory)
open("/lib/modules/3.16.0-0.bpo.4-amd64/kernel/fs/fuse/fuse.ko", 
O_RDONLY|O_CLOEXEC) = 3

fstat(3, {st_mode=S_IFREG|0644, st_size=164264, ...}) = 0
mmap(NULL, 164264, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb3405e4000
init_module(0x7fb3405e4000, 164264, "") = -1 EINVAL (Invalid argument)
munmap(0x7fb3405e4000, 164264)  = 0
close(3)= 0
write(2, "ERROR: could not insert 'fuse': "..., 49ERROR: could not 
insert 'fuse': Invalid argument

) = 49
munmap(0x7fb340d42000, 505175)  = 0
munmap(0x7fb340c6f000, 863489)  = 0
munmap(0x7fb340bee000, 524731)  = 0
munmap(0x7fb340dc9000, 4256)= 0
exit_group(1)   = ?

[root@myhost01 ~]# dpkg -l |grep fuse
ii  libfuse2:amd64 2.9.0-2+deb7u1amd64Filesystem 
in Userspace (library)


Above two commands show the package fuse is not installed, only libfuse2 
package is installed. This is the problem!


[root@myhost01 module]# aptitude install  fuse

[root@myhost01 module]# dpkg -l |grep fuse
ii  fuse 2.9.0-2+deb7u1amd64Filesystem in Userspace
ii  libfuse2:amd64 2.9.0-2+deb7u1amd64Filesystem 
in Userspace (library)


You must reboot the server to make it work

[root@myhost01 module]# shutdown -r now

[root@myhost01 ~]# modprobe fuse
[root@myhost01 ~]# echo $?
0

[root@myhost01 ~]# lsmod |grep fuse
fuse   87557  1


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/551af99a.60...@gameloft.com

Re: how to debug this fuse problem

[Harry Putnam]

Eduard Bloch  writes:

>> searching with `aptitudue search ckt7' (or ckt4)  finds nothing at all.
>
> It's just an arbitrary version string. It can be (almost) anything, even
> 1.2.3.myCuteVersion-10.9.8.
>
>> I suspect I could/should be running i686 with pae.  Not sure why the
>> installer choose a 486 kernel originally ... (it changed to 586 during a
>> full-upgrade a mnth or two ago)
>> 
>> The jessie OS here is running as vbox guest on a 2x Xeon on HP xw8600
>
> I don't know why the installer chose that kernel, your Xeon should be
> fully i686 compatible. If the installation is damaged somehow (see
> above) then switching to another kernel might make the problem
> disappear.

Many thanks to all posters... this is quite a useful thread to me.
Still haven't got to fixing the problem but with the information here
I am now well armed.

Thanks posters


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87sicx3or2@reader.local.lan

Re: how to debug this fuse problem

[Lisi Reisz]

On Thursday 19 March 2015 16:08:25 Gene Heskett wrote:
> On Thursday 19 March 2015 08:17:23 Lisi Reisz wrote:
> > On Wednesday 18 March 2015 23:41:21 Harry Putnam wrote:
> > > Eduard Bloch  writes:
> > > > It's just the kernel from Jessie. See
> > > > https://packages.debian.org/jessie/linux-image-3.16.0-4-586
> > >
> > > Sorry to be so dense here but:
> > >
> > > Apparently it is a little more going on in those lines above.  I
> > > don't see anything on the page you cite with names like:
> > > 3.16.7-ckt4-3 3.16.7-ckt7-1
> > >
> > > searching with `aptitudue search ckt7' (or ckt4)  finds nothing at
> > > all.
> > >
> > > What is the meaning of the names with ckt in them?

> The ckt patches are from Con Kovilas,

Con Kovilas appears to be ck.  

Here is an explanatuion of ckt (sorry, Harry - I could have googled 
differently and found it sooner!)  ckt is Canonical Kernel Team
http://askubuntu.com/questions/555042/what-is-a-ckt-mainline-kernel
No doubt contributed back to upstream.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201503191645.58208.lisi.re...@gmail.com

Re: how to debug this fuse problem

[Gene Heskett]

On Thursday 19 March 2015 12:34:16 Sven Hartge wrote:
> Gene Heskett  wrote:
> > The ckt patches are from Con Kovilas,
>
> Wrong.
>
> The -ck patches were from him. But they have nothing to do with the
> kernel used in Debian Jessie.
>
> CKT in this case here stands for "Canonical Kernel Team" who maintain
> the long-term stable branche 3.16 for use in Ubuntu and Debian.

Ahh, enlightenment. I was wondering where the t came from.  My mistake.

Thank you Sven.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201503191241.54681.ghesk...@wdtv.com

Re: how to debug this fuse problem

[Gene Heskett]

On Thursday 19 March 2015 12:29:12 Eduard Bloch wrote:
> Hallo,
>
> * Gene Heskett [Thu, Mar 19 2015, 12:08:25PM]:
> > Mode rant (with some profanity):
>
> TLDR. Is this about fuse?
>
> Eduard.

Yeah, mine. :(

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201503191239.13412.ghesk...@wdtv.com

Re: how to debug this fuse problem

[Sven Hartge]

Gene Heskett  wrote:

> The ckt patches are from Con Kovilas, 

Wrong.

The -ck patches were from him. But they have nothing to do with the
kernel used in Debian Jessie.

CKT in this case here stands for "Canonical Kernel Team" who maintain
the long-term stable branche 3.16 for use in Ubuntu and Debian.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/fbfhil6ro...@mids.svenhartge.de

Re: how to debug this fuse problem

[Eduard Bloch]

Hallo,
* Gene Heskett [Thu, Mar 19 2015, 12:08:25PM]:

> Mode rant (with some profanity):

TLDR. Is this about fuse?

Eduard.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150319162912.ga13...@rotes76.wohnheim.uni-kl.de

Re: how to debug this fuse problem

[Gene Heskett]

On Thursday 19 March 2015 08:17:23 Lisi Reisz wrote:
> On Wednesday 18 March 2015 23:41:21 Harry Putnam wrote:
> > Eduard Bloch  writes:
> > > It's just the kernel from Jessie. See
> > > https://packages.debian.org/jessie/linux-image-3.16.0-4-586
> >
> > Sorry to be so dense here but:
> >
> > Apparently it is a little more going on in those lines above.  I
> > don't see anything on the page you cite with names like:
> > 3.16.7-ckt4-3 3.16.7-ckt7-1
> >
> > searching with `aptitudue search ckt7' (or ckt4)  finds nothing at
> > all.
> >
> > What is the meaning of the names with ckt in them?
>
> I did a Google search on "3.16.7-ckt4-3 debian" (without the quotation
> marks). I got this:
>
> https://packages.debian.org/sid/linux-headers-3.16.0-4-all
>
> Is that any help?
>
> Lisi

The ckt patches are from Con Kovilas, who was at one time a heavy 
contributor to the kernel, with a much improved scheduler for desktops 
being his specialty. But something he did caused a particularly nasty 
regression about 2-3 years ago, & Linus blew up (as only Linus can do) 
and banned him from direct contributions, so he has been publishing his 
patchset on lkml, but you will have to get the patch from his site.  I 
expire lkml fairly aggressively here, so my history of that list doesn't 
go back more than about 12,000 messages & I don't have that announcement 
post now.

A google search, or a direct search on gmane might turn up his last 
announce post which should get the OP a link to get that patch.

My own experience with his patches goes back quite a ways, and I have run 
this machine or its predecessor on Con's kernels for a couple years, 
they generally just worked, but were much snappier at desktop response 
than the linus kernels of the day.

Mode rant (with some profanity):

The only reason I haven't tried a new kernel lately, is that to use it I 
would also have to figure out how much of X I would have to pull and 
build at the same time, primarily because I run nvidia cards, and the 
current nouveau driver in the more recent kernels is totally 
incompatible with the nouveau pieces in my X install.  I have in my 
grub, several 3.16.x kernels, none of which can play a video because of 
the capability miss-match between the ancient X driver and the kernel 
driver.  The currently running 3.4-9amd64 works fairly well in that 
regard.

Sadly, much of the debian X is 5+ years old.  And the glxinfo output is, 
shall we say, discouraging at best.  Pull glxgears out to about 80% of 
the screen & its 170 fps.  So it plays a 40% of the screen video by 
using a hell of a lot of a quad core phenom. I could try to put the 
nvidia kit in, but support for my 3 year old GeForce 8400 GS  has 
already been dropped.  And the older version that I can get does not 
work with a kernel as new as the 3.4-9amd64 thats running now

And the only way to recover from an attempt to install the nvidia drivers 
that fails , is a bare metal full system reinstall.  Been there, done 
that, about 5 or 6 times.  nvidia designs good cards. But their 
installer, designed by their lawyers, sucks 10 day old dead toads thru 
soda straws, up with which I am no longer willing to put.  So I run 
whatever works now.

The competition, ATI, that AMD bought 3 or so years ago, is very 
carefully no better as they don't release linux drivers for their stuff 
until the card is out of production and supply shelves are empty, so its 
not possible to match up an ATI card that exists with the linux drivers 
to run it that exist at the same time.  I have had Alex D., now usually 
posting from X.org but paid by ATI/AMD, tell me personally via email 
that I'd have a driver shortly for the card I had that was being run by 
the vesa driver, or that there was support for card so-and-so, only to 
find the card was now pure unobtainium, or that when they threw the code 
over the fence, support for the card I had had been dropped as obsolete.  

Over the now 17 years I have been running linux I bought that song and 
dance, probably 700 dollars worth, and have yet to have a card that was 
usable except with the vesa driver. And their driver installer is worse 
than nvidias at destroying the system than the nvidia driver is. Once I 
went out & got the exact card he quoted, only to find that without even 
changing the color of a single dot above the i anyplace on the box, the 
card in the box was a slightly newer production with a different gpu on 
it that was unsupported. Needless to say that WAS the last straw, and 
there will never be another ATI card in any of my boxes. To be blunt, 
Alex D. is a liar, repeatedly.

I like to support the little guy, just so we would continue to have a 
choice in video cards, but the "little guy" can damned well support the 
user that bought the product, or he falls off the list of vendors to 
purchase from.  ATI was erased from that list, based on past 
performance, about 4 years ago, shortly after I built this machine, 
originally putting one of

Re: how to debug this fuse problem

[Eduard Bloch]

Hallo,
* Harry Putnam [Wed, Mar 18 2015, 07:41:21PM]:

> > Something is wrong with your modules installation. Run "dmesg" to see
> > what happened there.
> > Run "depmod -a" once, it might help if some stupid tool damaged the
> > module database (I had that "fun" with old dkms before).
> > Check the installed files (debsums linux-image-3.16.0-4-586)
> > Reinstall if needed (apt-get --reinstall install linux-image-3.16.0-4-586)
> 
> dmesg shows what looks like quite a mess.  I' don't know what it might
> mean, perhaps someone here has seen it before or understands what it
> means?
> 
> ,
> | dmesg|grep fuse
> | 
> | [7.166080] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
> | [7.166143] fuse: disagrees about version of symbol iov_iter_get_pages
> | [7.166188] fuse: Unknown symbol iov_iter_get_pages (err -22)

Please proceed as I suggested before (debsums, depmod, etc.). If the
package state is OK then feel free to open a bug report (with
reportbug utility).

> Apparently it is a little more going on in those lines above.  I don't
> see anything on the page you cite with names like: 3.16.7-ckt4-3
> 3.16.7-ckt7-1
> 
> searching with `aptitudue search ckt7' (or ckt4)  finds nothing at all.

It's just an arbitrary version string. It can be (almost) anything, even
1.2.3.myCuteVersion-10.9.8.

> I suspect I could/should be running i686 with pae.  Not sure why the
> installer choose a 486 kernel originally ... (it changed to 586 during a
> full-upgrade a mnth or two ago)
> 
> The jessie OS here is running as vbox guest on a 2x Xeon on HP xw8600

I don't know why the installer chose that kernel, your Xeon should be
fully i686 compatible. If the installation is damaged somehow (see
above) then switching to another kernel might make the problem
disappear.

Regards,
Eduard.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150319160603.ga12...@rotes76.wohnheim.uni-kl.de

Re: how to debug this fuse problem

[Lisi Reisz]

On Wednesday 18 March 2015 23:41:21 Harry Putnam wrote:
> Eduard Bloch  writes:
> > It's just the kernel from Jessie. See
> > https://packages.debian.org/jessie/linux-image-3.16.0-4-586
>
> Sorry to be so dense here but:
>
> Apparently it is a little more going on in those lines above.  I don't
> see anything on the page you cite with names like: 3.16.7-ckt4-3
> 3.16.7-ckt7-1
>
> searching with `aptitudue search ckt7' (or ckt4)  finds nothing at all.
>
> What is the meaning of the names with ckt in them?

I did a Google search on "3.16.7-ckt4-3 debian" (without the quotation marks).  
I got this:

https://packages.debian.org/sid/linux-headers-3.16.0-4-all

Is that any help?

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201503191217.24001.lisi.re...@gmail.com

Re: how to debug this fuse problem

[David Wright]

Quoting Harry Putnam (rea...@newsguy.com):

> Sorry to be so dense here but:
> 
> Apparently it is a little more going on in those lines above.  I don't
> see anything on the page you cite with names like: 3.16.7-ckt4-3
> 3.16.7-ckt7-1
> 
> searching with `aptitudue search ckt7' (or ckt4)  finds nothing at all.
> 
> What is the meaning of the names with ckt in them?

The kernel version is linux-image-3.16.0-4-686-pae and 3.16.7-ckt7-1
is the Debian package version tacked on the end, so on my i386
the deb is called linux-image-3.16.0-4-686-pae_3.16.7-ckt7-1_i386.deb

https://lists.debian.org/debian-kernel/2014/11/msg00154.html
explains why 3.16-kernel packages have ckt in the package version name.

> I suspect I could/should be running i686 with pae.  Not sure why the
> installer choose a 486 kernel originally ... (it changed to 586 during a
> full-upgrade a mnth or two ago)

The "486" version was probably a 586 version, which is for PCs lacking
PAE. Apparently the fact that the "486" version wouldn't actually run
on a real 486 was not noticed for somewhile after the relevant
improvement was made.

cat /proc/cpuinfo | grep pae
should indicate if 686-pae versions would be suitable.

Sorry not to be any help with the fuse problem.

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150319050844.ga19...@alum.home

Re: how to debug this fuse problem

[Harry Putnam]

Eduard Bloch  writes:

[...]

>> Attempting to modprobe fuse gets this error:
>> 
>> ,
>> | root # modprobe fuse
>> | modprobe: ERROR: could not insert 'fuse': Invalid argument
>
> Something is wrong with your modules installation. Run "dmesg" to see
> what happened there.
> Run "depmod -a" once, it might help if some stupid tool damaged the
> module database (I had that "fun" with old dkms before).
> Check the installed files (debsums linux-image-3.16.0-4-586)
> Reinstall if needed (apt-get --reinstall install linux-image-3.16.0-4-586)

dmesg shows what looks like quite a mess.  I' don't know what it might
mean, perhaps someone here has seen it before or understands what it
means?

,
| dmesg|grep fuse
| 
| [7.166080] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
| [7.166143] fuse: disagrees about version of symbol iov_iter_get_pages
| [7.166188] fuse: Unknown symbol iov_iter_get_pages (err -22)
| [  313.475402] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
| [  313.475416] fuse: disagrees about version of symbol iov_iter_get_pages
| [  313.475418] fuse: Unknown symbol iov_iter_get_pages (err -22)
| [38952.902191] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
| [38952.902224] fuse: disagrees about version of symbol iov_iter_get_pages
| [38952.902239] fuse: Unknown symbol iov_iter_get_pages (err -22)
| [38965.865410] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
| [38965.865413] fuse: disagrees about version of symbol iov_iter_get_pages
| [38965.865584] fuse: Unknown symbol iov_iter_get_pages (err -22)
| [38989.899913] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
| [38989.904530] fuse: disagrees about version of symbol iov_iter_get_pages
| [38989.904530] fuse: Unknown symbol iov_iter_get_pages (err -22)
| [39204.559898] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
| [39204.559947] fuse: disagrees about version of symbol iov_iter_get_pages
| [39204.559970] fuse: Unknown symbol iov_iter_get_pages (err -22)
| [39718.223622] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
| [39718.223683] fuse: disagrees about version of symbol iov_iter_get_pages
| [39718.223726] fuse: Unknown symbol iov_iter_get_pages (err -22)
| [40037.891183] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
| [40037.891353] fuse: disagrees about version of symbol iov_iter_get_pages
| [40037.891495] fuse: Unknown symbol iov_iter_get_pages (err -22)
| [40056.750094] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
| [40056.750148] fuse: disagrees about version of symbol iov_iter_get_pages
| [40056.750186] fuse: Unknown symbol iov_iter_get_pages (err -22)
| [40209.000103] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
| [40209.015074] fuse: disagrees about version of symbol iov_iter_get_pages
| [40209.015080] fuse: Unknown symbol iov_iter_get_pages (err -22)
| [40219.713514] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
| [40219.713570] fuse: disagrees about version of symbol iov_iter_get_pages
| [40219.713608] fuse: Unknown symbol iov_iter_get_pages (err -22)
| [40284.303346] fuse: Unknown symbol pagecache_get_page_fixed (err 0)
| [40284.303361] fuse: disagrees about version of symbol iov_iter_get_pages
| [40284.303363] fuse: Unknown symbol iov_iter_get_pages (err -22)
`


>> The upgrade log shows no upgrade for fuse at the last `full-upgrade'
>> but does show something happening with the kernel. However, I don't
>> understand what it means.
>> 
>> ,
>> | [UPGRADE] linux-compiler-gcc-4.8-x86:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
>> | [UPGRADE] linux-headers-3.16.0-4-586:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
>> | [UPGRADE] linux-headers-3.16.0-4-common:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
>> | [UPGRADE] linux-image-3.16.0-4-586:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
>> | [UPGRADE] linux-libc-dev:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
>
> It's just the kernel from Jessie. See
> https://packages.debian.org/jessie/linux-image-3.16.0-4-586

Sorry to be so dense here but:

Apparently it is a little more going on in those lines above.  I don't
see anything on the page you cite with names like: 3.16.7-ckt4-3
3.16.7-ckt7-1

searching with `aptitudue search ckt7' (or ckt4)  finds nothing at all.

What is the meaning of the names with ckt in them?

I suspect I could/should be running i686 with pae.  Not sure why the
installer choose a 486 kernel originally ... (it changed to 586 during a
full-upgrade a mnth or two ago)

The jessie OS here is running as vbox guest on a 2x Xeon on HP xw8600

Would it be likely to solve any of this if I upgraded to a 686 pae
kernel?   Or more likely to make the mess worse and I should get the
fuse mess cleared up first?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87wq2d3mce@reader.local.lan

Re: how to debug this fuse problem

[Eduard Bloch]

Hallo,
* Harry Putnam [Wed, Mar 18 2015, 07:48:54AM]:
> Running `jessie'
> 
> I've been using encfs, drawn from wheeze for months.  But following a
> `full upgrade' I can no longer mount an encfs file system.
> 
> The error message from mount attempt:
> 
> ,
> | fuse: device not found, try 'modprobe fuse' first
> | fuse failed.  Common problems:
> |  - fuse kernel module not installed (modprobe fuse)
> |  - invalid options -- see usage message
> `
> 
> Attempting to modprobe fuse gets this error:
> 
> ,
> | root # modprobe fuse
> | modprobe: ERROR: could not insert 'fuse': Invalid argument

Something is wrong with your modules installation. Run "dmesg" to see
what happened there.
Run "depmod -a" once, it might help if some stupid tool damaged the
module database (I had that "fun" with old dkms before).
Check the installed files (debsums linux-image-3.16.0-4-586)
Reinstall if needed (apt-get --reinstall install linux-image-3.16.0-4-586)

> The upgrade log shows no upgrade for fuse at the last `full-upgrade'
> but does show something happening with the kernel. However, I don't
> understand what it means.
> 
> ,
> | [UPGRADE] linux-compiler-gcc-4.8-x86:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
> | [UPGRADE] linux-headers-3.16.0-4-586:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
> | [UPGRADE] linux-headers-3.16.0-4-common:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
> | [UPGRADE] linux-image-3.16.0-4-586:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
> | [UPGRADE] linux-libc-dev:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1

It's just the kernel from Jessie. See
https://packages.debian.org/jessie/linux-image-3.16.0-4-586

Regards,
Eduard.

-- 
Every great idea is worthless without someone to do the work. --Neil Williams


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150318123238.ga9...@rotes76.wohnheim.uni-kl.de

how to debug this fuse problem

[Harry Putnam]

Running `jessie'

I've been using encfs, drawn from wheeze for months.  But following a
`full upgrade' I can no longer mount an encfs file system.

The error message from mount attempt:

,
| fuse: device not found, try 'modprobe fuse' first
| fuse failed.  Common problems:
|  - fuse kernel module not installed (modprobe fuse)
|  - invalid options -- see usage message
`

Attempting to modprobe fuse gets this error:

,
| root # modprobe fuse
| modprobe: ERROR: could not insert 'fuse': Invalid argument
`

I did try downgrading fuse and dependencies, but got the same errors

The upgrade log shows no upgrade for fuse at the last `full-upgrade'
but does show something happening with the kernel. However, I don't
understand what it means.

,
| [UPGRADE] linux-compiler-gcc-4.8-x86:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
| [UPGRADE] linux-headers-3.16.0-4-586:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
| [UPGRADE] linux-headers-3.16.0-4-common:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
| [UPGRADE] linux-image-3.16.0-4-586:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
| [UPGRADE] linux-libc-dev:i386 3.16.7-ckt4-3 -> 3.16.7-ckt7-1
`

Running `uname -r' still shows: 3.16.0-4-586, so I'm not sure what:
3.16.7-ckt4-3 -> 3.16.7-ckt7-1 means.

Anyone have an idea what's going on here... and what I might have to
do to mount my encfs filesystem?



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87619y4jbt@reader.local.lan