Yep, when we got multiple entries here, neither check nor repair complained.
I guess it's not fundamentally inconsistent from a filesystem integrity
perspective, but it does not make the operating system happy.
We don't have a root cause for this one, we think it's another way
that the shutdown problem exhibited itself. If you can run the latest
code (1.2pre5) the shutdown problem should be fixed, and if you see
it again, let us know!
On Mon, 13 Jan 2003, Michael Sinz wrote:
> Eric Sandeen wrote:
> > We've actually seen this here too, recently. We -think- it is the
> > result of previous filesystem corruption on shutdown, which should now
> > be fixed. Did you have any filesystem shutdowns or other corruption
> > before this? The possible corruption bug that was fixed could even
> > happen on a clean shutdown, unfortunately.
> Well, there was that one time a while back (late November?) where
> XFS was broken (clean shutdown would prevent a boot due to some
> block information being confused) I reverted and recovered back then
> and had not had a crash (unclean shutdown) since then.
> Also, some more information: xfs_check was returning that the system
> was clean (all OK, not even a minor warning) and yet I had a number of
> "mtab" files in /etc. In fact, I had a hard time getting rid of them.
> Using "rm" did not work well (that would really confuse the directory
> and required a shutdown/reboot to recover from - and still multiple
> /etc/mtab files)
> In finally fixed it my doing a "mv /etc/mtab* /junk/" (I had created
> that directory. All of the mtab file entries were no gone from /etc
> and /junk had only one. (and a simple rm -rf /junk cleaned that up)
> xfs_check still claims all is fine.
> Michael Sinz -- Director, Systems Engineering -- Worldgate Communications
> A master's secrets are only as good as
> the master's ability to explain them to others.