Skip to contentSkip to conversation

possible bug in "--pad" option for mkfs.jffs2?

DISCUSSION Ryan B. Lynch 3 participants 5 messages Aug 15, 2005 Memory technology devices (MTD)

lore
Share & tools
lore

Ryan B. Lynch

author
#0 lore raw

I don't know if this is really a bug, but mkfs.jffs2 doesn't seem to be working entirely as advertised for me. I'm trying to use the "--pad" option to create some relatively large JFFS2 images (~200-950 MB). I know that these are larger than is common, so I'm also on the lookout for size-related limitations.

I run 'mkfs.jffs2' with the following command line:

 $ /usr/sbin/mkfs.jffs2 \
Quoted 4 lines
   -r /tmp/root \
   -o /tmp/image-20050815.160044.jffs2 \
   -e 0x10000 \
   -p 214171648

The image size is NOT padded to 214,171,648 bytes, though--the size depends on the contents of the filesystem (I tried varying it a little to see what happens). I'm assuming that "-e" and "-p" both take values in bytes... Maybe someone can correct me on that?

Can anyone correct me, or give me some troubleshooting direction?

Thanks for the help,
Ryan

author
#1 lore raw

I did a little more testing with this, and the "--pad" option doesn't work AT ALL on my installation. Something is definitely wrong, here.

I compiled JFFS2 from source, using a CVS snapshot from 2005/08/14, with the "jffs2-summary-20050811-v2.patch" applied.

Can anyone confirm this?

-Ryan

Quoted 30 lines · Ryan B. Lynch

I don't know if this is really a bug, but mkfs.jffs2 doesn't seem to be working entirely as advertised for me. I'm trying to use the "--pad" option to create some relatively large JFFS2 images (~200-950 MB). I know that these are larger than is common, so I'm also on the lookout for size-related limitations.

I run 'mkfs.jffs2' with the following command line:

$ /usr/sbin/mkfs.jffs2 \
Quoted 4 lines
   -r /tmp/root \
   -o /tmp/image-20050815.160044.jffs2 \
   -e 0x10000 \
   -p 214171648

The image size is NOT padded to 214,171,648 bytes, though--the size depends on the contents of the filesystem (I tried varying it a little to see what happens). I'm assuming that "-e" and "-p" both take values in bytes... Maybe someone can correct me on that?

Can anyone correct me, or give me some troubleshooting direction?

Thanks for the help,
Ryan

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

#2 lore raw
Quoted 7 lines · Ryan B. Lynch

I did a little more testing with this, and the "--pad" option doesn't work AT ALL on my installation. Something is definitely wrong, here.

I compiled JFFS2 from source, using a CVS snapshot from 2005/08/14, with the "jffs2-summary-20050811-v2.patch" applied.

Can anyone confirm this?

Dunno, never used this option (what for?). Glance at utils/mkfs.jffs2.c. :-)

Signature · 3 lines
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
author
#3 lore raw

Hey,

Quoted 4 lines · Artem B. Bityuckiy

Ryan B. Lynch wrote:

Dunno, never used this option (what for?). Glance at utils/mkfs.jffs2.c. :-) \

The "--pad" option? From the manpage:

"-p, --pad[=SIZE]

    Pad output to SIZE bytes with 0xFF.  If SIZE is not specified, the

output is padded to the end of the final erase block."

I'm looking at the C source right now, too... gonna see if I can figure out WTF is going on.

-Ryan

#4 lore raw
In reply to Ryan B. Lynch

Hi Ryan,

Quoted 11 lines

I run 'mkfs.jffs2' with the following command line:

$ /usr/sbin/mkfs.jffs2 \
Quoted 4 lines
   -r /tmp/root \
   -o /tmp/image-20050815.160044.jffs2 \
   -e 0x10000 \
   -p 214171648

The image size is NOT padded to 214,171,648 bytes, though--the size

Do not use space between -p and its parameter. It will work.

It is getopt bug (or feature) which happens using optional parameter.

If we whould change it to required parameter, than both "-p X" and "-pX" would be OK, but in this case "-p X" means "-p" without parameter and X
- if I'm right.

Ferenc