Hello Warner, > If you booted a kernel from approximately April 15th through May 3th, > there were a number of small, but critical, vm bugs. This can cause > file system corruption, and leave silent landmines for later. It is > recommended that if you did boot these kernels, you build a newer > kernel, come up in single user and force an fsck on all filesystems. > This is to prevent 'false' panics later that are a result of the > corruption that might be dormant in them now. could this bug have caused corruption of the content of files as well ? i am having relatively rare cases of corrupted (32kb sized blocks of) data which i copy from disk to disk - and am now wondering if this might be related. thanks, HeikoReceived on Tue May 06 2003 - 02:18:59 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:06 UTC