On Wed, 2002-03-20 at 09:23, Bas wrote:
> The following has happened:
> Today I was editing some files on my / filesystem. I had made some changes
> to one of my startup scripts and the configuration file for samba, which are
> one the same filesystem. When I tried to look into the logfile directory,
> which is a separate lv, I could run ls, but when I ran ls -la, it hung. Only
> option was to reboot, but I waited a little, probably enough time to clear
> the changes to disk. After a reboot I noticed the files I had changed were
> indeed changed, the still had the same size, but were filled with ^@
> characters -> This was visible through vim. Funny thing is that the backup
> files vi makes (.rc.samba.swp) were also damaged and not useable anymore.
The real culprit here is the fact that your machine locked up - when
this happens, there's no telling what data may or may not get down to
The ^@ (null) characters you saw as a result are explained in the FAQ.
I have no experience with evms, so I can't say whether that could have
been a factor.
You might consider compiling kdb into your kernel, so that if it locks
up again, you can break into kdb and see what's going on (a simple "bt"
command would probably show where things got stuck.)
p.s. the weekly patches were dropped in favor of the "split" patches; it
was felt that we had too many patch versions floating around out there.
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc.