On Jan 02 2016, Riku Bister <[email protected]> wrote: > Heya, Happy new year for everyone > > After keeping s3ql weeks or days mounted, it always fail to umount, only > way i have manageg to fix this is remount drives time to time, is there any > other tip what i can fix this? > Daemon seems to be alive, waiting... > 2016-01-02 17:08:55.234 25817 MainThread s3ql.umount.blocking_umount: PID > still alive and commandline unchanged. > 2016-01-02 17:08:55.235 25817 MainThread s3ql.umount.blocking_umount: > Daemon seems to be alive, waiting... > > It just loops, see time how log i waited. the filesystem was not on use, > check with lsof and every process has killed.
What do you mean with "every process"? Are you talking about processes accessing the mountpoint? If there were any, you wouldn't have been able to call umount.s3ql in the first place. Is there still a mount.s3ql process? What are the contents of mount.log? Can you get a Python stacktrace? (https://bitbucket.org/nikratio/s3ql/wiki/Providing%20Debugging%20Info) If not, can you get a C stacktrace? Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
