Hi Maxim,
When replying to emails on this list, please do not put your reply
above the quoted text, and do not quote the entire message you're
answering to. This makes it unnecessarily hard for other readers to
understand the context of your email. Instead, please cut quoted parts
that are not relevant to your reply, and insert your responses right
after the points you're replying to (as I have done below). Thanks!
Maxim Kostrikin <[email protected]> writes:
> вторник, 11 ноября 2014 г., 1:13:49 UTC+6 пользователь Nikolaus Rath
> написал:
>> Maxim Kostrikin <[email protected] <javascript:>> writes:
>> >> 2014-11-10 05:11:33.867 4539:MainThread s3ql.fsck.check: Creating
>> >> temporary extra indices...
>> >> 2014-11-10 05:11:35.765 4539:MainThread s3ql.fsck.check_lof: Checking
>> >> lost+found...
>> >> 2014-11-10 05:11:35.765 4539:MainThread s3ql.fsck.check_cache: Checking
>> >> cached objects...
>> >> 2014-11-10 05:11:39.559 4539:MainThread s3ql.fsck.check_names_refcount:
>> >> Checking names (refcounts)...
>> >
>> > Last line stick for hours with no progress.
>> > fsck.s3ql eat on core 100% constantly.
>> >
>> > Please advise.
>>
>> Is this a new problem with 2.12, i.e. was it working with 2.11?
>>
>> What is the output if you press Ctrl-C?
>>
> I hoped that 2.12 was the cause.
> 2.11.1 same result.
> Ctrl-C typing C^
> Kill PID - interrupts the fsck process.
You mean, you cannot abort the process with Ctrl-C?
In that case, please apply the attached patch and send SIGUSR1 when it's
hanging, this should give a proper stack trace.
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.
--- a/src/s3ql/fsck.py
+++ b/src/s3ql/fsck.py
@@ -30,6 +30,7 @@
import textwrap
import time
import atexit
+import faulthandler
log = logging.getLogger(__name__)
@@ -1139,6 +1140,9 @@
options = parse_args(args)
setup_logging(options)
+ faulthandler.enable()
+ faulthandler.register(signal.SIGUSR1)
+
# Check if fs is mounted on this computer
# This is not foolproof but should prevent common mistakes
if is_mounted(options.storage_url):