Re: SIOCSIFMTU error when trying out jumbo frames

In comp.os.linux.networking Rahul <(E-Mail Removed)> wrote:
> I was trying to get jumbo frames working on my cluster. This is a privater
> LAN so end-to-end Jumbo frames support ought to be possible in theory.
>
> I tried:
>
> ifconfig eth0 mtu 9000
> SIOCSIFMTU: Invalid argument
> [root@node10 ~]# ifconfig eth1 mtu 9000
> SIOCSIFMTU: Invalid argument
> ifconfig bond0 mtu 9000
> SIOCSIFMTU: Invalid argument
>
> The server does have bonded GigE links. I see similar error messages
> documented by other users on the web but no real solution. Any ideas what I
> could be messing up?
>
You failed to mention what kernel and device you're using.
There's a known kernel bug like this for the e1000 driver setting
large MTU's.

Jerry

Jerry Peters <(E-Mail Removed)> wrote in news:ha5u6s$eue$1
@news.eternal-september.org:

> You failed to mention what kernel and device you're using.
> There's a known kernel bug like this for the e1000 driver setting
> large MTU's.
>
>

Sorry! Here's more info:

echo `uname -r`
2.6.18-92.el5

bond0 Link encap:Ethernet HWaddr [munged]
inet addr:10.0.0.100 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: [munged]/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:6119439311 errors:0 dropped:30212 overruns:0 frame:0
TX packets:5124928889 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5507970304794 (5.0 TiB) TX bytes:5356879814519 (4.8
TiB)

Any other device info that could help?


--
Rahul

Am Samstag, 3. Oktober 2009 18:44, Rahul a écrit :

> Jerry Peters <(E-Mail Removed)> wrote
>
>> You failed to mention what kernel and device you're using.
>> There's a known kernel bug like this for the e1000 driver
>> setting large MTU's.
>
> echo `uname -r`
> 2.6.18-92.el5

'hwinfo --netcard' shows the driver.

--
printf -v email $(echo \ 155 141 162 143 145 154 142 162 165 151 \
156 163 155 141 100 171 141 150 157 157 056 143 157 155|tr \ \\\\)
# Live every life as if it were your last! #