Re: [Yaffs] [EXTERNAL] Re: file doesn't exist

>     bool success = false;

>     int file;

>     uint8_t num_retries = 0;

>     os_itv_set(OS_WAIT_50_MSEC);

>     if ( model != MODEL_UNKNOWN ) //should we even bother??

>     {

>         while(( num_retries < NUM_WRITE_RETRIES ) && ( !success ))

>         {

>             num_retries++;

>             // Write the default Security Codes Configuration.

>             if ( (file = *ffs_open*(filesystemname,
> O_CREAT|O_RDWR|O_TRUNC, S_IREAD|S_IWRITE)) != -1)

>             {

>                 os_itv_wait();

>                 // Default high priority codes.

>                 if ( *ffs_write*(file, (void *)&HighSecurityConfig,
> sizeof(security_config_t)) != -1)

>                 {

>                     os_itv_wait();

>                     // Next default low priority codes.

>                     if(*yaffs_lseek*(file, sizeof(security_config_t),
> SEEK_SET) != -1)

>                    {

>                         os_itv_wait();

>                         if ( *ffs_write*(file, (void
> *)&LowSecurityConfig, sizeof(security_config_t)) != -1)

>                         {

>                             success = true;

>                         }

>                     }

>                 }

>                 os_itv_wait();

>                 *ffs_close*(file);

>             }

>         }

>     }

>     return success;

>    1. 32 blocks is reasonably small for a Yaffs partition. Not too small,
>    but still smaller than normal. That in itself should not be an issue. How
>    many files are there? How much free space is there before modifying the
>    files?

>    1. Most of are partitions are 32 blocks

>                                                                i.      I’m
> not sure why we designed it this way, I was not the original designer. In
> fact on our other device I got rid of all the config partitions and made
> them one, now we just have 3  (cfgs, activity_logs & call_playback ).

>    1. Our first partition has 10 files not including the lost+found (See
>       below in list)

>                                                                i.      The
> rootCA, deviceKey, and deviceCert are not written be default only when we
> need them.

>    1. So we have 7 of 32 blocks used (25 free blocks) (or did you want
>             the number of bytes free?)

>    1. Are the other partitions mounted at the same time or are they left
>    unmounted?

>    1. All the partitions are mounted at the power up. I thought maybe it
>       was a mounting issue, but don’t see any mount failures.

> yaffs_comm_configs_device                       start=1,
> end =32               (32 blocks)

> yaffs_config_profiles_device                       start=33,
> end =64               (32 blocks)

> yaffs_gps_configs_device                             start=65,
>              end =96               (32 blocks)

> yaffs_misc_configs_device                           start=97,
> end =128             (32 blocks)

> yaffs_mode_configs_device                        start=129,            end
> =144             (16 blocks)

> yaffs_security_codes_device                      start=145,            end
> =176             (32 blocks)

> yaffs_time_configs_device                          start=177,
> end =208             (32 blocks)

> yaffs_activity_logs_device                           start=209,
> end =848             (640 blocks)

> yaffs_call_playback_device                          start=849,
> end =1023           (175 blocks)

> /comm_cfgs:
> 515 100600 1 0 4097 2048 3 rootCA                        (doesn’t always
> exist)
> 514 100600 1 0 4097 2048 3 deviceKey                 (doesn’t always exist)
> 769 100600 1 0 4097 2048 3 deviceCert                (doesn’t always exist)
> 2263 100600 1 0 138 2048 1 Ntcip1211
> 262 100600 1 0 272 2048 1 ActiveCallCfg
> 261 100600 1 0 16 2048 1 NetworkUDPCfg
> 260 100600 1 0 4 2048 1 ServiceAdr
> 259 100600 1 0 10 2048 1 SerialCom
> 2 40666 1 0 2048 2048 1 lost+found/
> 258 100600 1 0 24 2048 1 Network
> 257 100600 1 0 401 2048 1 ModemInit

>    1. Initial power-up we default our configuration files.

>    1. We have multiply mount points but it appears to happen only on the
>       first mount point. Blocks 1-32

>    1. Reboot and files all exist in fist mount point. (yaffs_lstat
>    returns 0)
>    2. Do a write to a file in first mount point

>    1. Any file (from what I can tell)

>    1. Reboot and all files don’t exist (yaffs_lstat returns -1)
>    2. From then on any write and reboot the files will exist.

>    1. I haven’t been able to reproduce it after this.