OVH Community, your new community space.

mdadm: sending ioctl 1261 to a partition!


Spacedust
29-12-2012, 15:35
W kernelu 3.0.56 naprawili to w końcu: http://www.kernel.org/pub/linux/kern...angeLog-3.0.56. W 3.2.24 też jest, także OVH mogłoby uaktualnić swoje kernele, aby zapobiec pytaniom co to jest

Linux 3.0.56

commit 90123275293f831d36dfd1fcfc78afa6c3563f0b
Author: Jan Kara
Date: Fri Jun 15 12:52:46 2012 +0200

scsi: Silence unnecessary warnings about ioctl to partition

commit 6d9359280753d2955f86d6411047516a9431eb51 upstream.

Sometimes, warnings about ioctls to partition happen often enough that they
form majority of the warnings in the kernel log and users complain. In some
cases warnings are about ioctls such as SG_IO so it's not good to get rid of
the warnings completely as they can ease debugging of userspace problems
when ioctl is refused.

Since I have seen warnings from lots of commands, including some proprietary
userspace applications, I don't think disallowing the ioctls for processes
with CAP_SYS_RAWIO will happen in the near future if ever. So lets just
stop warning for processes with CAP_SYS_RAWIO for which ioctl is allowed.

Acked-by: Paolo Bonzini
CC: James Bottomley
CC: linux-scsi@vger.kernel.org
Signed-off-by: Jan Kara
Signed-off-by: Jens Axboe
Cc: Satoru Takeuchi
Signed-off-by: Greg Kroah-Hartman
http://www.kernel.org/pub/linux/kern...angeLog-3.2.24

commit f45c9a6eec20cd712421c442785e7a4e9215a230
Author: Jan Kara
Date: Fri Jun 15 12:52:46 2012 +0200

scsi: Silence unnecessary warnings about ioctl to partition

commit 6d9359280753d2955f86d6411047516a9431eb51 upstream.

Sometimes, warnings about ioctls to partition happen often enough that they
form majority of the warnings in the kernel log and users complain. In some
cases warnings are about ioctls such as SG_IO so it's not good to get rid of
the warnings completely as they can ease debugging of userspace problems
when ioctl is refused.

Since I have seen warnings from lots of commands, including some proprietary
userspace applications, I don't think disallowing the ioctls for processes
with CAP_SYS_RAWIO will happen in the near future if ever. So lets just
stop warning for processes with CAP_SYS_RAWIO for which ioctl is allowed.

CC: Paolo Bonzini
CC: James Bottomley
CC: linux-scsi@vger.kernel.org
Acked-by: Paolo Bonzini
Signed-off-by: Jan Kara
Signed-off-by: Jens Axboe
[bwh: Backported to 3.2: use ENOTTY, not ENOIOCTLCMD]
Signed-off-by: Ben Hutchings

WMP
03-11-2012, 10:15
Ja mam na własnym jajku, myśle że jest to problem z konfiguracją mdraid tworzoną podczas instalacji serwera przez ovh. Tylko boję się ruszać na produkcyjnym serwerze...

mario1973
03-11-2012, 09:55
Macie to też na własnych kompilacjach ? Czy tylko na OVH ? Bo mnie to też denerwuje.

M

WMP
03-11-2012, 09:16
Poradziłeś sobie z tym jakoś?

zort
05-08-2012, 22:36
Też to mam po zmianie jajka na 3.2

Wg nich: http://comments.gmane.org/gmane.linux.raid/37327 to niegroźne,

(...)
1261 is flush-bufs
(...)

Spacedust
24-06-2012, 22:35
Na serwerze w BHS mam takie coś w dmesg:

mdadm: sending ioctl 1261 to a partition!
kernel: 3.2.13-xxxx-std-ipv6-64

Myślałem, że była to wina grsec, ale po zmianie na zwykłe jądro jest to samo.