JFFS2 an nodes checking

[Artem B. Bityuckiy]

> Yes, he does. The problem is that each time you access a FIFO you update
> its ctime and mtime on the flash... which leads to a _lot_ of nodes,
> only one of which is non-obsolete. That's a problem on NAND flash.

Things are same for regular files. This is from SUSv3 for write() call:

"Upon successful completion, where nbyte is greater than 0, write() 
shall mark for update the st_ctime and st_mtime fields of the file"

This is from SUSv3 fore read() call:

"Upon successful completion, where nbyte is greater than 0, read() shall 
mark for update the st_atime field of the file, and shall return the 
number of bytes read."

What's special with FIFOs ?

Why that's a problem on NAND flash especially ?


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