Eric Sandeen was good enough to email me a utility which looks for
null'd files. That found a few of them. Most of /usr/local/lib
(anything that had been open ~30 seconds before going to single user
mode) got the whack. When the system oops'd I didn't have any files
open. But it seems like anything that had been open up to 30 seconds
before the crash was corrupted. 'Recovery' took place after reboot. Is
there any chance that rmap11c, preempt or some of the hash patches I'm
using is causing this behaviour? I was running XFS for months with no
lost files. Recently any time my system crashes though I lose
something. Thanks.
-Blake
Whatchu talkin' 'bout, Willis?
> At 14:38 23-1-2002 -0500, Blake Matheny wrote:
> >I am using the latest XFS from CVS with kernel version 2.4.17. I'm
> >also using the rmap and preempt patches. Recently I had a kernel oops
> >when I was in single user mode, kdb reported it being at line 812 in
> >page_buf_io.c from the xfs source. When this happened several files
> >got hosed, including my /etc/fstab.
> >First, is this a known problem or is there something I can do to fix
> >it? Looking at the source there didn't appear to be a blatently
> >obvious fix. Second, is there some way to see which file were filled
> >with null bytes? Several applications are no longer able to run, it
> >appears that a few different libraries were also hosed. I'm not on the
> >list so please CC me if you have any answers. Thanks.
> >-Blake
>
> Did you edit some files with vi?
>
> Yes? See FAQ
> No? What were you busy with doing in single user mode? Did recovery take
> place after a reboot or did the fs need fixing?
>
> Cheers
>
>
>
> --
> Seth
> Every program has two purposes one for which
> it was written and another for which it wasn't
> I use the last kind.
|