sunnuntai 3. tammikuuta 2016 1.40.44 UTC+8 Nikolaus Rath kirjoitti: > > > 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. > yes i mean process accessing mountpoint.
> > Is there still a mount.s3ql process? > yes, need kill them to get fsck/mount again. > > What are the contents of mount.log? > nothing actually... :D > > Can you get a Python stacktrace? > (https://bitbucket.org/nikratio/s3ql/wiki/Providing%20Debugging%20Info) > > If not, can you get a C stacktrace? > when next time comes, i can wait few days. if i umount now or tomorrow it will work normally, it only happen when long time mounted. the filesystem works no problem there was no reason for umounting, but i just did it. i have 6 mountpoints its global problem, so when im unable to umount one i will turn on python stacktrace and then try umount next. > > > 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.
