Bug still on 2.4.10?
This is on 2.4.8 but I get the funny feeling this maybe hasn't been fixed yet for 2.4.10:
Sep 11 06:58:08 yeti kernel: md: fsck.ext3(pid 151) used obsolete MD
ioctl(4717), upgrade your software to use new ictls. I'm runing:
Parallelizing fsck version 1.23 (15-Aug-2001) Unless maybe I just need to recompile it???
Here's a previous reference I found from Jan 2001.
http://oss.sgi.com/projects/xfs/mail_archive/0101/msg00185.html
________________________________________
Michael D. Black Principal Engineer
[email protected] 321-676-2923,x203
http://www.csihq.com Computer Science Innovations
http://www.csihq.com/~mike My home page FAX 321-676-2355
Quoted 9 lines · Mike Black
This is on 2.4.8 but I get the funny feeling this maybe hasn't been fixed yet for 2.4.10:
Sep 11 06:58:08 yeti kernel: md: fsck.ext3(pid 151) used obsolete MDioctl(4717), upgrade your software to use new ictls. I'm runing:
Parallelizing fsck version 1.23 (15-Aug-2001) Unless maybe I just need to recompile it???
Upgrade to 1.24 or downgrade to 1.22; 1.23 uses the wrong ioctl for some operations....
Quoted 5 lines
This is on 2.4.8 but I get the funny feeling this maybe hasn't been fixed yet for 2.4.10:
Sep 11 06:58:08 yeti kernel: md: fsck.ext3(pid 151) used obsolete MDioctl(4717), upgrade your software to use new ictls.
This isnt a kernel bug.
Quoted 3 lines
I'm runing:
Parallelizing fsck version 1.23 (15-Aug-2001)
Unless maybe I just need to recompile it???
Back down to 1.22