RE: Questions about ubifs,ubi and mtd?

武井 克明
2018-12-12T01:07:59Z

Dear Richard,
Thank you for your comment.
We are using kernel 3.2.26 for reasons.
I can not update the kernel right now.

To everyone
Is there a lot of fixes and patches for processing that causes abnormal behavior as I asked you?
We hope to solve the problem by patch to kernel 3.2.26. if possible.
Shyly, I have little experience of developing ubifs or ubi, and I can not yet figure out which program is likely to be involved in this abnormal operation(ref. Note*).

Note*:
Nevertheless, when loading our program from 'rootfs-a', trying to read the inode with the ubifs_read_node() function will result in "bad node type" (ex: 193 but expected 9) and the LEB can not be read with the expected value. (Even though you do not have write access to rootfs) In addition, the file size may be 0 byte in some cases.

Best regards,
Katsuaki Takei/Oki Electric Industry Co., Ltd./JP

> -----Original Message-----
> From: Richard Weinberger <richard.weinberger@gmail.com>
> Sent: Wednesday, December 12, 2018 2:10 AM
> To: 武井 克明 <takei744@oki.com>
> Cc: linux-mtd@lists.infradead.org
> Subject: Re: Questions about ubifs,ubi and mtd?
>
> On Tue, Dec 11, 2018 at 3:09 PM 武井 克明 <takei744@oki.com> wrote:
> >
> > Hi all,
> >
> > We are developing the product using file system using ubi, ubifs on hardware
> with NAND flash memory.
> >
> > Although the development of the product was completed, we are seeking
> your help as the customer who is using it is having trouble with it.
> >
> > The product we have developed has 6 MTD partitions for NAND flash
> memory.
> > These consist of 6 MTDs named 'kernel-a' 'kernel-b', 'rootfs-a', 'rootfs-b',
> 'data-1', 'data-2', and online program only accesses 'data-1' and 'data-2' for
> write access.
> > Nevertheless, when loading our program from 'rootfs-a', trying to read
> > the inode with the ubifs_read_node() function will result in "bad node type"
> (ex: 193 but expected 9) and the LEB can not be read with the expected value.
> (Even though you do not have write access to rootfs) In addition, the file size
> may be 0 byte in some cases.
> >
> > Is there anyone who encountered such a problem? Is there patch?
>
> Well, are you using a recent kernel?