Summary: | 13.0-RELEASE-p2 ufs2+sujournal. Fatal trap 12: page fault while in kernel mode | ||
---|---|---|---|
Product: | Base System | Reporter: | Igor Valkov <viaprog> |
Component: | kern | Assignee: | freebsd-fs (Nobody) <fs> |
Status: | Open --- | ||
Severity: | Affects Some People | CC: | chris, crest, grahamperrin, kwiat3k, mckusick |
Priority: | --- | Keywords: | crash |
Version: | 13.0-RELEASE | ||
Hardware: | amd64 | ||
OS: | Any |
Description
Igor Valkov
2021-06-24 18:22:40 UTC
(In reply to Igor A. Valkov from comment #0) > … > #7 0xffffffff808b25ec at ufs_dirrewrite+0x14c > #8 0xffffffff808ba48b at ufs_rename+0x138b > … > Uptime: 6h57m43s > … Please, can you recall what was occurring around that time? (In reply to Graham Perrin from comment #1) After extracting many small files immediately moving one of them. Like this tar xfz many-small-and-medium-files.tar.gz && mv many-small-and-medium-files/one_file.txt . Partition size is 60TB, ufs+sujournal This report is a new panic that we have not seen before now. To be able to debug it, we will need some way to reproduce it. So, if you can come up with a script that triggers it, please let us know. It would also be helpful to know if journaling is what triggers the bug, so if you can reproduce it, try disabling journaling (tunefs -j disable /fs) to see if that solves the problem. That would help us narrow down the search space for the bug. Without softupdates journaling (tunefs -j disable) works fine for six months. The problem arises, as I understand it, when we try to move files that are not yet committed to disk and are being processed by soft-updates. It occurred to me when unpacking an archive with several tens of thousands of small files and immediately trying to move them somewhere. |