Linux NILFS development
 help / color / mirror / Atom feed
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: Tue, 23 Jul 2013 15:15:41 +0400	[thread overview]
Message-ID: <1374578141.2226.5.camel@slavad-ubuntu> (raw)
In-Reply-To: <CALJXSJrj0J_-ZUCOurJXaYhx_wEJwxb2_5OOJjQSSmmP-PQDgg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Mon, 2013-07-22 at 15:11 -0400, Jérôme Poulin wrote:

[snip]
> 
> I'm back using my laptop but wasn't able to reproduce it again, it is
> not as easy as it was before to reproduce, sometimes apt-get update
> works, sometimes it freezes. Here is a different paste bin as
> pastebin.ca seems to be down for some time now:
> http://pastebin.com/ALmuHdfh
> 

Thank you. Now I downloaded this output.

> > So, as I see, the reproducing path is: (1) delete /var/cache/apt; (2) issue apt-get update.
> 
> In fact it is the other way around;
> (1) Issue apt-get update: Crash.
> (2) Reboot, try again: Crash.
> (3) Delete /var/lib/apt/lists/* and try again: Works for some time.
> 

Ok. Thank you for additional details.

> 
> > (1) The strace output for the case of issuing the apt-get update (in the case of issue reproducing).
> 
> That will be hard to obtain except maybe if I alias my apt-get update
> to strace -f -o /boot/somefile.txt apt-get update and hope the problem
> occur again. It sometimes happen when launched from the Ubuntu Store
> which doesn't use bash to launch the update.
> 

Ok. I see. I'll try to analyze the issue on the basis of available
information. But it will be a great to have the requested strace output.

Thanks,
Vyacheslav Dubeyko.

> > (2) I need more details about your NILFS2 partition. Could you share output of "nilfs-tune -l"?
> 
> $ sudo nilfs-tune -l /dev/vgUbuntu/root
> nilfs-tune 2.1.4
> Filesystem volume name:  root
> Filesystem UUID:  336f247d-c8d1-4e91-887a-258121c4face
> Filesystem magic number:  0x3434
> Filesystem revision #:  2.0
> Filesystem features:      (none)
> Filesystem state:  invalid or mounted
> Filesystem OS type:  Linux
> Block size:  4096
> Filesystem created:  Thu Apr 11 22:34:29 2013
> Last mount time:  Mon Jul 22 13:35:46 2013
> Last write time:  Mon Jul 22 15:06:02 2013
> Mount count:  86
> Maximum mount count:  50
> Reserve blocks uid:  0 (user root)
> Reserve blocks gid:  0 (group root)
> First inode:  11
> Inode size:  128
> DAT entry size:  32
> Checkpoint size:  192
> Segment usage size:  16
> Number of segments:  25599
> Device size:  214748364800
> First data block:  1
> # of blocks per segment:  2048
> Reserved segments %:  5
> Last checkpoint #:  3229012
> Last block address:  17242181
> Last sequence #:  136170
> Free blocks count:  17827840
> Commit interval:  0
> # of blks to create seg:  0
> CRC seed:  0x7ab1d7ed
> CRC check sum:  0xfab54710
> CRC check data size:  0x00000118
> --
> 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


--
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

  parent reply	other threads:[~2013-07-23 11:15 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 [this message]
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
     [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=1374578141.2226.5.camel@slavad-ubuntu \
    --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