From: David Woodhouse <dwmw2@infradead.org>
To: decouto@lcs.mit.edu
Cc: mtd@infradead.org, ipaq@handhelds.org
Subject: Re: jffs2 problem
Date: Fri, 23 Mar 2001 14:31:22 +0000 [thread overview]
Message-ID: <12498.985357882@redhat.com> (raw)
In-Reply-To: <200103231425.f2NEPYH21217@new-york.lcs.mit.edu>
decouto@lcs.mit.edu said:
> i tried it again, but definitely erasing first. similar thing:
> Argh. Special inode #1011 had more than one node
Very strange. Can you change DEFAULT_CONSOLE_LOGLEVEL to 8 in kernel/
printk.c, boot it and log all the messages? There'll be lots.
decouto@lcs.mit.edu said:
> hmmm. my last checkout and compile was say weds 21 march.
Ought to be OK. I haven't knowingly fixed something since then which I
think could cause this behaviour.
What is ino #1101?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-03-23 14:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 2:02 jffs2 problem Douglas S. J. De Couto
2001-03-23 8:37 ` David Woodhouse
2001-03-23 14:25 ` Douglas S. J. De Couto
2001-03-23 14:31 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-30 22:03 JFFS2 Problem Jeff Smith
2001-05-03 21:55 ` David Woodhouse
2001-09-03 8:49 jffs2 problem Wojciech Kromer
2002-07-10 21:52 JFFS2 Problem Snehaprabha
2002-07-11 7:05 ` David Woodhouse
2002-07-11 19:18 ` Snehaprabha
2002-07-11 19:32 ` Russ Dill
2002-07-11 13:29 Frederic Giasson
2003-07-30 2:37 JFFS2 problem Vikram Mehta
2004-03-22 16:18 Michael Palme
2004-06-09 6:57 jffs2 problem zhang hao
2004-06-09 9:41 ` David Woodhouse
2005-07-19 10:11 Hinko Kocevar
2005-07-19 10:32 ` Artem B. Bityuckiy
2005-07-19 10:58 ` Hinko Kocevar
2005-07-19 11:05 ` Artem B. Bityuckiy
2005-07-19 11:45 ` Hinko Kocevar
2005-07-19 12:05 ` Artem B. Bityuckiy
2005-07-19 12:09 ` Steven Scholz
2005-07-19 12:21 ` Artem B. Bityuckiy
2005-07-19 12:19 ` Hinko Kocevar
2005-07-19 12:30 ` Hinko Kocevar
2006-08-10 8:29 JFFS2 problem Amit Kumar Sharma
2006-08-10 9:32 ` Artem B. Bityutskiy
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=12498.985357882@redhat.com \
--to=dwmw2@infradead.org \
--cc=decouto@lcs.mit.edu \
--cc=ipaq@handhelds.org \
--cc=mtd@infradead.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