On Sat, 14 Jul 2001, Colin Walters wrote:
> When I tried to set up an 'at' command today, it told me I didn't have
> permissions; this confused me until I looked at /etc/at.deny, which
> was about 100 null characters. Following this, I noticed that one of
> my old emails had been destroyed too.
I have had this corruption using bad memory in the 2.4.0-test releases.
After replacing it I have not been able to replicate this.
I have seen this behaviour on the list with kernels that have been
compiled with gcc-2.96-rh. What compiler did you use.?
> So I wrote the attached program to search for non-empty files
> consisting entirely of null characters on XFS filesystems, which I'm
> posting in the hope that it will be useful for someone else.
>
> It revealed that my filesystem is pretty badly damaged (about 150
> files were hit), so I'll probably have to restore from backups and
> switch back to ext2 for now.
Have you tried running an xfs_repair -n on th filesystem to see what it
thinks of it.
> I'm running 2.4.6 from benh's tree on PowerPC.
I believe that the original report on PPC kernels were linus based.
> I did try an xfs_check on the filesystem, which reported no errors.
The extended attribute of the file is empty. That's why it is also giving
back NULLS. This happens during recovery IIRC. So it is not really corrupt
in the sense of the checker.
Did you see this after XFS recovery of the filesystem?
> Let me know if there's any more debugging information I can give; I
> really wish I could use XFS!
I don't know if there is something we can do about this except making EA
work. It would probably be moot point then. I am not sure if I am coorect
on this issue though.
Cheers
Seth
|