Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Am running a "cat /var/log/messages" command and see the following over and over (below is an extract):
Jan 30 21:59:01 DNS-323 user.warn kernel: md: mdadm(pid 27923) used obsolete MD ioctl, upgrade your software to use new ictls.
Jan 30 22:05:05 DNS-323 user.warn kernel: md: mdadm(pid 28113) used obsolete MD ioctl, upgrade your software to use new ictls.
Jan 30 22:15:06 DNS-323 user.warn kernel: md: mdadm(pid 28372) used obsolete MD ioctl, upgrade your software to use new ictls.
Jan 30 22:25:09 DNS-323 user.warn kernel: md: mdadm(pid 28636) used obsolete MD ioctl, upgrade your software to use new ictls.
What does it mean and how do I fix it?
Am on 1.05 and funplug 0.5 running on USB....
Thanks
Tony
Offline
It means that mdadm (the software which is responsible for maintaining the raid array) is using an obsolete kernelfunction. Nothing to be worried about, it just works. This function is still available, but could be removed in future kernels, that's why you get the warning.
Offline
Mijzelf wrote:
It means that mdadm (the software which is responsible for maintaining the raid array) is using an obsolete kernelfunction. Nothing to be worried about, it just works. This function is still available, but could be removed in future kernels, that's why you get the warning.
Thanks for the reply. I got concerned because I had not seen it before ie I don't think I used to get it......
Offline
Did you change the log level of your syslog? This could explain why you didn't see the message before.
Offline
silversurfer wrote:
Did you change the log level of your syslog? This could explain why you didn't see the message before.
Not for a while..... changed it to 5 in July last year....... maybe I just didn't notice before (but there are rather a lot of them)
Offline
I have had "md: mdadm(pid 2593) used obsolete MD ioctl, upgrade your software to use new ictls." in dmesg forever, the dns323 works fine though
Offline
OK, thanks. Won't worry about it anymore......
Offline
silversurfer wrote:
Did you change the log level of your syslog? This could explain why you didn't see the message before.
How does one change the log level of syslog?
Offline
KyleK wrote:
silversurfer wrote:
Did you change the log level of your syslog? This could explain why you didn't see the message before.
How does one change the log level of syslog?
See here:
http://dns323.kood.org/forum/t2632-DNS- … vity-time-(without-doing-anything).html
Offline