* czietz <bts@bts.grml.org> [20080930 20:30]:

> The problem seems to be resolved in the 2008-09-28 devel release. On one of the
> machines previously affected I was able to work for quite a long time(download
> and install packages, compile software etc.) without any signs of file system
> corruption.
> I still didn't have the time to verify that on the other machine.

Excellent news, thanks for testing!
I hereby close this bugreport, feel free to reopen the issue
if you encounter the problem again.

thanks!

regards,
-mika-

The problem seems to be resolved in the 2008-09-28 devel release. On one of the
machines previously affected I was able to work for quite a long time(download
and install packages, compile software etc.) without any signs of file system
corruption.
I still didn't have the time to verify that on the other machine.

Hi!

We have new develreleases being available at http://debian.netcologne.de/
www.grml.org/devel/ - any chance that you could try to test them and report 
whether the issue is still present for you?

thx && regards,
-mika-

* czietz <bts@bts.grml.org> [20080602 19:30]:

> When using grml64 0.2 (and be it just a "apt-get update"), the file system
> (aufs) gets destroyed. Seemingly random files point to other random files via a
> link. For example files in /usr/include may point to files in /usr/man/. Which
> files are affected differs every time grml64 is restarted.

> This bug appears on two machines with different hardware configurations. The
> grml64-CD was checked against the MD5 hash published on the download page and
> found to be correctly burned. The RAM of the machines was checked for errors.
> There are no suspicious entries in the syslog. grml (the 32 bit version) runs
> without such errors.

Thanks for reporting!

As discussed in de.comp.os.unix.linux.misc testing with a new grml
version would be great. Hopefully we'll be able to provide an ISO
with a newer, current Linux kernel within the next weeks. In the
meantime daily snapshots (though with the same kernel as provided by
grml64 0.2) are available from daily.grml.org

I'll ping you as soon as we have a new grml version which might be
interesting for you. :)

thx && regards,
-mika-

When using grml64 0.2 (and be it just a "apt-get update"), the file system
(aufs) gets destroyed. Seemingly random files point to other random files via a
link. For example files in /usr/include may point to files in /usr/man/. Which
files are affected differs every time grml64 is restarted.

This bug appears on two machines with different hardware configurations. The
grml64-CD was checked against the MD5 hash published on the download page and
found to be correctly burned. The RAM of the machines was checked for errors.
There are no suspicious entries in the syslog. grml (the 32 bit version) runs
without such errors.