Opened 5 years ago
Closed 19 hours ago
#15624 closed bug (not reproducible)
KDL from IMAP connection worker: unhandled page fault in kernel space
Reported by: | jmairboeck | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | File Systems/BFS | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
This is hrev53709 on x86_64
I just got a KDL from IMAP connection worker. I have configured my Gmail account in Mail, which is rather big (~100k mails in the "All Mail" folder). mail_deamon was currently syncing mails (which it doesn't really do reliably for me, but that's a different problem ...)
I got this once already before in the last few weeks but it is not easily reproducible, I think.
Attachments (1)
Change History (7)
by , 5 years ago
Attachment: | IMG_20200112_180645.jpg added |
---|
follow-up: 2 comment:1 by , 5 years ago
Does file system contains errors? File system can be checked by checkfs -c /boot
. Replace /boot
with your volume path is needed.
comment:2 by , 5 years ago
Replying to X512:
Does file system contains errors? File system can be checked by
checkfs -c /boot
. Replace/boot
with your volume path is needed.
This is the output:
(dir has no name) (inode = 1637898), could not be opened 756024 nodes checked, 0 blocks not allocated, 0 blocks already set, 23925 blocks could be freed files 718563 directories 36354 attributes 692 attr. dirs 370 indices 45 direct block runs 767060 (14.96 GiB) indirect block runs 8651 (in 210 array blocks, 3.82 GiB) double indirect block runs 6909 (in 12 array blocks, 26.99 MiB)
Except maybe for the first line, this doesn't look suspicious to me.
comment:3 by , 5 years ago
Actually:
23925 blocks could be freed
This is pretty suspicious, it means that there were blocks that were not really allocated for anything.
(dir has no name) (inode = 1637898), could not be opened
This may be why; there was a directory that was for some reason corrupt, and so it was probably removed and anything in it "freed".
We should try to avoid KDLs though.
comment:5 by , 19 hours ago
I don't think so. A few weeks ago, I ran checkfs on that disk and it was clean. I reinstalled the system since I reported this ticket though.
comment:6 by , 19 hours ago
Resolution: | → not reproducible |
---|---|
Status: | new → closed |
KDL screenshot