© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I’ve done another few tests, this time with « sshfs »’s debug enabled. This didn’t work for the similar bug I experienced last year.
I mounted the fs with:
bogdanb@mabelode:~$ sshfs -d tanelorn:/mnt/corum /media/corum 2>&1 | tee sshfs-log.txt
Then I did things on the FS until I encountered the bug. Note that, as I said, this happens randomly, and usually when there’s a lot of activity. This time it took even longer than usual, I suspect that debugging conflicts with whatever is causing the lock-up.
(In this case, I was tagging music files with Picard; Picard reads the files to generate an acoustic fingerprint, and later writes the file with modified tags somewhere else. At the same time I was looking at images on the same mount-point, to help trigger the bug.)
As a result, the log is 16 MB long uncompressed. I also made backtraces for the SSHFS and SSH processes while locked up. I did several to see if it was completely frozen or just very slow; one of them seems to have changed between runs.
I noticed at one point a “Corrupted MAC on input” message. I had noticed the same message before, in a test run without “-d”. The earlier test run locked up very fast after that message, but this one kept going for quite a while, so I think it may be just a coincidence.