-----BEGIN PGP SIGNED MESSAGE-----
Raphael Bauduin schrieb:
From what I read on the web, this could be due to a suboptimal cable,
but could it be the cause of the XFS problems? I don't get these
could you use a better cable and see, if the PCI errors go away?
also check earlier logs again, *maybe* the PCI errors appeared way
before the fs took note.
If I have the possibility I'll do it. But those PCI errors only once per boot.
When it's running I don't get any of these errors. That seems to indicate that
driver has adapted its working to the controller, and that it's doing fine
I've looked at older logs and those messages appeared at a boot of 3 december,
also followed by this:
Dec 3 10:18:19 dotnet kernel: Starting XFS recovery on filesystem: sd(8,38)
Dec 3 10:18:19 dotnet kernel: Ending XFS recovery on filesystem: sd(8,38)
What's the exact meaning of these messages? Does it mean the partition was not
If the partition is not cleanly unmounted at each boot, could it result in a
partition error like I had?
- the kernel upgrade?
do you have "working kernels" left? are they running still fine?
Once the problem occured with the 2.4.26, it also accured when booting in 2.4.20
PS: I Think I followed the procedure to subscribe, but I don't get any mails of
the mailing list.
If you answer, please send it to me directly also.
- xfs only?
if you have spare diskspace you could try other filesystems and see, if
the errors are the same. but first i'd really care about these PCI errors...
BOFH excuse #30:
positron router malfunction
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----