Dear list,
as far as this is a public available ML my name is Gerd, not John ;-)
My system has a vanilla 2.4.19 kernel with the appropriate patch patched in
without probs. Kernel compilation using gcc 2.95-2 was problemless, as it was
often before. The last kernel I used for a longer time without probs was
2.4.16. I always compile XFS as a module, without any debugging.
I have 3 partitions type xfs: extra, xfs, depot. All 3 have been accessible
with 2.4.19 without probs for one or two weeks or so, now 2 seem to be
corrupt. They are mountable, I can see it's content, but when a want to copy a
file
or create a new one say with touch, this session hangs, I could only kill
the window (a kill -9 to the touch or cp or a ctrl-c does not work).
My system is a single processor, all hardware is the same as with 2.4.16,
disks are SCSI with a Tekram hostadapter, no LVM, no RAID. This is my first
problem regarding XFS since 1.0.0. I have seen no message in /var/log/messages
or elsewhere.
After reading the FAQ and some browsing in the ML archive I decided to do
whats written in the FAQ, to send a mail to the ML ;-)
I also decided to update to the recent xfsprogs 2.0.3 from the ftp server
this evening and to give xfs_repair a try. I cannot imagine what has happened
to the xfs partitions, in my view it seems related to the update to the
2.4.19, but going back to the painless 2.4.16 didn't help. In the moment I read
in
the FAQ that gcc 2.95-2 should not be used, may be I should update to 2.95-3,
what's recommended in the FAQ
Any further suggestions ?
-Gerd
--
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
|