Re: another 2TB issue in 2.4.33pre

Am Mittwoch, 28. Juni 2006 20:40 schrieb Peter T. Breuer:
> > enbd-client  7356: #2511 setkernelnbd: Failed set size 1229375668224 on
> > fd 4: File too large
>
> Aha. My bad. The routine which receives the result puts it in an int
> which it then checks for sign. Goodness gracious.
>
> It would be better to have the setdevicesize routine return just "0". I
> can't see anywhere it needs the number of sectors as a result.

[changes]

I have made the changes, and now it works:

enbd-client 11624: client (-1) got signature [storage3], had []
enbd-client 11624: client (-1) negotiated blksize 512
enbd-client 11624: client (-1) negotiated pulse_intvl 10
enbd-client 11624: client (-1) got session port 1037 ok
enbd-client 11624: client (-1) introduction sequence ends ok
enbd-client 11624: client (-1) trying sig <storage3>
enbd-client 11624: client (-1) set sig or passed sigchk OK
enbd-client 11624: client (-1) will set size 1229375668224
enbd-client 11624: BLKGETSIZE failed
enbd-client 11624: sending ENBD_SET_SECTORS64 2401124352
enbd-client 11624: ENBD_SET_SECTORS64 succeeded
enbd-client 11624: client (-1) set device size 1229375668224
enbd-client 11624: client (-1) will set blksize 512
enbd-client 11624: client (-1) Warning! changing device blksz from 1024 to 512
enbd-client 11624: client (-1) set blksize 512
enbd-client 11624: client (-1) set device ro flag 0
enbd-client 11624: client (-1) set md5sum flags on device
enbd-client 11624: client (-1) set device md5sum flag 8000
enbd-client 11624: client (-1) set device req timeout 10
enbd-client 11624: client (-1) set device show_errs flag 0
enbd-client 11624: client (-1) set device buffer_writes flag 0
enbd-client 11624: client (-1) sets session slots to 0-1
enbd-client 11624: client (-1) launched daemon 0 (11629) for storage3:1037
enbd-client 11624: client (-1) launched daemon 1 (11630) for storage3:1037
enbd-client 11630: client (1) opened device /dev/nde

I could mount an access the device! Thx a lot.

Regards,
Flo