From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: "Jérôme Poulin" <jeromepoulin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-nilfs <linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Kernel Bug: unable to handle kernel paging request
Date: Sat, 27 Jul 2013 21:06:52 +0400 [thread overview]
Message-ID: <680DC2BF-EEEC-445C-BA5B-DF966CABF1BA@dubeyko.com> (raw)
In-Reply-To: <CALJXSJrY22eGkYA76wwL4moAdsjV+_PUtvVO6tt5K16hzMh8xQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Jul 26, 2013, at 10:13 PM, Jérôme Poulin wrote:
> Good afternoon,
>
> I have more informations to add to the bug.
>
Thank you for additional info.
[snip]
> I was able to reproduce consistently the problem.
> 1. Make a snapshot of a checkpoint and mount it.
> 2. Read from the checkpoint (make a backup).
> 3. Issue apt-get update.
>
I tried to reproduce the issue but I haven't success in it.
Could you describe the reproducing path in more details?
Moreover, could you share lscp utility output for your NILFS2 partition?
[snip]
>
> Here are the log files.
> 1. strace from the backup was still reading, it did not stop.
> 2. apt-get-crash.log
> 4362 13:32:04 read(6, " Debugging symbols\nHomepage: htt"..., 32052) = 32052
> 4362 13:32:04 read(6, "tcp-wrappers/libwrap0-dev_7.6.q-"..., 32460) = 32460
> 4362 13:32:04 read(6, "bdevel\nInstalled-Size: 542\nMaint"..., 32710) = 32710
> 4362 13:32:04 read(6, "ian.org>\nArchitecture: i386\nSour"..., 32558) = 32558
> 4362 13:32:04 read(6, "l-Maintainer: XCB Developers <xc"..., 32613) = 32613
> 4362 13:32:04 read(6, "ed: 9m\n\nPackage: libxcb-xvmc0-db"..., 31979) = 31979
> 4362 13:32:04 read(6, "ibz-dev\nFilename: pool/main/x/xf"..., 32335) = 32335
> 4362 13:32:04 read(6, "n: Ubuntu\nSupported: 9m\nTask: my"..., 31903) = 31903
> 4362 13:32:04 read(6, "\nFilename: pool/main/libx/libxpm"..., 32467) = 32467
> 4362 13:32:04 read(6, "buntu/+filebug\nOrigin: Ubuntu\nSu"..., 31982) = 31982
> 4362 13:32:04 read(6, "chpad.net/ubuntu/+filebug\nOrigin"..., 31976) = 31976
> 4362 13:32:04 read(6, "buntu Developers <ubuntu-devel-d"..., 32681) = 32681
> 4362 13:32:04 read(6, "-utils\nDepends: debconf (>= 0.5)"..., 32468) = 32468
> 4362 13:32:04 read(6, "top, mythbuntu-backend-slave, my"..., 31678) = 31678
> 4362 13:32:04 read(6, "d5: 1b0992eebd45ca5ceadc775532a4"..., 32126) = 32126
> 4362 13:32:04 read(6, " all\nSource: munin\nVersion: 2.0."..., 32535) = 32535
> 4362 13:32:04 read(6, "fice-core | openoffice.org-hunsp"..., 32373) = 32373
> 4362 13:32:04 read(6, "ffice.org-dictionaries (1:3.3.0~"..., 32513) = 32513
> 4362 13:32:04 read(6, "hbuntu-backend-master\n\nPackage: "..., 31756) = 31756
> 4362 13:32:04 read(6, "2614b9\nSHA256: bcc70d6577dd06565"..., 32118) = 32118
> 4362 13:32:04 read(6, "17\nSHA256: d903f798a8c38fef2b992"..., 32339) = 32339
> -- End of file --
>
Could you share the full strace output?
Because in shared part of strace output I can't see any issue or failure.
Moreover, the reported issue occurs in segstor thread. But, usually, segctor activity
takes place after writing or flushing operation. So, it means for me that a reason of the
issue is hidden in another part of the strace output or, maybe, in strace output for
backup operation. Could you share the strace output for backup operation too?
Thanks,
Vyacheslav Dubeyko.
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-07-27 17:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 5:24 Kernel Bug: unable to handle kernel paging request Jérôme Poulin
[not found] ` <CALJXSJquK6YxGKuH97Ec2CTMyJaZrJjOfePSKtgPDm8_9YXzzw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-12 18:58 ` Jérôme Poulin
[not found] ` <CALJXSJoW9Qpp9t42u_k4cW3gO6qzSPoeCjtQDU3tDKq6TJ=K8Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-18 17:30 ` Vyacheslav Dubeyko
[not found] ` <F4156394-8A25-4F81-81C3-9921CB00BD92-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-07-22 19:11 ` Jérôme Poulin
[not found] ` <CALJXSJrj0J_-ZUCOurJXaYhx_wEJwxb2_5OOJjQSSmmP-PQDgg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-23 11:15 ` Vyacheslav Dubeyko
2013-07-26 18:13 ` Jérôme Poulin
[not found] ` <CALJXSJrY22eGkYA76wwL4moAdsjV+_PUtvVO6tt5K16hzMh8xQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-27 17:06 ` Vyacheslav Dubeyko [this message]
[not found] ` <CALJXSJqV5nYb_t6GMS0FpWyf1aRehAgpvebwgbJzMJfctf1b2A@mail.gmail.com>
[not found] ` <CALJXSJqV5nYb_t6GMS0FpWyf1aRehAgpvebwgbJzMJfctf1b2A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-29 17:30 ` Vyacheslav Dubeyko
2013-08-09 13:15 ` Vyacheslav Dubeyko
2013-08-14 22:38 ` Ryusuke Konishi
[not found] ` <20130815.073806.260411879.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2013-08-16 4:49 ` Ryusuke Konishi
[not found] ` <20130816.134934.27810145.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2013-08-16 7:03 ` Vyacheslav Dubeyko
2013-08-29 19:10 ` Vyacheslav Dubeyko
[not found] ` <72C60256-983E-43D0-9DA1-D4A446B578BB-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-08-29 23:37 ` Jérôme Poulin
[not found] ` <CALJXSJpbHN2SQWz0e2gC_hrRKG8EcnV2bWf068GWsuoa8AX5Dw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-30 5:43 ` Vyacheslav Dubeyko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=680DC2BF-EEEC-445C-BA5B-DF966CABF1BA@dubeyko.com \
--to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
--cc=jeromepoulin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox