headers
Philipp Gühring | 1 Sep 2005 11:37
Picon

JFFS2 on normal block devices?

Hi,

We are using CF-Flash cards, which are made available as IDE harddisks to the 
system. Since they have longterm stability problems with normal filesystems, 
I would like to use JFFS for it instead.

How much work is necessary to port JFFS2 to normal block devices?
Who could do it?
Has anyone already done it?
Does it make sense to do it at all?

Regards,
Philipp Gühring

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo <at> axis.com
Permalink | Reply | 2 comments |
headers
Tino Keitel | 1 Sep 2005 12:10
Favicon

Re: JFFS2 on normal block devices?

On Thu, Sep 01, 2005 at 11:37:13 +0200, Philipp Gühring wrote:
> Hi,
> 
> We are using CF-Flash cards, which are made available as IDE harddisks to the 
> system. Since they have longterm stability problems with normal filesystems, 
> I would like to use JFFS for it instead.
> 
> How much work is necessary to port JFFS2 to normal block devices?

Just use BLKMTD.

Regards,
Tino

--

-- 
Tino Keitel
Software Engineer

Innominate Security Technologies AG  /device attached security/
tel: +49.30.6392-3309
fax: +49.30.6392-3307
Albert-Einstein-Str. 14
D-12489 Berlin, Germany
www.innominate.com

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo <at> axis.com
Permalink | Reply | 1 comment |
headers
Jörn Engel | 1 Sep 2005 13:39
Picon

Re: JFFS2 on normal block devices?

On Thu, 1 September 2005 12:10:15 +0200, Tino Keitel wrote:
> On Thu, Sep 01, 2005 at 11:37:13 +0200, Philipp Gühring wrote:
> > 
> > We are using CF-Flash cards, which are made available as IDE harddisks to the 
> > system. Since they have longterm stability problems with normal filesystems, 
> > I would like to use JFFS for it instead.
> > 
> > How much work is necessary to port JFFS2 to normal block devices?
> 
> Just use BLKMTD.

Or block2mtd.

Jörn

--

-- 
When I am working on a problem I never think about beauty.  I think
only how to solve the problem.  But when I have finished, if the
solution is not beautiful, I know it is wrong.
-- R. Buckminster Fuller

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo <at> axis.com
Permalink | Reply | 0 comments |
headers
Randy Graham | 3 Sep 2005 01:06

Flash errors on axis 83+ device server?

I don't know if this is the correct forum for this question, but .....

Can anyone tell me the most likely cause of the following errors I found 
in my /var/log/messages file on my 83+ board?

Aug 31 05:10:15 AxisProduct kernel: Warning: DQ5 raised while erase 
operation was in progress, but erase completed OK
Aug 31 18:26:17 AxisProduct kernel: Warning: DQ5 raised while erase 
operation was in progress, but erase completed OK
Sep  1 04:59:29 AxisProduct kernel: Warning: DQ5 raised while erase 
operation was in progress, but erase completed OK
Sep  1 05:41:04 AxisProduct kernel: Warning: DQ5 raised while erase 
operation was in progress, but erase completed OK
Sep  1 10:18:36 AxisProduct kernel: Write of 68 bytes at 0x0049ffbc 
failed. returned -22, retlen 68
Sep  1 10:39:29 AxisProduct kernel: Warning: DQ5 raised while erase 
operation was in progress, but erase completed OK

I'm most concerned about the write error, which  occurred while my app 
was writing to disk (indirectly while updating a SQLite database file).

-Randy

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo <at> axis.com
Permalink | Reply | 0 comments |
headers
Randy Graham | 20 Sep 2005 22:11

Write errors and warnings in /var/log/messages file.

Can someone at Axis explain to me the significance of these kernel
messages I'm seeing in /var/log/messages on my device server 83+ board?

Sep 12 18:47:14 AxisProduct kernel: Warning: DQ5 raised while erase
operation was in progress, but erase completed OK
Sep 12 22:17:05 AxisProduct kernel: Write of 68 bytes at 0x0049ffbc
failed. returned -22, retlen 68
Sep 13 02:42:11 AxisProduct kernel: Write of 68 bytes at 0x0049ffbc
failed. returned -22, retlen 68
Sep 13 21:58:21 AxisProduct kernel: Warning: DQ5 raised while erase
operation was in progress, but erase completed OK
Sep 14 08:49:02 AxisProduct kernel: Warning: DQ5 raised while erase
operation was in progress, but erase completed OK

All my application code lives in user space and I have no custom drivers
or kernel hacks installed so I don't see how my application could be
directly responsible for these messages.

Is it possible that my flash is becoming exhausted?

-Randy

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo <at> axis.com
Permalink | Reply | 0 comments |
headers
Andrew Lunn | 20 Sep 2005 23:14
Picon

Compilation errors with latest CVS code

Hi folks

Im using the MTD CVS trunk from today along with Linux 2.6.13.  I'm
not using NAND flash, NOR flash with transparent ECC or DataFlash, so
i disabled JFFS2_FS_WRITEBUFFER. The compilation the fails:

  CC      fs/jffs2/compr.o
  CC      fs/jffs2/dir.o
  CC      fs/jffs2/file.o
fs/jffs2/file.c: In function 'jffs2_fsync':
fs/jffs2/file.c:39: warning: statement with no effect
  CC      fs/jffs2/ioctl.o
  CC      fs/jffs2/nodelist.o
fs/jffs2/nodelist.c: In function 'check_node_data':
fs/jffs2/nodelist.c:415: error: 'struct jffs2_sb_info' has no member named 'wbuf_pagesize'
fs/jffs2/nodelist.c:417: error: 'struct jffs2_sb_info' has no member named 'wbuf_pagesize'
make[2]: *** [fs/jffs2/nodelist.o] Error 1
make[1]: *** [fs/jffs2] Error 2

wbuf_pagesize only exists when JFFS2_FS_WRITEBUFFER is enabled, but it
is incorrectly used unconditionally in a few places like above.

Any chance of fixing this?

        Thanks
                Andrew

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo <at> axis.com
(Continue reading)

Permalink | Reply | 0 comments |
headers
Artem B. Bityutskiy | 21 Sep 2005 12:21
Picon
Favicon

Re: Compilation errors with latest CVS code

Andrew Lunn wrote:
> Hi folks
> 
> Im using the MTD CVS trunk from today along with Linux 2.6.13.  I'm
> not using NAND flash, NOR flash with transparent ECC or DataFlash, so
> i disabled JFFS2_FS_WRITEBUFFER. The compilation the fails:

Josh Boyer wrote:
 > Argh guys!  When compiling with CONFIG_JFFS2_FS_WRITEBUFFER not set we
 > get the following error:

I'll take care about this today.

--

-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 0 comments |
headers
Artem B. Bityutskiy | 21 Sep 2005 15:29
Picon
Favicon

Re: Compilation errors with latest CVS code

Artem B. Bityutskiy wrote:
> Andrew Lunn wrote:
> 
>> Hi folks
>>
>> Im using the MTD CVS trunk from today along with Linux 2.6.13.  I'm
>> not using NAND flash, NOR flash with transparent ECC or DataFlash, so
>> i disabled JFFS2_FS_WRITEBUFFER. The compilation the fails:
> 
> 
> Josh Boyer wrote:
>> Argh guys!  When compiling with CONFIG_JFFS2_FS_WRITEBUFFER not set we
>> get the following error:
> 
> I'll take care about this today.
> 
Fixed.
--

-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 0 comments |
headers
Mats Friberg | 23 Sep 2005 07:23
Picon
Favicon

RE: Write errors and warnings in /var/log/messages file.

I'm guessing you're using an old kernel when you get this.
It should be solved if you get a newer one.

For more info about Dairy queen 5 problem see. 
http://lists.infradead.org/pipermail/linux-mtd/2003-March/007246.html

It shouldn't cause you any problem and is not a sign of flash getting
exhausted.

Mats

-----Original Message-----
From: owner-jffs-dev <at> axis.com [mailto:owner-jffs-dev <at> axis.com] On Behalf
Of Randy Graham
Sent: den 20 september 2005 22:12
To: jffs-dev <at> axis.com
Subject: Write errors and warnings in /var/log/messages file.

Can someone at Axis explain to me the significance of these kernel
messages I'm seeing in /var/log/messages on my device server 83+ board?

Sep 12 18:47:14 AxisProduct kernel: Warning: DQ5 raised while erase
operation was in progress, but erase completed OK Sep 12 22:17:05
AxisProduct kernel: Write of 68 bytes at 0x0049ffbc failed. returned
-22, retlen 68 Sep 13 02:42:11 AxisProduct kernel: Write of 68 bytes at
0x0049ffbc failed. returned -22, retlen 68 Sep 13 21:58:21 AxisProduct
kernel: Warning: DQ5 raised while erase operation was in progress, but
erase completed OK Sep 14 08:49:02 AxisProduct kernel: Warning: DQ5
raised while erase operation was in progress, but erase completed OK
(Continue reading)

Permalink | Reply | 0 comments |

Gmane