From: tommy <jiujin.hong@mid-fun.com>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: about ubifs question
Date: Wed, 19 Aug 2009 14:28:50 +0800 [thread overview]
Message-ID: <1250663330.13486.1.camel@tommy-desktop> (raw)
In-Reply-To: <1250658794.3885.1.camel@localhost>
hi,sir !
Can you explain why my ubifs switch to read-only filesystem when it resume from suspend !
Unmounting local filesystems...
mount: can't find /mnt/ram in /proc/mounts
UBIFS error (pid 1201): make_reservation: cannot reserve 160 bytes in jhead 1, error -30
UBIFS error (pid 1201): ubifs_write_inode: can't write inode 135, error -30
UBIFS error (pid 1201): make_reservation: cannot reserve 160 bytes in jhead 1, error -30
UBIFS error (pid 1201): ubifs_write_inode: can't write inode 442, error -30
UBIFS error (pid 1201): make_reservation: cannot reserve 160 bytes in jhead 1, error -30
UBIFS error (pid 1201): ubifs_write_inode: can't write inode 136, error -30
UBIFS: cannot re-mount due to prior errors
mount: mounting ubi0:rootfs on / failed: Read-only file system
On 三, 2009-08-19 at 08:13 +0300, Artem Bityutskiy wrote:
> On Wed, 2009-08-19 at 12:39 +0800, tommy wrote:
> > about ubifs work under Kernel suspend and resume
> >
> > When Kernel resume from suspend by apm -s ,
> >
> > i touch file in nand flash and sync,but when Kernel restart ,my touched
> > file didn't occur!
>
> How do you restart your kernel? Do you unmount cleanly?
>
> > After Kernel resume ,i guess my touched file isn't in nand flash but
> > memory !
>
> Try typing sync before restarting.
>
next prev parent reply other threads:[~2009-08-19 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 4:39 about ubifs question tommy
2009-08-19 5:13 ` Artem Bityutskiy
[not found] ` <1250660141.11476.4.camel@tommy-desktop>
2009-08-19 5:51 ` Artem Bityutskiy
2009-08-19 6:28 ` tommy [this message]
2009-08-19 6:35 ` tommy
2009-08-19 10:56 ` tommy
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=1250663330.13486.1.camel@tommy-desktop \
--to=jiujin.hong@mid-fun.com \
--cc=dedekind@infradead.org \
--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