Stable File System for embedded product

[Rod Boyce]

I would much more strongly suggest not mounting this partition
read-write as this is most likely what is corrupting the partition also
try noatime as well.  /etc is required for boot up so I would suggest
changing the way you use /etc.  We have soft links to another location
on another file system and keep /etc combined with the root file system.
Upwards of 10K power cycles can't be wrong.


Rod

> -----Original Message-----
> From: Alex Zeffertt [mailto:ajz at cambridgebroadband.com]
> Sent: Monday, 19 January 2004 11:04 p.m.
> To: S. Hebbar
> Cc: linuxppc-embedded at lists.linuxppc.org
> Subject: Re: Stable File System for embedded product
>
>
> Are you using a flash device (i.e. /dev/mtdblockN) for /etc?  If so,
> then I would recommend JFFS for this partition.  JFFS2 is (supposedly)
> more reliable, but we have found that you can't fit it on a flash
> partition of only 4 flash sectors since it needs more than that for
> scratch.
>
> If it's not flash then maybe you should consider ext3 - a journalling
> extension to ext2.
>
> Alex
>
> On Mon, 2004-01-19 at 06:23, S. Hebbar wrote:
> > Hello,
> >
> > I am trying to find which file system is the best for
> > /etc partition on an embedded linux platform.
> >
> > I am using the following file systems for linux & rootfs:-
> > Linux: CramFS (linux 2.4.20 denx) (read-only)
> > RootFS: CramFS  (read-only)
> >
> > At the moment, I am using ext2 partition for /etc (read-write)
> > But, 1 out of  4 power-cycles of the board corrupts the
> > /etc partition.
> >
> > Any information related to the above topic is
> > grately appreciated.
> >
> > Regards,
> > S. Hebbar.
> >
> >
>
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/