On Tue, 02 Jun 2009 12:15:34 +0100, Tom Brown <tom(a)ng23.net> wrote:
> It's certainly not normal, and could be indicative of some
other problem
> going on. Setting the max bonds is not critical to make bonding work,
> but
> you should google that error and figure out why it's saying permission
> denied, other things could be silently failing.
>
>
i hve googled it to death it seems and so far i cant find an answer -
the box is just a vanilla CentOS 5.3 with 4 nics into 2 bonds all done
with cobbler so i dont really see why this would be happening.
will keep looking though
Yeah no luck here either. I didn't think permissions on sysfs were
persistent across reboots, but you could try chmod'ing that directory and
file, and see if you can access it after the system boots up.
Also, one of the few things I found was that the initscripts don't like
when max_bonds is set to 0, so check your modprobe.conf for that.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.