> I should add that error 990 is EFSCORRUPTED which usually means XFS has
> detected a metadata problem on the disk and has shut it down. There should
> have been a console message when this started, I did not see one in the
> output Mathew sent.
> The xfs_create looping error should not be happening either, this is another
> inconsistency between metadata in different locations - a lookup on a
> directory is failing to find an entry in a directory, but the create code
> says it is there.
> At this point I would distrust the hardware, Simon's suggestion would be
> a good one.
I think it's a bug with XFS and kickstart. I've been playing around with it
extensively and have come across it. If you do a xfsrepair on the partition,
it looks clean and then you can mount it without a problem.
All that said, I've been changing and tweaking my kickstart script lots
over the last two weeks and somewhere along the way the problem went
away. Try changing your partitions as defined in the kickstart file. For
grins, try these and see if the problem reappears:
part / --size 350 --onprimary=1
part swap --size 256
part /usr --size 1000 --grow
part /kickstart --size 2000
(I think I gave up trying to create a separate /var partition at this point).
It's not always the /var partition though, since in one of the iterations of
it had the problem on the /kickstart partition.
Remember when I first wrote in on the bug about not being able to create
a /usr/local/net partition (it's been fixed in an update file just fine, but
I don't have time to patch my current install) and I wrote I had similar
with my /boot partition? I never got back to you, but it was this problem. It
turned out to be a dissimilar problem to the /usr/local/net one, but a
lemme know how it goes. I'm quite certain it's not your hardware