From: Wakko Warner <wakko@animx.eu.org>
To: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Cc: linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NILFS crash on 2.6.37
Date: Sat, 22 Jan 2011 11:09:38 -0500 [thread overview]
Message-ID: <20110122160938.GA23181@animx.eu.org> (raw)
In-Reply-To: <20110122.230956.176521815.ryusuke@osrg.net>
Ryusuke Konishi wrote:
> On Fri, 21 Jan 2011 20:57:48 -0500, Wakko Warner wrote:
> > That patch fix it. Just a note, the 2.6.37 vanilla source was about 20
> > lines up from 704
>
> Thanks for testing. Will send upstream and to stable.
No problem.
> > > > > [ 1202.581501] NILFS warning: broken superblock. using spare superblock.
> > > > > [ 1202.582093] NILFS warning: broken superblock. using spare superblock.
> >
> > Why does it say this 2 times? Just curious.
>
> Because each super block is read twice in different block sizes.
>
> Well, indeed it looks confusing. I'll try to do something.
Ah, I see.
--
Microsoft has beaten Volkswagen's world record. Volkswagen only created 22
million bugs.
prev parent reply other threads:[~2011-01-22 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 2:49 NILFS crash on 2.6.37 Wakko Warner
2011-01-21 7:37 ` Ryusuke Konishi
2011-01-21 9:18 ` Ryusuke Konishi
2011-01-22 1:57 ` Wakko Warner
2011-01-22 14:09 ` Ryusuke Konishi
2011-01-22 16:09 ` Wakko Warner [this message]
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=20110122160938.GA23181@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.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