Hello to All,
I am facing problems like various warnings after giving mount point
for jffs2 File System as /tmp dir .
I have Root file system as ext2 . Please can I be guided on foll :
1.) Is it that Mount point for filesystem should not be /tmp .
2.) Are there any other dir which should not be given as a mount
point for File system.
BR,
Mansi
Trimmed Cc: line.
On Mon, 2005-04-25 at 11:39 +0530, [email protected] wrote:
[...]
> I am facing problems like various warnings after giving mount point
> for jffs2 File System as /tmp dir .
Post details if you really want an idea of what went wrong/you did
wrong.
> I have Root file system as ext2 . Please can I be guided on foll :
>
> 1.) Is it that Mount point for filesystem should not be /tmp .
No.
> 2.) Are there any other dir which should not be given as a mount
> point for File system.
None.
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
[email protected] wrote:
> Hello to All,
> I am facing problems like various warnings after giving mount point
> for jffs2 File System as /tmp dir .
Please, post your warning. Post them better to the MTD list.
Before posting please explore carefully the
http://www.linux-mtd.infradead.org Web site.
Which flash do you use? How did you prepare your JFFS2 image?
--
Best regards, Artem B. Bityuckiy
Oktet Labs (St. Petersburg), Software Engineer.
+78124286709 (office) +79112449030 (mobile)
E-mail: [email protected], web: http://www.oktetlabs.ru
Thanks fo your response,
I use NOR flash . I am testing the system using LTP test case . Flash
Image is not prepared by me . I simply mount jffs2 on to a mount point
and test for jffs2 . But the behaviour is seen that if I give mount
point as /tmp and not any other directory I get abnormal behaviour like:
1.following log seen
[root@Linux tmp]$ waiting for chip to be ready timed out in word write
Write error in obliterating obsoleted node at 0x0011c570: -5
Unable to handle kernel NULL pointer dereference at virtual address
00000000
pgd = c3d08000
[00000000] *pgd=c3d4c011, *pte=00000000, *ppte=00000000
Internal error: Oops: 807 [#1].........................................
3.) mount after this I get
root@Linux /]$ mount -t jffs2 /dev/mtdblock0 /tmp
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x002a82a0:
0xffff in
stead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x002a82a4:
0x0057 in............................
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Artem B.
Bityuckiy
Sent: Monday, April 25, 2005 1:57 PM
To: Mahur Mansi (IFIN SCC SMS)
Cc: [email protected]; [email protected]
Subject: Re: Mounting File System .
[email protected] wrote:
> Hello to All,
> I am facing problems like various warnings after giving mount
> point for jffs2 File System as /tmp dir .
Please, post your warning. Post them better to the MTD list.
Before posting please explore carefully the
http://www.linux-mtd.infradead.org Web site.
Which flash do you use? How did you prepare your JFFS2 image?
--
Best regards, Artem B. Bityuckiy
Oktet Labs (St. Petersburg), Software Engineer.
+78124286709 (office) +79112449030 (mobile)
E-mail: [email protected], web: http://www.oktetlabs.ru
[email protected] wrote:
> I simply mount jffs2 on to a mount point
> and test for jffs2 . But the behaviour is seen that if I give mount
> point as /tmp and not any other directory I get abnormal behaviour like:
Frankly, I hardly understand what do you mean :-)
> 1.following log seen
> [root@Linux tmp]$ waiting for chip to be ready timed out in word write
> Write error in obliterating obsoleted node at 0x0011c570: -5
This implies JFFS2 can not write to flash. This must a problem of
underlying layers (your driver is buggy, your HW is broken, etc).
> Unable to handle kernel NULL pointer dereference at virtual address
> 00000000
This probably a bug in JFFS2 - it doesn't handle an error gracefully.
Please, do the following:
1. inform us about your kernel version;
2. explore http://www.linux-mtd.infradead.org carefully;
3. try the latest MTD snapshot;
4. post to the MTD mailing list - all the MTD people are there.
If the last snapshot doesn't help, then:
1. enable MTD debugging and JFFS2 debug level 1 in your .config;
2. post the JFFS2/MTD debugging output;
3. post the output of 'cat /proc/mtd;
4. use the last MTD snapshot.
Cheers,
Artem.
--
Best regards, Artem B. Bityuckiy
Oktet Labs (St. Petersburg), Software Engineer.
+78124286709 (office) +79112449030 (mobile)
E-mail: [email protected], web: http://www.oktetlabs.ru