Linux NILFS development
 help / color / mirror / Atom feed
From: Anton Eliasson <devel-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
To: slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Nilfs2 crash debugging
Date: Mon, 26 Aug 2013 20:37:56 +0200	[thread overview]
Message-ID: <521BA084.80901@antoneliasson.se> (raw)
In-Reply-To: <1377510966.2621.3.camel@slavad-ubuntu>

Vyacheslav Dubeyko skrev 2013-08-26 11:56:
> On Sun, 2013-08-25 at 17:02 +0200, Anton Eliasson wrote:
>
> [snip]
>> Yes. Here's another huge kernel.log for you [2]. It's 19 MB compressed
>> and 282 MB uncompressed. I blanked the log while running the stock
>> kernel and then rebooted to the custom debugging kernel. X wouldn't
>> start so I just logged in to a virtual terminal, changed directory to
>> "~/Bilder/20130321-28 Jakobs bilder från Nederländerna" and then
>> executed `cat 179.JPG >/dev/null`.
>>
>> This caused a read-only remount and a bunch of "broken bmap" messages to
>> show, followed by an "Input/Output error". I saved a copy of
>> /var/log/kernel.log as soon as I could after that, before reinstalling
>> the stock kernel and rebooting.
>>
>> [1]: http://antoneliasson.se/publicdump/config.x86_64.last.20130825
>> [2]: http://antoneliasson.se/publicdump/kernel.log.20130825.gz
>>
> Yes, it's great. Thank you. Now I can investigate the issue's
> environment. I suspect that this issue is related to the issue with
> "unable to handle kernel paging request" in nilfs_end_page_io(). But,
> maybe, I am wrong. Anyway, it is a good basis for more detailed
> understanding of the issue.
>
> Thanks,
> Vyacheslav Dubeyko.
>
>
You're welcome. And thank you for your thorough instructions. It's been 
very informative and worthwhile for me to patch and build a kernel with 
custom options. Let me know if you need more experiments run on the 
damaged filesystem. Otherwise I'll delete the stored disk images in a 
month or two.

-- 
Best Regards,
Anton Eliasson

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

  reply	other threads:[~2013-08-26 18:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51F2A8A4.4020400@antoneliasson.se>
     [not found] ` <51F2A8A4.4020400-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-07-26 16:52   ` Fwd: Re: Broken nilfs2 filesystem Anton Eliasson
     [not found]     ` <51F2A945.6050909-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-07-27 16:23       ` Vyacheslav Dubeyko
     [not found]         ` <9016EBD5-1E01-476F-B1B9-66AE593F4728-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-07-27 22:32           ` Anton Eliasson
2013-08-15 10:40           ` Nilfs2 crash debugging (was: Broken nilfs2 filesystem) Anton Eliasson
     [not found]             ` <520CB032.2000602-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-08-16  7:11               ` Vyacheslav Dubeyko
2013-08-19 19:55               ` Vyacheslav Dubeyko
     [not found]                 ` <FEA41B6A-7D82-4563-AAF5-D5AFA3734D79-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-08-25 15:02                   ` Nilfs2 crash debugging Anton Eliasson
     [not found]                     ` <521A1C88.9080100-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-08-26  9:56                       ` Vyacheslav Dubeyko
2013-08-26 18:37                         ` Anton Eliasson [this message]
     [not found]                           ` <521BA084.80901-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-08-30  5:58                             ` Vyacheslav Dubeyko
2013-09-04 19:39                               ` Anton Eliasson
     [not found]                                 ` <52278C63.6090303-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-09-04 20:00                                   ` 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=521BA084.80901@antoneliasson.se \
    --to=devel-17olwe7vw2dlc78zk6colg@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=slava-yeENwD64cLxBDgjK7y7TUQ@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