On 17/11/2015 22:08, Christopher Forgeron wrote:
I just submitted this as a bug:
( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204641 )
..but I thought I should bring it to the list's attention for more exposure
- If that's a no-no, let me know, as I have a few others that are related
t
Hi,
I have a HP DL380 G9, that I boot from an internal SmartArray Controller
provided RAID1 into FreeBSD 10.1 amd64.
I have upgraded the BIOS to the 2015-10 release and on reboot, I now get a
message that
/boot/loader.efi
can’t be found.
I can legacy boot it into mfsbsd and the file is ther
Sounds interesting. I'd love to see your results when you're ready to
share, or even the 'work in progress' if you want to share privately .
On Tue, Jan 13, 2015 at 6:30 PM, Garrett Wollman
wrote:
> I recently bought a copy of the SPECsfs2014 benchmark, and I've been
> using it to test out our
I just submitted this as a bug:
( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204641 )
..but I thought I should bring it to the list's attention for more exposure
- If that's a no-no, let me know, as I have a few others that are related
to this that I'd like to discuss.
- - - -
Consider
Op 17/11/15 om 17:15 schreef Steven Hartland:
>
>
> On 17/11/2015 15:26, Johan Hendriks wrote:
>> Hello all
>>
>> We have a NFS server witch has three network ports.
>>
>> We have bonded these interfaces as a lagg interface, but when we use the
>> server it looks like only two interfaces are used
On Tue, Nov 17, 2015 at 9:16 AM, Kurt Jaeger wrote:
> Hi!
>
>> > Is there something we can do to make sure lagg0 uses all the interfaces.
>>
>> Nope. LACP doesn't actively load balance its interfaces.
>
> On FreeBSD 11
>
> man lagg(4)
>
> says:
>
> The driver currently supports the aggreg
Hi!
> > Is there something we can do to make sure lagg0 uses all the interfaces.
>
> Nope. LACP doesn't actively load balance its interfaces.
On FreeBSD 11
man lagg(4)
says:
The driver currently supports the aggregation protocols failover (the
default), lacp, loadbalance, roundrobin,
On 17/11/2015 15:26, Johan Hendriks wrote:
Hello all
We have a NFS server witch has three network ports.
We have bonded these interfaces as a lagg interface, but when we use the
server it looks like only two interfaces are used.
This is our rc.conf file
ifconfig_igb0="up"
ifconfig_igb1="up"
On Tue, Nov 17, 2015 at 12:08 AM, Patrick M. Hausen wrote:
> Hi, all,
>
> > Am 16.11.2015 um 22:19 schrieb Freddie Cash :
> >
> > You label the disks as they are added to the system the first time.
> That
> > way, you always know where each disk is located, and you only deal with
> the
> > label
Hi!
> We have a NFS server witch has three network ports.
>
> We have bonded these interfaces as a lagg interface, but when we use the
> server it looks like only two interfaces are used.
>
> This is our rc.conf file
>
> ifconfig_igb0="up"
> ifconfig_igb1="up"
> ifconfig_igb2="up"
> cloned_inte
On Tue, Nov 17, 2015 at 8:26 AM, Johan Hendriks wrote:
> Is there something we can do to make sure lagg0 uses all the interfaces.
Nope. LACP doesn't actively load balance its interfaces. Each flow
gets assigned to a single interface based on a hash of the source and
destination MACs, IP addres
Hello all
We have a NFS server witch has three network ports.
We have bonded these interfaces as a lagg interface, but when we use the
server it looks like only two interfaces are used.
This is our rc.conf file
ifconfig_igb0="up"
ifconfig_igb1="up"
ifconfig_igb2="up"
cloned_interfaces="lagg0"
i
I disagree, get the remote hands to copy the serial number to an easily
visible location on the drive when its in the enclosure. Then label the
drives with the serial number (or a compatible version of it). That way the
label is tied to the drive, and you dont have to rely on the remote hands
100%.
It was a control thing again, if you were using a partition another
application could be using the drive on another partition, therefore zfs
couldn't guarantee exclusive use of the disk so had to be more careful in
the way it operated the drive. I think this meant I went into write through
mode lik
From what i remember its a control thing. If you have another layer below
zfs, be it software based or hardware based, zfs cant be sure what is going
on, therefore cant guarantee anything. This is quite a big thing when it
comes to data integrity which is a big reason to use zfs. I remember having
Patrick M. Hausen wrote on 11/17/2015 09:08:
Hi, all,
Am 16.11.2015 um 22:19 schrieb Freddie Cash :
You label the disks as they are added to the system the first time. That
way, you always know where each disk is located, and you only deal with the
labels.
we do the same for obvious reason
Hi, all,
> Am 16.11.2015 um 22:19 schrieb Freddie Cash :
>
> You label the disks as they are added to the system the first time. That
> way, you always know where each disk is located, and you only deal with the
> labels.
we do the same for obvious reasons. But I always wonder about the possib
17 matches
Mail list logo
