What were you doing when this happened? This comes from xfs_create() when xfs_dir_lookup() fails with ENOENT. I'll have to look more closely to see exactly what's going on... -Eric -- Eric Sandeen XF
I don't know, to be honest. Looks like it might have happened at boot-up, as the entries are intertwined with the network card and parallel port ones: parport0: assign_addrs: aa5500ff(38) xfs_create
OK, this is what I did, and it's repeatable: service single start service single stop initscripts-5.83-1 I emptied dmesg with the -c flag... but as soon as I go into single mode and exit it, I get t
I made today a fresh installation on one system (sgi XFS 1.0 install CD). I just tried the gcc-2.96-81 for kernel again. I got an "Unknown Error 990" and boot failed because /var/run was corrupted a
OK, installed compat-egcs (plus a host of other RPMs required), and tried going into single mode and exiting it again. No problems this time. It seems that if you go into single mode on a system com
I've had similar problems here. I have a Fujitsu 18Gig IDE drive that has two partitions on it (both XFS, one mounted ro and the other is my root partition) Anyway, I just updated to the latest cvs c
I was just about to post "edit your Makefile to use kgcc instead of gcc"... Recompiling the 2.4.4 XFS kernel with kgcc seems to have solved the fs corruption issues for me. -- Juha
Strange... Wish I could say the same here. I've also tried a couple of different Chipsets. The main location that the drive will be housed is using a Promise ATA66 PCI card controller, and I'm curren
Thanks you guys for working through this one, that code you managed to get into is for an old bug in xfs which was fixed years ago, you get into the create a new file path, but when you go try insert
That's what we've got in common -- the VIA chip set. Nothing but trouble with that, to be honest. Memory performance is slower than on 440BX chip sets (trying to work out how to tweak the PCI regist
Strange. I'm experiencing the same problem on a Promise PDC20262 controller card too! Another thing, is that I've never, well... mostly never ;) , experienced problems with other filesystems on eithe
Just wanted to chime in with a FWIW post :) I've also got a Promise PDC 20262 w/ an IBM Deskstar running in UDMA mode 4 w/ no problems whatsoever. Additionally a Maxtor Diamond Max connected to the
I've done a bit more work on this today, and now have a drive that doesn't seem to generate the errors I was having. The solution for me seemed to be enabling devfs support. I already had it compiled
Whoops ;) Wanted to make sure I had all of the details *GRIN* I was just worrying about the umounts on shutdown or reboot. Seems like the scripts are getting their information from /proc/mounts and
<a lot> Hm, not sure about the devfs thing, sure seems like it would not be related, but... I must admit that I have not yet really looked into this one. Ack! Nice catch, I guess we should fix that u