freebsd-stable Digest, Vol 349, Issue 4
freebsd-sta...@freebsd.org
freebsd...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-sta...@freebsd.org
You can reach the person managing the list at
freebsd-st...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-stable digest..."
Today's Topics:
1. Firefox 3.6.X and Thunderbird 3.0.X crashing with Radeon
graphics on FBSD 8.0-STABLE SMP/sm64 box (O. Hartmann)
2. Re: Firefox 3.6.X and Thunderbird 3.0.X crashing with Radeon
graphics on FBSD 8.0-STABLE SMP/sm64 box (Gary Jennejohn)
3. Multi node storage, ZFS (Michal)
4. Re: Multi node storage, ZFS (Vincent Hoffman)
5. Re: Multi node storage, ZFS (Boris Kochergin)
6. Re: Multi node storage, ZFS (Freddie Cash)
7. Re: Multi node storage, ZFS (Michael Loftis)
8. Re: Multi node storage, ZFS (Michal)
9. Re: Multi node storage, ZFS (Freddie Cash)
10. Re: Multi node storage, ZFS (Michael Loftis)
11. Re: Multi node storage, ZFS (Freddie Cash)
12. Re: Multi node storage, ZFS (Michal)
13. Re: Powerd and est / eist functionality (John Long)
14. Re: Powerd and est / eist functionality (John Long)
15. Re: Powerd and est / eist functionality (Jeremy Chadwick)
16. Re: Can't boot after make installworld (Krzysztof Dajka)
17. Re: Multi node storage, ZFS (Ivan Voras)
18. Re: Multi node storage, ZFS (Miroslav Lachman)
19. Re: Multi node storage, ZFS (Michal)
20. Re: Firefox 3.6.X and Thunderbird 3.0.X crashing with Radeon
graphics on FBSD 8.0-STABLE SMP/sm64 box (O. Hartmann)
21. Re: Multi node storage, ZFS (Ben Morrow)
22. Re: Powerd and est / eist functionality (John Long)
23. Re: Powerd and est / eist functionality (Matthew D. Fuller)
----------------------------------------------------------------------
Message: 1
Date: Wed, 24 Mar 2010 13:32:40 +0000
From: "O. Hartmann" <ohar...@zedat.fu-berlin.de>
Subject: Firefox 3.6.X and Thunderbird 3.0.X crashing with Radeon
graphics on FBSD 8.0-STABLE SMP/sm64 box
To: freebsd...@freebsd.org, freebs...@freebsd.org,
freebsd-...@freebsd.org
Message-ID: <4BAA1478...@zedat.fu-berlin.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Since the introduction of Thunderbird 3.0 and Firefox 3.6 I see
spontanous crashes/coredumps of both thunderbird and firefox. Interingly
Firefox 3.5.X works well on he same platform.
The platform is a FreeBSD 8.0-STABLE/amd64 (r205536: Tue Mar 23 22:19:04
CET 2010), SMP box with 8GB of RAM, QuadCore Intel Q6600 on a P35-based
motherboard.
Thunderbird 3 crashes rarely compared to Firefox 3. The longer the
application thunderbird runs, the higher the likelyhood the app crashes
and vanishes. Sometimes this happens immediately after starting
thunderbird, sometimes it takes its few minutes or half an hour.
Firefox 3 is sensitive to its pull-down menus or requester showing up in
some situations. I can provoke a crash by clicking onto a pull-down-menu
in firefox 3, it immediately dumps a core.
Well, I wouldn't write s cross-posting if I would be sure this behaviour
is due to some oddities in my installation, but since this odd behaviour
occured both on Firefox 3.6 and Thunderbird 3 in several situations and
with several tries to get a workaround, I feel desperately lost.
What I did so far:
- Recompiling EVERY port on my box (four times in a row to make sure
everything is right, its a pain with nearly 950 ports).
- Deinstalling both Firefox 3 and Thunderbird 3 and installing the
binary packages from FreeBSD.ORG
I have a private UP box, running the same OS FreeBSD 8.0-STABLE/amd64 on
a single core Athlon 3500+ with only 2GB of RAM. There I use both
Thunderbird 3.0.3 and Firefox 3.6.2 without any problem.
I suspect the X11 server or some part of the accelerator stuff
triggering the crashes. On the both machines,
WITHOUT_NOUVEAU = YES
is defined. On the UP box at home, I utilise a HD4830 graphics
accelerator with DR enabled. The lab's box have had
both HD4670 and now HD4770 accelerators, both do not work properly with
the state-of-the-art drivers supported by the official pots collection.
HD4670 never got to work since the new RadeonHD driver 1.3 was
introduced (prior to that it worked), the new HD4770 works with
explicitely disabling DRI and crashes whenever I leave a session (quit
windowmaker). Well, this is another story, but I suspect the Radeon
driver infrastructure causing the problems - but I'm not sure.
I use perl-threaded 5.10, but I guess this is not a problem since the
problems occur whether I have threaded perl or not.
As I said, I feel like a dead man in the water ...
Regards,
Oliver
------------------------------
Message: 2
Date: Wed, 24 Mar 2010 15:06:53 +0100
From: Gary Jennejohn <gary.je...@freenet.de>
Subject: Re: Firefox 3.6.X and Thunderbird 3.0.X crashing with Radeon
graphics on FBSD 8.0-STABLE SMP/sm64 box
To: "O. Hartmann" <ohar...@zedat.fu-berlin.de>
Cc: freebsd...@freebsd.org, freebsd-...@freebsd.org,
freebs...@freebsd.org
Message-ID: <20100324150...@ernst.jennejohn.org>
Content-Type: text/plain; charset=US-ASCII
On Wed, 24 Mar 2010 13:32:40 +0000
"O. Hartmann" <ohar...@zedat.fu-berlin.de> wrote:
> Since the introduction of Thunderbird 3.0 and Firefox 3.6 I see
> spontanous crashes/coredumps of both thunderbird and firefox. Interingly
> Firefox 3.5.X works well on he same platform.
>
> The platform is a FreeBSD 8.0-STABLE/amd64 (r205536: Tue Mar 23 22:19:04
> CET 2010), SMP box with 8GB of RAM, QuadCore Intel Q6600 on a P35-based
> motherboard.
>
> Thunderbird 3 crashes rarely compared to Firefox 3. The longer the
> application thunderbird runs, the higher the likelyhood the app crashes
> and vanishes. Sometimes this happens immediately after starting
> thunderbird, sometimes it takes its few minutes or half an hour.
>
> Firefox 3 is sensitive to its pull-down menus or requester showing up in
> some situations. I can provoke a crash by clicking onto a pull-down-menu
> in firefox 3, it immediately dumps a core.
>
If you suspect the graphics card's driver is at fault then I would try
linux-opera or even linux-firefox and see whether it also dies when you
use a drop-down menu.
Another possibility would be to set hw.physmem to say 3G or 4G in
loader.conf and see whether that affects thunderbird/firefox. Who
knows, there may some weird problem caused by all that memory? That
would a fairly quick and cheap way to test this.
--
Gary Jennejohn
------------------------------
Message: 3
Date: Wed, 24 Mar 2010 15:47:21 +0000
From: Michal <mic...@ionic.co.uk>
Subject: Multi node storage, ZFS
To: freebsd...@freebsd.org
Message-ID: <4BAA3409...@ionic.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
I wrote a really long e-mail but realised I could ask this question far
far easier, if it doesn't make sense, the original e-mail is bellow
Can I use ZFS to create a multinode storage area. Multiple HDD's in
Multiple servers to create one target of, for example, //officestorage
Allowing me to expand the storage space when needed and clients being
able to retrieve data (like RAID0 but over devices not HDD)
Here is an example I found which is where I'm getting some ideas from
http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
Any pointers would be helpful,
Thanks
---------------------------------------------------------------------
I've been searching around and I am finding myself confused and reading
conflicting information. I would like to build a Storage system where by
I have multiple nodes. At the minute I have a number or NAS's which work
well and RAID6 works well in the situation we have, but unfortunately
it's a short-term solution I inherited and once you crunch the numbers
of 6 devices with 6 HDD's in RAID6 you realise how much space you have
wasted then say, 1 device of RAID6 with 36 HDD's (the saving is a fair
few TB)
There are other issues as well, increasing the size, 3rd party NAS
device features missing which other storage devices have...etc so I
looked around and my grand idea was basically this;
"Build a system where I can have multiple nodes which create one target
(we will use //officestorage for our example) as opposed to //nas1/
which is of course 1 device. Using multiple nodes will allow us to add a
new device, thus increasing the space available but the target will
always be the same and to the client nothing has change (other then
available space) (Think of this as RAID0). Multiple nodes will also
allow for redundancy across devices (think RAID1) and give better IO as
it's multiple devices and not just 1 device. I could have devices in
different locations so a whole building could burn down and still not
lose the data"
After looking around I found this
https://help.ubuntu.com/community/HighlyAvailableAoETarget
Which looks quite good, it's basically RAID1 but instead of HDD's it's
across servers, I've used DRBD and it worked well, but this doesn't give
me better IO as only 1 device is live.
I then found this
http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
Which looks fantastic, though I will need a master server to create the
RAID0 and RAID1 across the multiple nodes and then share this out, which
is ok but I would need a hot swap master server, so I'm looking at two
of those. I then started thinking about ZFS, I've heard lots of good
things about it in the past and thinking can ZFS do what I want. I have
read some things which say it can do what that 2nd link does and others
which say it can't. Everything I come across is about using just 1
device and I could build 1 device with DRBD, but that doesn't help, nor
will it allow me to expand it (if your server runs out of physical space
you can't add more HDD's.
Anyone point me in the right direction??
Thanks
------------------------------
Message: 4
Date: Wed, 24 Mar 2010 16:11:38 +0000
From: Vincent Hoffman <vi...@unsane.co.uk>
Subject: Re: Multi node storage, ZFS
To: freebsd...@freebsd.org
Message-ID: <4BAA39BA...@unsane.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
On 24/03/2010 15:47, Michal wrote:
> I wrote a really long e-mail but realised I could ask this question far
> far easier, if it doesn't make sense, the original e-mail is bellow
>
> Can I use ZFS to create a multinode storage area. Multiple HDD's in
> Multiple servers to create one target of, for example, //officestorage
> Allowing me to expand the storage space when needed and clients being
> able to retrieve data (like RAID0 but over devices not HDD)
>
At least in theory you could use geom_gate and zfs I suppose, never
tried it though.
ggatec(8), ggated(8) are your friends for that.
Vince
> Here is an example I found which is where I'm getting some ideas from
> http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
>
> Any pointers would be helpful,
> Thanks
>
>
> ---------------------------------------------------------------------
>
>
> I've been searching around and I am finding myself confused and reading
> conflicting information. I would like to build a Storage system where by
> I have multiple nodes. At the minute I have a number or NAS's which work
> well and RAID6 works well in the situation we have, but unfortunately
> it's a short-term solution I inherited and once you crunch the numbers
> of 6 devices with 6 HDD's in RAID6 you realise how much space you have
> wasted then say, 1 device of RAID6 with 36 HDD's (the saving is a fair
> few TB)
>
> There are other issues as well, increasing the size, 3rd party NAS
> device features missing which other storage devices have...etc so I
> looked around and my grand idea was basically this;
>
> "Build a system where I can have multiple nodes which create one target
> (we will use //officestorage for our example) as opposed to //nas1/
> which is of course 1 device. Using multiple nodes will allow us to add a
> new device, thus increasing the space available but the target will
> always be the same and to the client nothing has change (other then
> available space) (Think of this as RAID0). Multiple nodes will also
> allow for redundancy across devices (think RAID1) and give better IO as
> it's multiple devices and not just 1 device. I could have devices in
> different locations so a whole building could burn down and still not
> lose the data"
>
>
> After looking around I found this
>
> https://help.ubuntu.com/community/HighlyAvailableAoETarget
>
> Which looks quite good, it's basically RAID1 but instead of HDD's it's
> across servers, I've used DRBD and it worked well, but this doesn't give
> me better IO as only 1 device is live.
>
> I then found this
>
> http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
>
> Which looks fantastic, though I will need a master server to create the
> RAID0 and RAID1 across the multiple nodes and then share this out, which
> is ok but I would need a hot swap master server, so I'm looking at two
> of those. I then started thinking about ZFS, I've heard lots of good
> things about it in the past and thinking can ZFS do what I want. I have
> read some things which say it can do what that 2nd link does and others
> which say it can't. Everything I come across is about using just 1
> device and I could build 1 device with DRBD, but that doesn't help, nor
> will it allow me to expand it (if your server runs out of physical space
> you can't add more HDD's.
>
> Anyone point me in the right direction??
>
> Thanks
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
>
------------------------------
Message: 5
Date: Wed, 24 Mar 2010 12:14:52 -0400
From: Boris Kochergin <sp...@acm.poly.edu>
Subject: Re: Multi node storage, ZFS
To: Vincent Hoffman <vi...@unsane.co.uk>, FreeBSD-STABLE Mailing List
<freebsd...@freebsd.org>
Message-ID: <4BAA3A7C...@acm.poly.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Vincent Hoffman wrote:
> On 24/03/2010 15:47, Michal wrote:
>
>> I wrote a really long e-mail but realised I could ask this question far
>> far easier, if it doesn't make sense, the original e-mail is bellow
>>
>> Can I use ZFS to create a multinode storage area. Multiple HDD's in
>> Multiple servers to create one target of, for example, //officestorage
>> Allowing me to expand the storage space when needed and clients being
>> able to retrieve data (like RAID0 but over devices not HDD)
>>
>>
> At least in theory you could use geom_gate and zfs I suppose, never
> tried it though.
> ggatec(8), ggated(8) are your friends for that.
>
>
> Vince
Indeed, you can. I've done it. As for failover, you could run the
recently-committed HAST code on primary and backup central machines.
Upon failure of the primary central machine, the backup one would take
its IP address, mount the ZFS filesystem over the network, do whatever
other userspace things may be necessary, and resume servicing I/O.
-Boris
------------------------------
Message: 6
Date: Wed, 24 Mar 2010 09:20:28 -0700
From: Freddie Cash <fjw...@gmail.com>
Subject: Re: Multi node storage, ZFS
To: freebsd...@freebsd.org
Message-ID:
<b269bc571003240920r3c0...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Wed, Mar 24, 2010 at 8:47 AM, Michal <mic...@ionic.co.uk> wrote:
> I wrote a really long e-mail but realised I could ask this question far
> far easier, if it doesn't make sense, the original e-mail is bellow
>
> Can I use ZFS to create a multinode storage area. Multiple HDD's in
> Multiple servers to create one target of, for example, //officestorage
> Allowing me to expand the storage space when needed and clients being
> able to retrieve data (like RAID0 but over devices not HDD)
>
> Here is an example I found which is where I'm getting some ideas from
> http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
>
> Horribly, horribly, horribly complex. But, then, that's the Linux world.
:)
Server 1: bunch of disks exported via iSCSI
Server 2: bunch of disks exported via iSCSI
Server 3: bunch of disks exported via iSCSI
"SAN" box: uses all those iSCSI exports to create a ZFS pool
Use 1 iSCSI export from each server to create a raidz vdev. Or multiple
mirror vdevs. When you need more storage, just add another server full of
disks, export them via iSCSI to the "SAN" box, and expand the ZFS pool.
And, if you need fail-over, on your "SAN" box, you can use HAST at the lower
layers (currently only available in 9-CURRENT) to mirror the storage across
two systems, and use CARP to provide a single IP for the two boxes.
---------------------------------------------------------------------
> I've been searching around and I am finding myself confused and reading
> conflicting information. I would like to build a Storage system where by
> I have multiple nodes. At the minute I have a number or NAS's which work
> well and RAID6 works well in the situation we have, but unfortunately
> it's a short-term solution I inherited and once you crunch the numbers
> of 6 devices with 6 HDD's in RAID6 you realise how much space you have
> wasted then say, 1 device of RAID6 with 36 HDD's (the saving is a fair
> few TB)
>
> Yes, you save space, but your throughput will be horribly horribly horribly
low. RAID arrays should be narrow (1-9 disks), not wide (30+ disks), and
then combined into a larger array (multiple small RAID6 arrays joined into a
RAID0 stripe).
--
Freddie Cash
fjw...@gmail.com
------------------------------
Message: 7
Date: Wed, 24 Mar 2010 11:04:36 -0600
From: Michael Loftis <mlo...@wgops.com>
Subject: Re: Multi node storage, ZFS
To: freebsd...@freebsd.org
Message-ID: <C901C61A8023D94FD0DFBF27@[192.168.1.44]>
Content-Type: text/plain; charset=us-ascii; format=flowed
--On Wednesday, March 24, 2010 9:20 AM -0700 Freddie Cash
<fjw...@gmail.com> wrote:
> On Wed, Mar 24, 2010 at 8:47 AM, Michal <mic...@ionic.co.uk> wrote:
>
>> I wrote a really long e-mail but realised I could ask this question far
>> far easier, if it doesn't make sense, the original e-mail is bellow
>>
>> Can I use ZFS to create a multinode storage area. Multiple HDD's in
>> Multiple servers to create one target of, for example, //officestorage
>> Allowing me to expand the storage space when needed and clients being
>> able to retrieve data (like RAID0 but over devices not HDD)
>>
>> Here is an example I found which is where I'm getting some ideas from
>> http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
>>
>> Horribly, horribly, horribly complex. But, then, that's the Linux world.
> :)
>
> Server 1: bunch of disks exported via iSCSI
> Server 2: bunch of disks exported via iSCSI
> Server 3: bunch of disks exported via iSCSI
>
> "SAN" box: uses all those iSCSI exports to create a ZFS pool
>
> Use 1 iSCSI export from each server to create a raidz vdev. Or multiple
> mirror vdevs. When you need more storage, just add another server full of
> disks, export them via iSCSI to the "SAN" box, and expand the ZFS pool.
>
> And, if you need fail-over, on your "SAN" box, you can use HAST at the
> lower layers (currently only available in 9-CURRENT) to mirror the
> storage across two systems, and use CARP to provide a single IP for the
> two boxes.
If you were to do something like this, I'd make sure to have a fast local
ZIL (log) device on the head node. That would reduce latency for writes,
you might also do the same for reads. Then your bulk storage comes from
the iSCSI boxes.
Just a thought.
------------------------------
Message: 8
Date: Wed, 24 Mar 2010 17:12:50 +0000
From: Michal <mic...@ionic.co.uk>
Subject: Re: Multi node storage, ZFS
To: freebsd...@freebsd.org
Message-ID: <4BAA4812...@ionic.co.uk>
Content-Type: text/plain; charset=UTF-8
On 24/03/2010 16:20, Freddie Cash wrote:
Horribly, horribly, horribly complex. But, then, that's the Linux world.
> :)
Yes I know, it's not very clean, but was trying to gather ideas and I
found that
>
> Server 1: bunch of disks exported via iSCSI
> Server 2: bunch of disks exported via iSCSI
> Server 3: bunch of disks exported via iSCSI
>
> "SAN" box: uses all those iSCSI exports to create a ZFS pool
>
> Use 1 iSCSI export from each server to create a raidz vdev. Or multiple
> mirror vdevs. When you need more storage, just add another server full of
> disks, export them via iSCSI to the "SAN" box, and expand the ZFS pool.
>
> And, if you need fail-over, on your "SAN" box, you can use HAST at the lower
> layers (currently only available in 9-CURRENT) to mirror the storage across
> two systems, and use CARP to provide a single IP for the two boxes.
>
> ---------------------------------------------------------------------
This is pretty much what I have been looking for, I don't mind using a
SAN Controller server in which to deal with all of this in fact I
expected that, but I wanted to present the disks from a server full of
HDD's (which in effect is just a storage device) and then join them up.
I've briefly looked over RAIDz, will give it a good reading over later.
I'm thinking 6 disks in each server, and two raidz vdev created from 3
disks in each server. I can them serve them to the network. I've never
used ISCSI on FreeBSD however, I played with AOE on different *nix's so
I will give ISCSI a good looking over.
> Yes, you save space, but your throughput will be horribly horribly horribly
> low. RAID arrays should be narrow (1-9 disks), not wide (30+ disks), and
> then combined into a larger array (multiple small RAID6 arrays joined into a
> RAID0 stripe).
Oh Yes I agree, was doing some very crude calculations and the
difference in space was quite a lot, but no I would never do that in
reality
> If you were to do something like this, I'd make sure to have a fast
>local ZIL (log) device on the head node. That would reduce latency
>for writes, you might also do the same for reads. Then your bulk
>storage comes from the iSCSI boxes.
>
>Just a thought.
I've not come across ZIL so I think I will have to do my research
>At least in theory you could use geom_gate and zfs I suppose, never
>tried it though.
>ggatec(8), ggated(8) are your friends for that.
>
>Vince
Just had a look at ggatec, I've not seen or heard of that so I will
continue looking through that.
Many thanks to all, if I get something solid working I will be sure to
update the list with what will hopefully be a very cheap (other then
HDD's) SAN
------------------------------
Message: 9
Date: Wed, 24 Mar 2010 10:14:14 -0700
From: Freddie Cash <fjw...@gmail.com>
Subject: Re: Multi node storage, ZFS
To: freebsd...@freebsd.org
Message-ID:
<b269bc571003241014u3a9...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Wed, Mar 24, 2010 at 10:04 AM, Michael Loftis <mlo...@wgops.com> wrote:
> --On Wednesday, March 24, 2010 9:20 AM -0700 Freddie Cash <
> fjw...@gmail.com> wrote:
> On Wed, Mar 24, 2010 at 8:47 AM, Michal <mic...@ionic.co.uk> wrote:
>
>>
>> I wrote a really long e-mail but realised I could ask this question far
>>> far easier, if it doesn't make sense, the original e-mail is bellow
>>>
>>> Can I use ZFS to create a multinode storage area. Multiple HDD's in
>>> Multiple servers to create one target of, for example, //officestorage
>>> Allowing me to expand the storage space when needed and clients being
>>> able to retrieve data (like RAID0 but over devices not HDD)
>>>
>>> Here is an example I found which is where I'm getting some ideas from
>>> http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
>>>
>>> Horribly, horribly, horribly complex. But, then, that's the Linux world.
>>>
>> :)
>>
>> Server 1: bunch of disks exported via iSCSI
>> Server 2: bunch of disks exported via iSCSI
>> Server 3: bunch of disks exported via iSCSI
>>
>> "SAN" box: uses all those iSCSI exports to create a ZFS pool
>>
>> Use 1 iSCSI export from each server to create a raidz vdev. Or multiple
>> mirror vdevs. When you need more storage, just add another server full of
>> disks, export them via iSCSI to the "SAN" box, and expand the ZFS pool.
>>
>> And, if you need fail-over, on your "SAN" box, you can use HAST at the
>> lower layers (currently only available in 9-CURRENT) to mirror the
>> storage across two systems, and use CARP to provide a single IP for the
>> two boxes.
>>
>
> If you were to do something like this, I'd make sure to have a fast local
> ZIL (log) device on the head node. That would reduce latency for writes,
> you might also do the same for reads. Then your bulk storage comes from the
> iSCSI boxes.
>
Yes, that would be helpful (mirrored slogs, until we get slog removal
support).
As would an L2ARC (cache) device in the head node.
As well as lots and lots and lots of RAM.
And as fast of ethernet NICs as you can get between the head node and the
storage nodes.
And, and, and, and ... :)
--
Freddie Cash
fjw...@gmail.com
------------------------------
Message: 10
Date: Wed, 24 Mar 2010 11:18:51 -0600
From: Michael Loftis <mlo...@wgops.com>
Subject: Re: Multi node storage, ZFS
To: freebsd...@freebsd.org
Message-ID: <6B439D7236FCE1188F74836F@[192.168.1.44]>
Content-Type: text/plain; charset=us-ascii; format=flowed
--On Wednesday, March 24, 2010 5:12 PM +0000 Michal <mic...@ionic.co.uk>
wrote:
>
>> If you were to do something like this, I'd make sure to have a fast
>> local ZIL (log) device on the head node. That would reduce latency
>> for writes, you might also do the same for reads. Then your bulk
>> storage comes from the iSCSI boxes.
>>
>> Just a thought.
>
> I've not come across ZIL so I think I will have to do my research
ZFS Intent Log, basically ZFS's WAL (Write Ahead Log) -- write committed to
the ZIL are considered durable, and the system then batches up ZIL writes
to normal storage. For reads there's the cache devices. I honestly do not
know the state of this in FreeBSD, I gave up using ZFS on FreeBSD for now
due to poor performance. Also the *linux* iSCSI kernel initiator is
*really* buggy, can't say anything about FreeBSD iSCSI initiator nor
target, nor anything about the Linux iSCSI target.
By using (fast) ZFS log and ZFS cache devices that are local to the 'san
head end' you can *greatly* increase the array's perceived/usable speed.
>
>
>> At least in theory you could use geom_gate and zfs I suppose, never
>> tried it though.
>> ggatec(8), ggated(8) are your friends for that.
>>
>> Vince
>
> Just had a look at ggatec, I've not seen or heard of that so I will
> continue looking through that.
>
>
> Many thanks to all, if I get something solid working I will be sure to
> update the list with what will hopefully be a very cheap (other then
> HDD's) SAN
>
>
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
------------------------------
Message: 11
Date: Wed, 24 Mar 2010 10:20:05 -0700
From: Freddie Cash <fjw...@gmail.com>
Subject: Re: Multi node storage, ZFS
To: freebsd...@freebsd.org
Message-ID:
<b269bc571003241020t41c...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Wed, Mar 24, 2010 at 10:12 AM, Michal <mic...@ionic.co.uk> wrote:
> This is pretty much what I have been looking for, I don't mind using a
> SAN Controller server in which to deal with all of this in fact I
> expected that, but I wanted to present the disks from a server full of
> HDD's (which in effect is just a storage device) and then join them up.
> I've briefly looked over RAIDz, will give it a good reading over later.
> I'm thinking 6 disks in each server, and two raidz vdev created from 3
> disks in each server. I can them serve them to the network. I've never
> used ISCSI on FreeBSD however, I played with AOE on different *nix's so
> I will give ISCSI a good looking over.
AFAIK, there's no ATA-over-Ethernet support in FreeBSD, leaving iSCSI as the
only "network block device" option.
Although, I guess one could use ggate to export the remote disks. Not sure
how that compares to iSCSI/AoE. Or where exactly in the storage stack that
works (below iSCSI/AoE??).
--
Freddie Cash
fjw...@gmail.com
------------------------------
Message: 12
Date: Wed, 24 Mar 2010 17:36:54 +0000
From: Michal <mic...@ionic.co.uk>
Subject: Re: Multi node storage, ZFS
To: freebsd...@freebsd.org
Message-ID: <4BAA4DB...@ionic.co.uk>
Content-Type: text/plain; charset=UTF-8
On 24/03/2010 17:14, Freddie Cash wrote:
>
> Yes, that would be helpful (mirrored slogs, until we get slog removal
> support).
>
> As would an L2ARC (cache) device in the head node.
>
> As well as lots and lots and lots of RAM.
>
> And as fast of ethernet NICs as you can get between the head node and the
> storage nodes.
>
> And, and, and, and ... :)
>
As far as I know more RAM is more important the fast CPU, so RAM is the
order of the day, and I guess it depends what you think fast CPU is, but
I wasn't planning on a duel CPU or anything top of the range. I have
some duel core's knocking around...I think testing will show how
good/bad my calculations/assumptions are. Most are done in batched,
nightly and weekly so extremely fast isn't THAT important as we are
looking at device/server backup's and stored data which is moved off
servers once a week. At the minute we are not looking at 100 user file
system or anything along those lines.
For NICS I can sort out a Gb switch or some point-to-point Gb
connections betweeen the nodes, there is also the option is trying
getting some cheap fibre cards (I have a few laying around) and a cheap
fibre switch (something off ebay for testing might do) to have fibre
between the nodes. This however all goes out the water for trying to do
replication to other sites which are 100mb lines, but for the minute I
will focus on 1 location to stop it getting too complex. There are quite
a lot of hardware things which need to be done correctly, and yes I do
need to look at lots of other things. But stage one is just getting a
few Storage devices talking to a Storage controller and seeing if my
ideas work (improve IO, improved redundancy, easy to add storage)
Michael, I sort of understand what you are talking about with ZIL, but
not completely, so thanks for the pointers, there are clearly things I
have not thought about.
------------------------------
Message: 13
Date: Wed, 24 Mar 2010 13:37:06 -0700
From: John Long <fb...@sstec.com>
Subject: Re: Powerd and est / eist functionality
To: "Nenhum_de_Nos" <mat...@eternamente.info>,
freebsd...@freebsd.org
Message-ID: <5.2.1.1.2.201003...@mail.sstec.com>
Content-Type: text/plain; charset="us-ascii"; format=flowed
At 07:55 PM 3/22/2010, Nenhum_de_Nos wrote:
>
>On Mon, March 22, 2010 19:57, John Long wrote:
>> dmesg shows
>> cpu0: <ACPI CPU> on acpi0
>> est0: <Enhanced SpeedStep Frequency Control> on cpu0
>> est: CPU supports Enhanced Speedstep, but is not recognized.
>> est: cpu_vendor GenuineIntel, msr 6160b2506000b25
>> device_attach: est0 attach returned 6
>> p4tcc0: <CPU Frequency Thermal Control> on cpu0
>> cpu1: <ACPI CPU> on acpi0
>> est1: <Enhanced SpeedStep Frequency Control> on cpu1
>> est: CPU supports Enhanced Speedstep, but is not recognized.
>> est: cpu_vendor GenuineIntel, msr 6160b2506000b25
>> device_attach: est1 attach returned 6
>> p4tcc1: <CPU Frequency Thermal Control> on cpu1
>
>I get similar output on 8-STABLE and C2Q 9400/9450.
>wasn't it supposed to attach ok ?
>matheus
I am not sure just what is the best way for all this to work. I do not know
what a return of 6 means (not recognized?) or how to fix it. I can find no
similar mention anywhere of the fact that power is increased and not
lowered by the use of powerd or similar and thought that would provoke some
hints and more discussion because it is intriguing and it self negates its
own purpose and functionality.
I am trying to ascertain the viability of this motherboard w/ regards to
getting the power function working proper and am constrained by the lack of
monitoring tools vs what cupid.com has for win with hwmonitor and cpuz
(they have a dev kit also). Would another brand/model of mb work better? I
know that most all are lacking in acpi function in diff ways. Maybe I am
squeezing water out of a rock, that the cpu is at its min or 6 watts now,
but I just do not know. Btw: Intel is blowing out all 775 type chips. Today
is about the last day. They want everyone on I3/I5 etc but they are not as
functional re low tdp as 775 chips.
Just because you lower the freq by stretching the clock or actually
lowering the freq does not result in a lower TDP. I do not think that the
multiplier being lowered in this case. What appears to be happening is that
the cpu gets busier and that increases the tdp over not using it at all
making it less than useless in my case.
I can find very little comprehensive info on how the eist/est//p4tcc/powerd
thing is supposed to work. Reading source of powerd is not helping.
Logically, if the voltage is lowered then the power is going to be lower.
Is the voltage a function of the load automatically controlled by hardware
and/or the bios or is it supposed to be an artifact of the freq being
lowered by something like powerd? I believe the former for the latter is
not working. I now have everything relevant in the bios enabled.
est appears to be not working but what would happen if it were working? Is
that the key to lowering the TDP when the freq is lowered? Then what is
required for it to work? Where would I find the source in the tree?
p4tcc appears that it is a failsafe for thermal runaway and since my temp
is 26 - 30 or so all the time then it would be of no use because there is
too little differential.
I csupd to stable and rebuilt and there is no difference w/ this prob. I
did see that I went from SATA150 (it should be SATA300) to udma100 sata but
that is for another thread.
I changed hw.acpi.cpu.cx_lowest=C1 to C3 and that saved me about 1.5 watts
w/ powerd but it is still a watt higher than without powerd running at all.
Does anyone know of anything else I can try or is this the best it can get?
John
seemingly relevant sysctls:
debug.acpi.suspend_bounce: 0
debug.acpi.reset_clock: 1
debug.acpi.do_powerstate: 1
debug.acpi.acpi_ca_version: 20100121
debug.acpi.ec.timeout: 750
debug.acpi.ec.polled: 0
debug.acpi.ec.burst: 0
debug.acpi.batt.batt_sleep_ms: 0
debug.acpi.resume_beep: 0
debug.cpufreq.verbose: 0
debug.cpufreq.lowest: 0
hw.pcic.pd6722_vsense: 1
hw.pcic.intr_mask: 57016
hw.acpi.supported_sleep_state: S3 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S3
hw.acpi.lid_switch_state: NONE
hw.acpi.standby_state: NONE
hw.acpi.suspend_state: S3
hw.acpi.sleep_delay: 1
hw.acpi.s4bios: 0
hw.acpi.verbose: 0
hw.acpi.disable_on_reboot: 0
hw.acpi.handle_reboot: 0
hw.acpi.reset_video: 0
hw.acpi.cpu.cx_lowest: C1
dev.acpi.0.%desc: GBT GBTUACPI
dev.acpi.0.%driver: acpi
dev.acpi.0.%parent: nexus0
dev.acpi_sysresource.0.%desc: System Resource
dev.acpi_sysresource.0.%driver: acpi_sysresource
dev.acpi_sysresource.0.%location: handle=\_SB_.PCI0.PX40.SYSR
dev.acpi_sysresource.0.%pnpinfo: _HID=PNP0C02 _UID=1
dev.acpi_sysresource.0.%parent: acpi0
dev.acpi_sysresource.1.%desc: System Resource
dev.acpi_sysresource.1.%driver: acpi_sysresource
dev.acpi_sysresource.1.%location: handle=\_SB_.PCI0.PX40.PMIO
dev.acpi_sysresource.1.%pnpinfo: _HID=PNP0C02 _UID=2
dev.acpi_sysresource.1.%parent: acpi0
dev.acpi_sysresource.2.%desc: System Resource
dev.acpi_sysresource.2.%driver: acpi_sysresource
dev.acpi_sysresource.2.%location: handle=\_SB_.PCI0.EXPL
dev.acpi_sysresource.2.%pnpinfo: _HID=PNP0C02 _UID=4
dev.acpi_sysresource.2.%parent: acpi0
dev.acpi_sysresource.3.%desc: System Resource
dev.acpi_sysresource.3.%driver: acpi_sysresource
dev.acpi_sysresource.3.%location: handle=\_SB_.MEM_
dev.acpi_sysresource.3.%pnpinfo: _HID=PNP0C01 _UID=0
dev.acpi_sysresource.3.%parent: acpi0
dev.acpi_timer.0.%desc: 24-bit timer at 3.579545MHz
dev.acpi_timer.0.%driver: acpi_timer
dev.acpi_timer.0.%location: unknown
dev.acpi_timer.0.%pnpinfo: unknown
dev.acpi_timer.0.%parent: acpi0
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 1466
dev.cpu.0.freq_levels: 2933/-1 2566/-1 2199/-1 1833/-1 1466/-1 1099/-1
733/-1 366/-1
dev.cpu.0.cx_supported: C1/1 C2/1 C3/150
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% last 500us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/1 C3/150
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% 0.00% last 500us
dev.atapci.0.%desc: Intel ICH7 SATA300 controller
dev.atapci.0.%driver: atapci
dev.atapci.0.%location: slot=31 function=2 handle=\_SB_.PCI0.IDE1
dev.atapci.0.%pnpinfo: vendor=0x8086 device=0x27c0 subvendor=0x1458
subdevice=0xb002 class=0x010180
dev.atapci.0.%parent: pci0
dev.ata.0.%desc: ATA channel 0
dev.ata.0.%driver: ata
dev.ata.0.%parent: atapci0
dev.ata.1.%desc: ATA channel 1
dev.ata.1.%driver: ata
dev.ata.1.%parent: atapci0
dev.atdma.0.%desc: AT DMA controller
dev.atdma.0.%driver: atdma
dev.atdma.0.%location: handle=\_SB_.PCI0.PX40.DMA1
dev.atdma.0.%pnpinfo: _HID=PNP0200 _UID=0
dev.atdma.0.%parent: acpi0
dev.p4tcc.0.%desc: CPU Frequency Thermal Control
dev.p4tcc.0.%driver: p4tcc
dev.p4tcc.0.%parent: cpu0
dev.p4tcc.0.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1 3750/-1
2500/-1 1250/-1
dev.p4tcc.1.%desc: CPU Frequency Thermal Control
dev.p4tcc.1.%driver: p4tcc
dev.p4tcc.1.%parent: cpu1
dev.p4tcc.1.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1 3750/-1
2500/-1 1250/-1
dev.cpufreq.0.%driver: cpufreq
dev.cpufreq.0.%parent: cpu0
dev.cpufreq.1.%driver: cpufreq
dev.cpufreq.1.%parent: cpu1
------------------------------
Message: 14
Date: Wed, 24 Mar 2010 13:45:06 -0700
From: John Long <fb...@sstec.com>
Subject: Re: Powerd and est / eist functionality
To: Alexander Motin <m...@FreeBSD.org>
Cc: FreeBSD-STABLE Mailing List <freebsd...@FreeBSD.org>
Message-ID: <5.2.1.1.2.201003...@mail.sstec.com>
Content-Type: text/plain; charset="us-ascii"; format=flowed
At 11:27 PM 3/22/2010, Alexander Motin wrote:
>John Long wrote:
>> Hello, I am putting together a couple update servers. Went with c2d
>> E7500 on gigabyte G41M-ES2L boards. fbsd 8.0 release generic (so far)
>> amd64, 1g mem, 1tb wd cavier blk, fresh system.
>> My Kill-a-watt shows 41 watts idle and when I enable powerd then it
>> climbs to 43 watts idle.
>> It shows that the freq is controlled well, goes down to 365 mhz but
>> the tdp is not decreased, rather it increases.
>> If I disable eist, c1 and c3 helpers in bios, as per suggestion in
>> mail archive, then it adds 1 watt to both figures. I was hoping to get
>> this total tdp down to a very low amount, and it is but it should
>> theoretically go lower with powerd, right?
>> The bios reports 1.268V and 26C temp. I was hoping that the voltage
>> would go down to .85 or so when powerd lowered the freq to 365 etc.
>> Healthd does not seem to know what monitoring chip it is and I have no
>> idea unless I install xp (ugh) and run something from cpuid.com on it.
>> What is a good/better/best monitoring program, mbmon and bsdhwmon are
>> untried for they are not current I see. Or what do I do from here to
>> fix this problem?
>> thx,
>> John
>> dmesg shows
>> cpu0: <ACPI CPU> on acpi0
>> est0: <Enhanced SpeedStep Frequency Control> on cpu0
>> est: CPU supports Enhanced Speedstep, but is not recognized.
>> est: cpu_vendor GenuineIntel, msr 6160b2506000b25
>> device_attach: est0 attach returned 6
>> p4tcc0: <CPU Frequency Thermal Control> on cpu0
>> cpu1: <ACPI CPU> on acpi0
>> est1: <Enhanced SpeedStep Frequency Control> on cpu1
>> est: CPU supports Enhanced Speedstep, but is not recognized.
>> est: cpu_vendor GenuineIntel, msr 6160b2506000b25
>> device_attach: est1 attach returned 6
>> p4tcc1: <CPU Frequency Thermal Control> on cpu1
>> powerd -v
>> powerd: unable to determine AC line status
>> load 0%, current freq 2926 MHz ( 0), wanted freq 2834 MHz
>> load 0%, current freq 2926 MHz ( 0), wanted freq 2745 MHz
>> .......
>> load 3%, current freq 365 MHz ( 7), wanted freq 365 MHz
>> load 0%, current freq 365 MHz ( 7), wanted freq 365 MHz
>
>Your ACPI BIOS seems not reporting tables required to control EIST. So
>powerd probably uses only thermal throttling, which is not really
>effective for power saving on modern CPUs. You should check your BIOS
>options or may be update BIOS.
>
>If you have no luck with EIST - try to use C-states if BIOS reports at
>least them. It also can be quite effective.
>
>--
>Alexander Motin
Thanks for the info, I did try to kick it to C3 and that helped poquito
amount. Everything is enabled in bios that matters to this, that does help
a little too but powerd actually raises tdp a little. See other recent
reply for more info.
Thanks,
John
------------------------------
Message: 15
Date: Wed, 24 Mar 2010 14:36:54 -0700
From: Jeremy Chadwick <fre...@jdc.parodius.com>
Subject: Re: Powerd and est / eist functionality
To: John Long <fb...@sstec.com>
Cc: freebsd...@freebsd.org, Nenhum_de_Nos
<mat...@eternamente.info>
Message-ID: <20100324213...@icarus.home.lan>
Content-Type: text/plain; charset=us-ascii
On Wed, Mar 24, 2010 at 01:37:06PM -0700, John Long wrote:
> I am trying to ascertain the viability of this motherboard w/
> regards to getting the power function working proper and am
> constrained by the lack of monitoring tools vs what cupid.com has
> for win with hwmonitor and cpuz (they have a dev kit also). Would
> another brand/model of mb work better? I know that most all are
> lacking in acpi function in diff ways. Maybe I am squeezing water
> out of a rock, that the cpu is at its min or 6 watts now, but I just
> do not know.
You're placing too many eggs in one basket. Hardware monitoring is a
separate beast, and one you won't find good support for on FreeBSD.
By "hardware monitoring" I'm talking about thermals off the mainboard,
fan RPMs, CPU temperature (not on-die temps), and voltages. Let's talk
about those first, as they're something I'm familiar with.
- These data sources are only available if the motherboard manufacturer
added a H/W monitoring I/C to their mainboard. Consumer mainboards
are spotty as far as offering this capability.
- Each mainboard is different. Each mainboard model, or even
subrevision, can use a completely different H/W monitoring chip. To
make matters more complex, there are multiple models of H/W monitoring
ICs, and even multiple revision/versions of the same model that behave
completely different than their predecessor(s).
- How this chip is implemented on the mainboard is up to the
manufacturer. Some chips only exist on the LPC bus (think ISA I/O
ports). Some chips support SMBus. The mainboard has to be engineered
so that the pins on the H/W IC tie in to the LPC or SMBus bus(ses). You
don't know which is available/used unless the manufacturer states such
in their User Manual.
- In the case of LPC, the exact I/O ports must be provided by the board
manufacturer. In the case of SMBus, the slave address must be
provided by the board manufacturer. **YOU CANNOT GUESS THESE** despite
Linux's lm-sensors project having folks think otherwise. Guessing
("probing") is very high risk, and involves submitting reads to a select
set of LPC I/O ports (which could be used for other things/devices), or
to a select SMBus slave address. Some registers do things to the system
(or associated chips) on read operations; bits can get reset. I've seen
this happen in the case of one Winbond chip where an incorrect CRxx read
resulted in the chips' watchdog firing an NMI.
- Knowing the exact model and subrevision of H/W IC is important, since
programmer of the monitoring software has to know what all the
register offsets are, how to decode the data, etc.. There is no
standard, and there are multiple manufacturers of such devices
(Nuvoton/Winbond, National Semiconductor, ON Semiconductor/Analog
Devices, SMSC, TI, and some others. For a while companies like AMD,
nVidia, Intel, Broadcom, ALi, and VIA were making their own chips as
well).
- In the case of SMBus, the operating system must have an SMBus driver
for the system chipset (not H/W chip). For example, Intel systems often
use ichsmb(4), AMD systems use amdsmb(4), and so on. Without a driver
it's not feasible/possible for userland applications to talk to a device
connected to SMBus. For sake of example, there's no SMBus driver on
FreeBSD for ServerWorks chipsets.
Getting all of this data out of the mainboard manufacturer is like
pulling teeth, especially in the case of consumer boards. Server board
manufacturers (Supermicro, Tyan, Intel, etc.) often disclose this
information to those who request it via Technical Support. But if you
were to mail, say, Asus for this information, it'd likely go in one ear
and out the other.
All that (negativity) said: the closest thing you'll find on FreeBSD to
interface with these chips is ports/sysutils/mbmon,
ports/sysutils/healthd, or ports/sysutils/bsdhwmon.
mbmon supports very old mainboards which utilise LPC (it's SMBus support
is broken/shoddy). It also tries auto-probing, often gets it wrong, and
spits out readings which are incorrect/off the charts. Sometimes it
gets things wrong and spits out values that look real but aren't.
healthd is basically mbmon with some minor changes to the core but major
changes to the surrounding user interface.
bsdhwmon is intended for servers only and only speaks to devices using
SMBus, of which I'm the author.
Are we having fun yet?
Now back to the bigger picture...
CPU temperature (assuming you have a newer AMD or Intel CPU) is
available via the coretemp(4) driver, and active CPU clock frequency is
available via the cpufreq(4) drivers and their subsets. There is also
some very archaic (IMHO) support for temperature monitoring via ACPI,
but I believe that's mainly intended for laptops. With regards to ACPI,
you're purely limited by what the mainboard/BIOS implementer does; many
consumer motherboard vendors have absolutely no idea what to do with a
technical support request asking they fix/improve their ACPI tables.
For coretemp(4), you'll find the thermals under dev.cpu.X.temperature
in sysctl.
For cpufreq(4), you'll find the available processor frequency levels
under dev.cpu.X.freq_levels and what the current frequency is in
dev.cpu.X.freq.
For est(4), there's dev.est.X.freq_settings but I'm not sure how to get
these to be used or how to tune them; keep reading.
> Btw: Intel is blowing out all 775 type chips. Today is about the last
> day. They want everyone on I3/I5 etc but they are not as functional re
> low tdp as 775 chips.
That's a very interesting opinion you have there. I continue to see
LGA775 chips sold regularly all over, and new stock coming in fairly
often to major resellers online.
The i3/i5/i7 chips don't appear to offer ECC framework on their memory
controllers (which are now on-die as I'm sure you know), which is why I
plan to stay away from them for servers. Intel's pushing Xeon for that,
which I'm not willing to switch to until the prices drop more. There
are existing C2D and C2Q CPUs which have the exact same capabilities and
features as their Xeon counterparts yet the Xeons cost $50-100 more.
It's like SCSI all over again.
If low-as-possible TDP is all you're concerned with, buy an Atom.
> I can find very little comprehensive info on how the
> eist/est//p4tcc/powerd thing is supposed to work. Reading source of
> powerd is not helping. Logically, if the voltage is lowered then the
> power is going to be lower. Is the voltage a function of the load
> automatically controlled by hardware and/or the bios or is it
> supposed to be an artifact of the freq being lowered by something
> like powerd? I believe the former for the latter is not working. I
> now have everything relevant in the bios enabled.
What you probably want to look at is the source to all the subset
cpufreq(4) drivers that powerd(8) speaks to. See the cpufreq(4) man
page for details.
It seems most of us here -- myself included -- have very little
familiarity with how to get FreeBSD to use one subset driver or another
(e.g. est(4) vs. acpi_throttle(4), etc.). Someone recently clued me in
to how to switch from acpi_throttle to est on my Intel board which
*does* attach est(4) successfully, but I haven't bothered trying it
yet:
http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055665.html
http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055666.html
The disabled=1 variables shown there are for loader.conf, by the way,
and require a reboot after adjusting.
I'd give you links to the main thread, but Dan Naumov's mail client
doesn't appear to have Reference-Id header support so every reply of
his appears as a "new" entry in the thread list. Search for "powerd on
8.0, is it considered safe?" here:
http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/thread.html
> est appears to be not working but what would happen if it were
> working?
It should lower the clock frequency of the CPU during idle times, and
increase it during load. **HOW** it goes about adjusting the frequency
is where the different subset drivers come into play.
The attachment "error 6" message you see usually indicates the est(4)
driver doesn't have support for you specific model of CPU based on its
capabilities, or at least that's how I understand it. John Baldwin (I
think?) or Nate Lawson might have to chime in here.
You're not the first one to report this issue. It comes up fairly
often. Possibly since you're digging into the code you'd like to take
up maintaining these pieces?
> I csupd to stable and rebuilt and there is no difference w/ this
> prob. I did see that I went from SATA150 (it should be SATA300) to
> udma100 sata but that is for another thread.
This is a bug/quirk of some changes in ata(4). Your drive should be
operating at full SATA speed (probably SATA300). You can bring this up
in another thread if you want, but it's purely cosmetic as far as I
know. atacontrol(8) and diskinfo(8) -t and -c will come in handy.
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
------------------------------
Message: 16
Date: Wed, 24 Mar 2010 22:03:34 +0000
From: Krzysztof Dajka <alte...@gmail.com>
Subject: Re: Can't boot after make installworld
To: Jeremy Chadwick <fre...@jdc.parodius.com>
Cc: freebsd...@freebsd.org
Message-ID:
<684e57ec1003241503m5e9...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Thanks a lot for clarifying. I think that I'm going to stick with
STABLE release, as it reflects my expectations and time I can dedicate
to tinker with my system.
For some while I thought that I would return to Debian, because I
became used to it's pros and cons. Thanks to experience I gained in
few months in FreeBSD land I didn't think about Debian in GNU/Linux
incarnation, but at least Debian/kFreeBSD. Unfortunately as of today
Debian/kFreeBSD doesn't support booting from zfs. I think that it was
good idea to migrate to FreeBSD, as for now I'm missing fast upgrades
and deployment which are Debian assets, but I'm getting used to ports
and possibility of tuning system.
I've read thread
http://lists.freebsd.org/pipermail/freebsd-fs/2010-March/007956.html,
PJD is suggesting to enable few options in kernel:
> options WITNESS
> options WITNESS_SKIPSPIN
> options INVARIANTS
> options INVARIANT_SUPPORT
> options DEBUG_VFS_LOCKS
> options DEBUG_LOCKS
> options KDB
> options DDB
Is there something else I should turn on in kernel before running
bonnie++ which will surely crash my system? And one more question is
there a way to build new kernel which would be called ie kernel_debug
which I would load only when needed?
On
3/24/10, Jeremy Chadwick <fre...@jdc.parodius.com> wrote:
>Since you replied to Mark and I personally -- can you send a copy of
>this mail back to the mailing list? Others should be able to help
>answer the above questions; in this case, more eyes = good. :-)
Sorry about that sending mails not to everyone happens to me all the time ;)
------------------------------
Message: 17
Date: Wed, 24 Mar 2010 23:19:16 +0100
From: Ivan Voras <ivo...@freebsd.org>
Subject: Re: Multi node storage, ZFS
To: freebsd...@freebsd.org
Message-ID: <hoe355$tuk$1...@dough.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Freddie Cash wrote:
> On Wed, Mar 24, 2010 at 8:47 AM, Michal <mic...@ionic.co.uk> wrote:
>
>> I wrote a really long e-mail but realised I could ask this question far
>> far easier, if it doesn't make sense, the original e-mail is bellow
>>
>> Can I use ZFS to create a multinode storage area. Multiple HDD's in
>> Multiple servers to create one target of, for example, //officestorage
>> Allowing me to expand the storage space when needed and clients being
>> able to retrieve data (like RAID0 but over devices not HDD)
>>
>> Here is an example I found which is where I'm getting some ideas from
>> http://www.howtoforge.com/how-to-build-a-low-cost-san-p3
>>
>> Horribly, horribly, horribly complex. But, then, that's the Linux world.
> :)
>
> Server 1: bunch of disks exported via iSCSI
> Server 2: bunch of disks exported via iSCSI
> Server 3: bunch of disks exported via iSCSI
>
> "SAN" box: uses all those iSCSI exports to create a ZFS pool
For what it's worth - I think this is a good idea! iSCSI and ZFS make it
extraordinarily flexible to do this. You can have a RAIS - redundant
array of inexpensive servers :)
For example: each server box hosts 8-12 drives - use a hardware
controller with RAID6 and a BBU to create a single volume (if FreeBSD
booting issues allow, but that can be worked around). Export this volume
via iSCSI. Repeat for the rest of the servers. Then, on the client,
create a RAIDZ. or if you trust your setup that much. a straight striped
ZFS volume. If you do it the RAIDZ way, one of your storage servers can
fail completely.
As you need more space, add more servers in batches of three (if you did
RAIDZ, else the number doesn't matter), add them to the client as usual.
The "client" in this case can be a file server, and you can achieve
failover between several of those by using e.g. carp, heartbeat, etc. -
if the master node fails, some other one can reconstitute the ZFS pool
ad make it available.
But, you need very fast links between the nodes, and I wouldn't use
something like this without extensively testing the failure modes.
------------------------------
Message: 18
Date: Wed, 24 Mar 2010 23:30:20 +0100
From: Miroslav Lachman <000....@quip.cz>
Subject: Re: Multi node storage, ZFS
To: Michal <mic...@ionic.co.uk>
Cc: freebsd...@freebsd.org
Message-ID: <4BAA92...@quip.cz>
Content-Type: text/plain; charset=UTF-8; format=flowed
Michal wrote:
> On 24/03/2010 17:14, Freddie Cash wrote:
>
>>
>> Yes, that would be helpful (mirrored slogs, until we get slog removal
>> support).
>>
>> As would an L2ARC (cache) device in the head node.
>>
>> As well as lots and lots and lots of RAM.
>>
>> And as fast of ethernet NICs as you can get between the head node and the
>> storage nodes.
>>
>> And, and, and, and ... :)
>>
>
> As far as I know more RAM is more important the fast CPU, so RAM is the
> order of the day, and I guess it depends what you think fast CPU is, but
> I wasn't planning on a duel CPU or anything top of the range. I have
> some duel core's knocking around...
Any modern multicore CPU will be fine. And more RAM you have, the larger
ARC / prefetch will be used (more read speed you will gain)
> Michael, I sort of understand what you are talking about with ZIL, but
> not completely, so thanks for the pointers, there are clearly things I
> have not thought about.
This links can be useful to you
ZFS L2ARC
http://blogs.sun.com/brendan/entry/test
ZFS Evil Tuning Guide
http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#Disabling_the_ZIL_.28Don.27t.29
ZFS ZIL + L2ARC SSD Setup
http://www.mail-archive.com/zfs-d...@opensolaris.org/msg34674.html
Miroslav Lachman
------------------------------
Message: 19
Date: Wed, 24 Mar 2010 23:45:25 +0000
From: Michal <mic...@ionic.co.uk>
Subject: Re: Multi node storage, ZFS
To: freebsd...@freebsd.org
Message-ID: <4BAAA415...@ionic.co.uk>
Content-Type: text/plain; charset=UTF-8
On 24/03/2010 22:19, Ivan Voras wrote:
>
> For what it's worth - I think this is a good idea! iSCSI and ZFS make it
> extraordinarily flexible to do this. You can have a RAIS - redundant
> array of inexpensive servers :)
>
> For example: each server box hosts 8-12 drives - use a hardware
> controller with RAID6 and a BBU to create a single volume (if FreeBSD
> booting issues allow, but that can be worked around). Export this volume
> via iSCSI. Repeat for the rest of the servers. Then, on the client,
> create a RAIDZ. or if you trust your setup that much. a straight striped
> ZFS volume. If you do it the RAIDZ way, one of your storage servers can
> fail completely.
>
> As you need more space, add more servers in batches of three (if you did
> RAIDZ, else the number doesn't matter), add them to the client as usual.
>
> The "client" in this case can be a file server, and you can achieve
> failover between several of those by using e.g. carp, heartbeat, etc. -
> if the master node fails, some other one can reconstitute the ZFS pool
> ad make it available.
>
> But, you need very fast links between the nodes, and I wouldn't use
> something like this without extensively testing the failure modes.
>
I do aswell :D The thing is, I see it two ways; I worked for a a huge
online betting company, and we had the money for HP MSA's and big
expensive SAN's, then we have a lot of SMB's with no where near the
budget for that but the same problem with lots of data and the need for
backend storage for databases. It's all well and good having 1 ZFS
server, but it's fragile in the the sense of no redundancy, then we have
1 ZFS server and a 2nd with DRBD, but that's a waste of money...think 12
TB, and you need to pay for another 12TB box for redundancy, and you are
still looking at 1 server. I am thinking a cheap solution but one that
has IO throughput, redundancy and is easy to manange and expand across
multiple nodes
A "NAS" based solution...one based on a single NAS device which has
single targets //nas1 //nas2 etc is ok, but has many problems. A "SAN"
based solution can overcome these, it does add cost, but the amount can
be minimised. I'll work on it over the next few days and get some notes
typed up as well as some run some performance numbers. I'll try and do
it modular by adding more RAM and sorting our ZLS and cache, comparing
how they effect performance
------------------------------
Message: 20
Date: Thu, 25 Mar 2010 00:47:12 +0100
From: "O. Hartmann" <ohar...@mail.zedat.fu-berlin.de>
Subject: Re: Firefox 3.6.X and Thunderbird 3.0.X crashing with Radeon
graphics on FBSD 8.0-STABLE SMP/sm64 box
To: gary.je...@freenet.de
Cc: freebsd...@freebsd.org, "O. Hartmann"
<ohar...@zedat.fu-berlin.de>, freebsd-...@freebsd.org,
freebs...@freebsd.org
Message-ID: <4BAAA480...@mail.zedat.fu-berlin.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
On 03/24/10 15:06, Gary Jennejohn wrote:
> On Wed, 24 Mar 2010 13:32:40 +0000
> "O. Hartmann"<ohar...@zedat.fu-berlin.de> wrote:
>
>> Since the introduction of Thunderbird 3.0 and Firefox 3.6 I see
>> spontanous crashes/coredumps of both thunderbird and firefox. Interingly
>> Firefox 3.5.X works well on he same platform.
>>
>> The platform is a FreeBSD 8.0-STABLE/amd64 (r205536: Tue Mar 23 22:19:04
>> CET 2010), SMP box with 8GB of RAM, QuadCore Intel Q6600 on a P35-based
>> motherboard.
>>
>> Thunderbird 3 crashes rarely compared to Firefox 3. The longer the
>> application thunderbird runs, the higher the likelyhood the app crashes
>> and vanishes. Sometimes this happens immediately after starting
>> thunderbird, sometimes it takes its few minutes or half an hour.
>>
>> Firefox 3 is sensitive to its pull-down menus or requester showing up in
>> some situations. I can provoke a crash by clicking onto a pull-down-menu
>> in firefox 3, it immediately dumps a core.
>>
>
> If you suspect the graphics card's driver is at fault then I would try
> linux-opera or even linux-firefox and see whether it also dies when you
> use a drop-down menu.
>
> Another possibility would be to set hw.physmem to say 3G or 4G in
> loader.conf and see whether that affects thunderbird/firefox. Who
> knows, there may some weird problem caused by all that memory? That
> would a fairly quick and cheap way to test this.
>
> --
> Gary Jennejohn
You're right, I'll test this as soon as I'm back in my lab.
Oliver Hartmann
------------------------------
Message: 21
Date: Thu, 25 Mar 2010 00:33:35 +0000
From: Ben Morrow <b...@morrow.me.uk>
Subject: Re: Multi node storage, ZFS
To: mic...@ionic.co.uk, freebsd...@freebsd.org
Message-ID: <2010032500...@osiris.mauzo.dyndns.org>
Content-Type: text/plain; charset=us-ascii
Quoth Michal <mic...@ionic.co.uk>:
>
> I do aswell :D The thing is, I see it two ways; I worked for a a huge
> online betting company, and we had the money for HP MSA's and big
> expensive SAN's, then we have a lot of SMB's with no where near the
> budget for that but the same problem with lots of data and the need for
> backend storage for databases. It's all well and good having 1 ZFS
> server, but it's fragile in the the sense of no redundancy, then we have
> 1 ZFS server and a 2nd with DRBD, but that's a waste of money...think 12
> TB, and you need to pay for another 12TB box for redundancy, and you are
> still looking at 1 server. I am thinking a cheap solution but one that
> has IO throughput, redundancy and is easy to manange and expand across
> multiple nodes
If you do it right, you could have the 'SAN' box be one of the boxes
full of discs, with some or all of the others able to take over the
'SAN' role if it fails. That way you get redundancy without having to
have a machine sit idle. (You're still using more discs than you
strictly need to hold that much data, of course, but you can't avoid
that.)
Ben
------------------------------
Message: 22
Date: Wed, 24 Mar 2010 18:04:51 -0700
From: John Long <fb...@sstec.com>
Subject: Re: Powerd and est / eist functionality
To: Jeremy Chadwick <fre...@jdc.parodius.com>
Cc: freebsd...@freebsd.org, Nenhum_de_Nos
<mat...@eternamente.info>
Message-ID: <5.2.1.1.2.201003...@mail.sstec.com>
Content-Type: text/plain; charset="us-ascii"; format=flowed
At 02:36 PM 3/24/2010, Jeremy Chadwick wrote:
>On Wed, Mar 24, 2010 at 01:37:06PM -0700, John Long wrote:
>> I am trying to ascertain the viability of this motherboard w/
>> regards to getting the power function working proper and am
>> constrained by the lack of monitoring tools vs what cupid.com has
>> for win with hwmonitor and cpuz (they have a dev kit also). Would
>> another brand/model of mb work better? I know that most all are
>> lacking in acpi function in diff ways. Maybe I am squeezing water
>> out of a rock, that the cpu is at its min or 6 watts now, but I just
>> do not know.
>
>You're placing too many eggs in one basket. Hardware monitoring is a
>separate beast, and one you won't find good support for on FreeBSD.
>By "hardware monitoring" I'm talking about thermals off the mainboard,
>fan RPMs, CPU temperature (not on-die temps), and voltages. Let's talk
>about those first, as they're something I'm familiar with.
>
>- These data sources are only available if the motherboard manufacturer
>added a H/W monitoring I/C to their mainboard. Consumer mainboards
>are spotty as far as offering this capability.
>
>- Each mainboard is different. Each mainboard model, or even
>subrevision, can use a completely different H/W monitoring chip. To
>make matters more complex, there are multiple models of H/W monitoring
>ICs, and even multiple revision/versions of the same model that behave
>completely different than their predecessor(s).
>
>- How this chip is implemented on the mainboard is up to the
>manufacturer. Some chips only exist on the LPC bus (think ISA I/O
>ports). Some chips support SMBus. The mainboard has to be engineered
>so that the pins on the H/W IC tie in to the LPC or SMBus bus(ses). You
>don't know which is available/used unless the manufacturer states such
>in their User Manual.
>
>- In the case of LPC, the exact I/O ports must be provided by the board
>manufacturer. In the case of SMBus, the slave address must be
>provided by the board manufacturer. **YOU CANNOT GUESS THESE** despite
>Linux's lm-sensors project having folks think otherwise. Guessing
>("probing") is very high risk, and involves submitting reads to a select
>set of LPC I/O ports (which could be used for other things/devices), or
>to a select SMBus slave address. Some registers do things to the system
>(or associated chips) on read operations; bits can get reset. I've seen
>this happen in the case of one Winbond chip where an incorrect CRxx read
>resulted in the chips' watchdog firing an NMI.
>
>- Knowing the exact model and subrevision of H/W IC is important, since
>programmer of the monitoring software has to know what all the
>register offsets are, how to decode the data, etc.. There is no
>standard, and there are multiple manufacturers of such devices
>(Nuvoton/Winbond, National Semiconductor, ON Semiconductor/Analog
>Devices, SMSC, TI, and some others. For a while companies like AMD,
>nVidia, Intel, Broadcom, ALi, and VIA were making their own chips as
>well).
>
>- In the case of SMBus, the operating system must have an SMBus driver
>for the system chipset (not H/W chip). For example, Intel systems often
>use ichsmb(4), AMD systems use amdsmb(4), and so on. Without a driver
>it's not feasible/possible for userland applications to talk to a device
>connected to SMBus. For sake of example, there's no SMBus driver on
>FreeBSD for ServerWorks chipsets.
>
>Getting all of this data out of the mainboard manufacturer is like
>pulling teeth, especially in the case of consumer boards. Server board
>manufacturers (Supermicro, Tyan, Intel, etc.) often disclose this
>information to those who request it via Technical Support. But if you
>were to mail, say, Asus for this information, it'd likely go in one ear
>and out the other.
>
>All that (negativity) said: the closest thing you'll find on FreeBSD to
>interface with these chips is ports/sysutils/mbmon,
>ports/sysutils/healthd, or ports/sysutils/bsdhwmon.
>
>mbmon supports very old mainboards which utilise LPC (it's SMBus support
>is broken/shoddy). It also tries auto-probing, often gets it wrong, and
>spits out readings which are incorrect/off the charts. Sometimes it
>gets things wrong and spits out values that look real but aren't.
>
>healthd is basically mbmon with some minor changes to the core but major
>changes to the surrounding user interface.
>
>bsdhwmon is intended for servers only and only speaks to devices using
>SMBus, of which I'm the author.
>
>Are we having fun yet?
>
>Now back to the bigger picture...
>
>CPU temperature (assuming you have a newer AMD or Intel CPU) is
>available via the coretemp(4) driver, and active CPU clock frequency is
>available via the cpufreq(4) drivers and their subsets. There is also
>some very archaic (IMHO) support for temperature monitoring via ACPI,
>but I believe that's mainly intended for laptops. With regards to ACPI,
>you're purely limited by what the mainboard/BIOS implementer does; many
>consumer motherboard vendors have absolutely no idea what to do with a
>technical support request asking they fix/improve their ACPI tables.
>
>For coretemp(4), you'll find the thermals under dev.cpu.X.temperature
>in sysctl.
>
>For cpufreq(4), you'll find the available processor frequency levels
>under dev.cpu.X.freq_levels and what the current frequency is in
>dev.cpu.X.freq.
>
>For est(4), there's dev.est.X.freq_settings but I'm not sure how to get
>these to be used or how to tune them; keep reading.
I want to thank you very much for all the info you have provided. It has
clued me into a much better understanding and I see that it is a big
un-standard thing to monitor these functions. It seems that things are
actually working well with this system and I am chasing diminishing returns.
Let me just add this link for others that are on a path of understanding re
eist/est/powerd etc..
http://www.techarp.com/showarticle.aspx?artno=420&pgno=1 All power states
defined and link to acpi docs.
>
>> Btw: Intel is blowing out all 775 type chips. Today is about the last
>> day. They want everyone on I3/I5 etc but they are not as functional re
>> low tdp as 775 chips.
>
>That's a very interesting opinion you have there. I continue to see
>LGA775 chips sold regularly all over, and new stock coming in fairly
>often to major resellers online.
Knowing of the problems with h55 and bsd etc while needing to update both
my servers (k6-3 antiques from 1998 plus I have to get ready for the DNSSEC
changeover coming soon - run my own dns), I have been trying to catch the
Frys specials for a couple months on the Eseries c2d mdb and chip combos. 2
weeks ago I caught the hint that they were blowing all 775 stuff out, Frys
employee verified that, Intel's orders. Frys is big, Intel is not making
anymore 775 chips and when they are gone then only few online will have it.
They are going fast, On Saturday Frys (Woodland hills) had 25 E7500s, they
had a E7500 and mbd sale on monday and another today. I doubt they have
anymore other than open box now. They blew out all other 775 chips they had
prior to monday (e3400 last wk, 6300 prior). They may have some Q or E8200
etc but they may have another sale if so. It will not be long before newegg
and others are out of stock and cost will go way up. They want to push
everyone into the I-series. Wait and see..
>
>The i3/i5/i7 chips don't appear to offer ECC framework on their memory
>controllers (which are now on-die as I'm sure you know), which is why I
>plan to stay away from them for servers. Intel's pushing Xeon for that,
>which I'm not willing to switch to until the prices drop more. There
>are existing C2D and C2Q CPUs which have the exact same capabilities and
>features as their Xeon counterparts yet the Xeons cost $50-100 more.
>It's like SCSI all over again.
>
I agree with your thoughts however I believe one can still use the I-series
in a p55 board and get the ECC working but then you need to use a separate
video bd and the TDP is going to be about 30+ watts higher than using a g41
or such mbd and 775 chip.
>If low-as-possible TDP is all you're concerned with, buy an Atom.
Atom is about half the perf of a c2d especially if c2d is oc'd. An Atom in
a gclf945 mbd is about 35 watts because of the old 945 chip is 130nm tech.
Atom in Nvidia mdb would be way to go but c2d is still much faster. I get
41 watts with E7500, G41 mbd w/ video, 1 GB mem and 1 TB WD cavier HD
including losses thru power supply (antec 380 green -80 plus bronze,
smallest 80 plus handy). 24/7/365 is $1.00 per watt at my current rate of
8.5c / KWhr per year. Save 20 watts is saving $20.00 or more per year plus
I am set up for running on batteries and going solar. Do not discount the
problems in the economy. I run a truth website (netctr.com), things are not
as we are told by tptb.
>
>> I can find very little comprehensive info on how the
>> eist/est//p4tcc/powerd thing is supposed to work. Reading source of
>> powerd is not helping. Logically, if the voltage is lowered then the
>> power is going to be lower. Is the voltage a function of the load
>> automatically controlled by hardware and/or the bios or is it
>> supposed to be an artifact of the freq being lowered by something
>> like powerd? I believe the former for the latter is not working. I
>> now have everything relevant in the bios enabled.
>
>What you probably want to look at is the source to all the subset
>cpufreq(4) drivers that powerd(8) speaks to. See the cpufreq(4) man
>page for details.
I followed that and quite a bit more, it looks to be too much for just I to
handle with my constraints of duty and time.
>
>It seems most of us here -- myself included -- have very little
>familiarity with how to get FreeBSD to use one subset driver or another
>(e.g. est(4) vs. acpi_throttle(4), etc.). Someone recently clued me in
>to how to switch from acpi_throttle to est on my Intel board which
>*does* attach est(4) successfully, but I haven't bothered trying it
>yet:
>
>http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055665.html
>http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055666.html
>
>The disabled=1 variables shown there are for loader.conf, by the way,
>and require a reboot after adjusting.
>
>I'd give you links to the main thread, but Dan Naumov's mail client
>doesn't appear to have Reference-Id header support so every reply of
>his appears as a "new" entry in the thread list. Search for "powerd on
>8.0, is it considered safe?" here:
>
>http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/thread.html
I read all that and much more for several years back in my archives (I keep
about 11 years of mailists in my system here). I figured it was a nebulous
quest without more info. Now I see it is more then I need to byte off :-)
>
>> est appears to be not working but what would happen if it were
>> working?
>
>It should lower the clock frequency of the CPU during idle times, and
>increase it during load. **HOW** it goes about adjusting the frequency
>is where the different subset drivers come into play.
>
>The attachment "error 6" message you see usually indicates the est(4)
>driver doesn't have support for you specific model of CPU based on its
>capabilities, or at least that's how I understand it. John Baldwin (I
>think?) or Nate Lawson might have to chime in here.
>
>You're not the first one to report this issue. It comes up fairly
>often. Possibly since you're digging into the code you'd like to take
>up maintaining these pieces?
I appreciate the offer but I think it is more than I can chew right now :-)
I was just trying to find out how all this was supposed to work in the proper.
>> I csupd to stable and rebuilt and there is no difference w/ this
>> prob. I did see that I went from SATA150 (it should be SATA300) to
>> udma100 sata but that is for another thread.
>
>This is a bug/quirk of some changes in ata(4). Your drive should be
>operating at full SATA speed (probably SATA300). You can bring this up
>in another thread if you want, but it's purely cosmetic as far as I
>know. atacontrol(8) and diskinfo(8) -t and -c will come in handy.
Moving this to another thread for there are some unknowns here.
>
>--
>| Jeremy Chadwick j...@parodius.com |
>| Parodius Networking http://www.parodius.com/ |
>| UNIX Systems Administrator Mountain View, CA, USA |
>| Making life hard for others since 1977. PGP: 4BD6C0CB |
Thanks much again,
John
------------------------------
Message: 23
Date: Wed, 24 Mar 2010 20:48:48 -0500
From: "Matthew D. Fuller" <full...@over-yonder.net>
Subject: Re: Powerd and est / eist functionality
To: John Long <fb...@sstec.com>
Cc: freebsd...@freebsd.org, Jeremy Chadwick
<fre...@jdc.parodius.com>
Message-ID: <20100325014...@over-yonder.net>
Content-Type: text/plain; charset=us-ascii
On Wed, Mar 24, 2010 at 06:04:51PM -0700 I heard the voice of
John Long, and lo! it spake thus:
>
>> The i3/i5/i7 chips don't appear to offer ECC framework on their
>> memory controllers (which are now on-die as I'm sure you know),
>> which is why I plan to stay away from them for servers.
>
> I agree with your thoughts however I believe one can still use the
> I-series in a p55 board and get the ECC working
Not the case. To use ECC, the memory controller has to support it.
Nehalem moved the memory controller on-die, and on the non-Xeons, it
doesn't have ECC capability. You'd have to go Xeon, use prior chips
(with the memory controller on the motherboard) with careful
motherboard selection, or use AMD (where all the chips have ECC in the
IMC, though you still need a little care to be sure your motherboard
doesn't sabotage it).
--
Matthew Fuller (MF4839) | full...@over-yonder.net
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
------------------------------
End of freebsd-stable Digest, Vol 349, Issue 4
**********************************************