Re: block size problem ?
denis bonnenfant <[email protected]>
| Newsgroups | gmane.linux.enbd.general |
|---|---|
| Message-ID | <[email protected]> |
> What kernel is this? 2.6.12 with my patches. As i remenber there was a warning about ioctl during compiling of enbd_base.c maybe i need to investigate it further. > >Jul 7 18:05:18 se3 kernel: ENBD #824[105]: enbd_open DISK CHECK wanted in open >>on device nda >>Jul 7 18:05:18 se3 kernel: ENBD #4404[105]: enbd_media_changed MEDIA CHANGED called >>Jul 7 18:05:18 se3 kernel: ENBD #4410[105]: enbd_media_changed REMOTE CHECK >>done locally, no remote ioctl! > > > Well, again, you don't have the remote ioctls module loaded, I think. > > Well, you were right, enbd_ioctl was not loaded ! So maybe we have to change /etc/init.d/enbd script to allow it to be loaded ? here the syslog : Jul 8 14:13:58 se3 enbd-client: enbd-client: client says target 0 is ldap-croise:12345 Jul 8 14:13:58 se3 enbd-client: enbd-client: client identifier is A-1 Jul 8 14:13:58 se3 enbd-client: enbd-client: client channels is 4 Jul 8 14:13:58 se3 enbd-client: enbd-client: client cksum flag is 1 Jul 8 14:13:58 se3 enbd-client: enbd-client: client says blksize is 512 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) opened device /dev/nda Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) manager opened NBD device /dev/nda (2b00) Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) set kernel bdflush sync boundary to 80% from -1209666576% Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) left kernel bdflush async boundary at -1074079676% Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) manager detaches from shell Jul 8 14:13:58 se3 enbd-client: nbd/pidfile 28529: <# 144> lockpidfile returning err 0 for lock attempt Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) manager made pidfile /var/run/enbd-client-A-1.pid with pid 28529 Jul 8 14:13:58 se3 enbd-client: nbd/time 28529: <# 64> mygettimeofday time was 0+0E-6 s and is 1120824838+17447E-6 s Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) starts introduction sequence on ldap-croise:12345 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) got size 159966560256 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) got signature [A-1], had [] Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) negotiated blksize 512 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) negotiated pulse_intvl 10 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) got session port 12347 ok Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) introduction sequence ends ok Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) set device size 159966560256 Jul 8 14:13:58 se3 enbd-client: enbd-client 28529: <#1693> setdeviceblksize client (-1) Warning! kernel says blksz is 4096 != 512 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) set md5sum flags on device Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) sets session slots to 0-3 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) manager launched daemon 0 (28530) for ldap-croise:12347 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) manager launched daemon 1 (28531) for ldap-croise:12347 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) manager launched daemon 2 (28532) for ldap-croise:12347 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (-1) manager launched daemon 3 (28533) for ldap-croise:12347 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (3) opened device /dev/nda Jul 8 14:13:58 se3 enbd-client: enbd-client: client (0) opened device /dev/nda Jul 8 14:13:58 se3 enbd-client: enbd-client: client (3) opened socket 5 to ldap-croise:12347 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (0) opened socket 5 to ldap-croise:12347 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (1) opened device /dev/nda Jul 8 14:13:58 se3 enbd-client: enbd-client: client (2) opened device /dev/nda Jul 8 14:13:58 se3 enbd-client: enbd-client: client (1) opened socket 5 to ldap-croise:12347 Jul 8 14:13:58 se3 enbd-client: enbd-client: client (2) opened socket 5 to ldap-croise:12347 Jul 8 14:14:00 se3 enbd-client: enbd-client: client (3) read passwd ok from ldap-croise:12347 Jul 8 14:14:00 se3 enbd-client: enbd-client: client (3) got cliserv magic ok from ldap-croise:12347 Jul 8 14:14:00 se3 enbd-client: enbd-client: client (0) read passwd ok from ldap-croise:12347 Jul 8 14:14:00 se3 enbd-client: enbd-client: client (0) got cliserv magic ok from ldap-croise:12347 Jul 8 14:14:00 se3 enbd-client: enbd-client: client (3) got a signature ok from ldap-croise:12347 Jul 8 14:14:00 se3 enbd-client: enbd-client: client (3) begins main loop Jul 8 14:14:00 se3 enbd-client: enbd-client: client (0) got a signature ok from ldap-croise:12347 Jul 8 14:14:00 se3 enbd-client: enbd-client: client (0) begins main loop Jul 8 14:14:01 se3 enbd-client: enbd-client: client (1) read passwd ok from ldap-croise:12347 Jul 8 14:14:01 se3 enbd-client: enbd-client: client (1) got cliserv magic ok from ldap-croise:12347 Jul 8 14:14:01 se3 enbd-client: enbd-client: client (1) got a signature ok from ldap-croise:12347 Jul 8 14:14:01 se3 enbd-client: enbd-client: client (1) begins main loop Jul 8 14:14:01 se3 enbd-client: enbd-client: client (2) read passwd ok from ldap-croise:12347 Jul 8 14:14:01 se3 enbd-client: enbd-client: client (2) got cliserv magic ok from ldap-croise:12347 Jul 8 14:14:01 se3 enbd-client: enbd-client: client (2) got a signature ok from ldap-croise:12347 Jul 8 14:14:01 se3 enbd-client: enbd-client: client (2) begins main loop Jul 8 14:14:03 se3 enbd-client: enbd-client: client (-1) opened device /dev/nda It looks fine now ! mdadm is happy now...