From: enrico.scholz@sigma-chemnitz.de (Enrico Scholz)
To: linux-mtd@lists.infradead.org
Subject: Kernel oops with an unclean unmounted filesystem
Date: Mon, 24 Feb 2003 13:21:35 +0100 [thread overview]
Message-ID: <lywujpzx68.fsf@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <200302201248.48556.tglx@linutronix.de> (Thomas Gleixner's message of "Thu, 20 Feb 2003 12:48:48 +0100")
Thomas Gleixner <tglx@linutronix.de> writes:
>> ...
>> 4. - mkdir sleep
>> - ln -s /bin/sleep sleep/run
>> - echo 1 >sleep/params
>> - touch sleep/sync
>> 5. waited 1-2 seconds
>> 6. pressed the reset-button of the device
> ...
> No touch sleep/sync was your last action.
> Current CVS has a sanity check for this, so it should not Oops any more.
Thanks; with recent CVS version (20030223) it does not oops
anymore when mounting the filesystem.
When accessing the questionable directory (ls
/etc/minit/getty/sleep) the first time, the 'ls' process hangs in
D state. After rebooting 'ls' does not hang anymore but gives an
I/O error at sleep/sync. I can not remove this file; but because
the corruption seems to be caused by the writing-part of JFFS2
(see below), this is not a problem.
> It will give you just a warning. Please try, if you can
> reproduce it, by using the same procedure.
I can reproduce it 100% on a 2.5.59 kernel with any 'touch foo'
command. When using the CVS version of jffs2 (and commmenting out
the unpoint() stuff which does not compile with 2.5), things seem
to be fine and the filesystem does not become corrupted.
Thanks for your help
Enrico
next prev parent reply other threads:[~2003-02-24 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 12:35 Kernel oops with an unclean unmounted filesystem Enrico Scholz
2003-02-19 14:42 ` Thomas Gleixner
2003-02-19 20:22 ` Thomas Gleixner
2003-02-19 20:18 ` Enrico Scholz
2003-02-20 11:48 ` Thomas Gleixner
2003-02-24 12:21 ` Enrico Scholz [this message]
2003-02-20 13:34 ` David Woodhouse
2003-02-24 12:37 ` Enrico Scholz
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=lywujpzx68.fsf@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=linux-mtd@lists.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