cramfs root filesystem corruption

Kári Davíðsson kd at flaga.is
Sat Jun 1 00:07:25 EST 2002


Inactive meaning "unmounted" or just not beeing used?

K.D.

> -----Original Message-----
> From: Paul Ruhland [mailto:pruhland at microwavedata.com]
> Sent: 31. maí 2002 14:04
> To: wd at denx.de
> Cc: linuxppc-embedded at lists.linuxppc.org
> Subject: Re: cramfs root filesystem corruption
>
>
>
> 200205301450.50112.pruhland at microwavedata.com> you wrote:
> >> The cramfs image is in flash, mounted as root via mtd blockdevice.
> >> Typically the error occurs during flash reprogramming (
> using mtd char
> >> device '/dev/mtd0' ) ...during/after flash programming the cramfs
> >> filesystem 'loses' information ( files disappear ).  The
> errors from syslog
> >> are 'error during decompression', typically the error
> numbers ( from
> >> 'linux/zlib_fs.h' ) are Z_BUF_ERROR, for the first error,
> and Z_DATA_ERROR
> >> for the rest.
> >
> > Ummm... can you please explain EXACTLY what you
> > are doing? You have a
> > cramfs in flash, mounted as root, and you are erasing and
> overwriting
> > the SAME cramfs partition WHILE RUNNING FROM IT?
> >
>
> No, I have redundant cramfs images in flash.  I am erasing
> and overwriting the
> inactive image while the other, active image,  is mounted as root.
>
>
>
>

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





More information about the Linuxppc-embedded mailing list