Re: Using GTP and glabel for ZFS arrays

[Andrey V. Elsukov]

On 22.07.2010 10:32, Dan Langille wrote:
> I'm not sure of the criteria, but this is what I'm running:
> 
> atapci0:  port 0xdc00-0xdc0f mem
> 0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on pci7
> 
> atapci1:  port 0xac00-0xac0f mem
> 0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on pci3
> 
> I added ahci_load="YES" to loader.conf and rebooted.  Now I see:

You can add siis_load="YES" to loader.conf for SiI 3124.

-- 
WBR, Andrey V. Elsukov



signature.asc
Description: OpenPGP digital signature

Re: Using GTP and glabel for ZFS arrays

[Jeremy Chadwick]

On Thu, Jul 22, 2010 at 02:32:48AM -0400, Dan Langille wrote:
> On 7/21/2010 11:39 PM, Adam Vande More wrote:
> >On Wed, Jul 21, 2010 at 10:34 PM, Adam Vande More  >> wrote:
> 
> >Also if you have an applicable SATA controller, running the ahci module
> >with give you more speed.  Only change one thing a time though.
> >Virtualbox makes a great testbed for this, you don't need to allocate
> >the VM a lot of RAM just make sure it boots and such.
> 
> I'm not sure of the criteria, but this is what I'm running:
> 
> atapci0:  port 0xdc00-0xdc0f mem
> 0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on
> pci7
> 
> atapci1:  port 0xac00-0xac0f mem
> 0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on
> pci3
> 
> I added ahci_load="YES" to loader.conf and rebooted.  Now I see:
> 
> ahci0:  port
> 0x8000-0x8007,0x7000-0x7003,0x6000-0x6007,0x5000-0x5003,0x4000-0x400f
> mem 0xfb3fe400-0xfb3fe7ff irq 22 at device 17.0 on pci0
> 
> Which is the onboard SATA from what I can tell, not the controllers
> I installed to handle the ZFS array.  The onboard SATA runs a
> gmirror array which handles /, /tmp, /usr, and /var (i.e. the OS).
> ZFS runs only on on my /storage mount point.

The Silicon Image controllers have their own driver, siis(4), which uses
AHCI as well.  It's just as reliable as ahci(4), and undergoes
similar/thorough testing.

-- 
| 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 |

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Dan Langille]

On 7/22/2010 2:59 AM, Andrey V. Elsukov wrote:

On 22.07.2010 10:32, Dan Langille wrote:

I'm not sure of the criteria, but this is what I'm running:

atapci0:  port 0xdc00-0xdc0f mem
0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on pci7

atapci1:  port 0xac00-0xac0f mem
0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on pci3

I added ahci_load="YES" to loader.conf and rebooted.  Now I see:


You can add siis_load="YES" to loader.conf for SiI 3124.


Ahh, thank you.

I'm afraid to do that now, before I label my ZFS drives for fear that 
the ZFS array will be messed up.  But I do plan to do that for the 
system after my plan is implemented.  Thank you.  :)


--
Dan Langille - http://langille.org/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Jeremy Chadwick]

On Thu, Jul 22, 2010 at 03:02:33AM -0400, Dan Langille wrote:
> On 7/22/2010 2:59 AM, Andrey V. Elsukov wrote:
> >On 22.07.2010 10:32, Dan Langille wrote:
> >>I'm not sure of the criteria, but this is what I'm running:
> >>
> >>atapci0:  port 0xdc00-0xdc0f mem
> >>0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on pci7
> >>
> >>atapci1:  port 0xac00-0xac0f mem
> >>0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on pci3
> >>
> >>I added ahci_load="YES" to loader.conf and rebooted.  Now I see:
> >
> >You can add siis_load="YES" to loader.conf for SiI 3124.
> 
> Ahh, thank you.
> 
> I'm afraid to do that now, before I label my ZFS drives for fear
> that the ZFS array will be messed up.  But I do plan to do that for
> the system after my plan is implemented.  Thank you.  :)

They won't be messed up.  ZFS will figure out, using its metadata, which
drive is part of what pool despite the device name changing.  I don't
use glabel or GPT so I can't comment on whether or not those work
reliably in this situation (I imagine they would, but I keep seeing
problem reports on the lists when people have them in use...)

-- 
| 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 |

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Dan Langille]

On 7/22/2010 3:08 AM, Jeremy Chadwick wrote:

On Thu, Jul 22, 2010 at 03:02:33AM -0400, Dan Langille wrote:

On 7/22/2010 2:59 AM, Andrey V. Elsukov wrote:

On 22.07.2010 10:32, Dan Langille wrote:

I'm not sure of the criteria, but this is what I'm running:

atapci0:   port 0xdc00-0xdc0f mem
0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on pci7

atapci1:   port 0xac00-0xac0f mem
0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on pci3

I added ahci_load="YES" to loader.conf and rebooted.  Now I see:


You can add siis_load="YES" to loader.conf for SiI 3124.


Ahh, thank you.

I'm afraid to do that now, before I label my ZFS drives for fear
that the ZFS array will be messed up.  But I do plan to do that for
the system after my plan is implemented.  Thank you.  :)


They won't be messed up.  ZFS will figure out, using its metadata, which
drive is part of what pool despite the device name changing.


I now have:
siis0:  port 0xdc00-0xdc0f mem 
0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on pci7


siis1:  port 0xac00-0xac0f mem 
0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on pci3


And my zpool is now:

$ zpool status
  pool: storage
 state: ONLINE
 scrub: none requested
config:

NAMESTATE READ WRITE CKSUM
storage ONLINE   0 0 0
  raidz1ONLINE   0 0 0
ada0ONLINE   0 0 0
ada1ONLINE   0 0 0
ada2ONLINE   0 0 0
ada3ONLINE   0 0 0
ada4ONLINE   0 0 0

Whereas previously, it was ad devices (see 
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=399538+0+current/freebsd-stable).


Thank you (and to Andrey V. Elsukov who posted the same suggestion at 
the same time you did).  I appreciate it.


> I don't

use glabel or GPT so I can't comment on whether or not those work
reliably in this situation (I imagine they would, but I keep seeing
problem reports on the lists when people have them in use...)


Really?  The whole basis of the action plan I'm highlighting in this 
post is to avoid ZFS-related problems when devices get renumbered and 
ZFS is using device names (e.g. /dev/ad0> instead of labels (e.g. 
gpt/disk00).


--
Dan Langille - http://langille.org/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Charles Sprickman]

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 2:59 AM, Andrey V. Elsukov wrote:

On 22.07.2010 10:32, Dan Langille wrote:

I'm not sure of the criteria, but this is what I'm running:

atapci0:  port 0xdc00-0xdc0f mem
0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on pci7

atapci1:  port 0xac00-0xac0f mem
0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on pci3

I added ahci_load="YES" to loader.conf and rebooted.  Now I see:


You can add siis_load="YES" to loader.conf for SiI 3124.


Ahh, thank you.

I'm afraid to do that now, before I label my ZFS drives for fear that the ZFS 
array will be messed up.  But I do plan to do that for the system after my 
plan is implemented.  Thank you.  :)


You may even get hotplug support if you're lucky. :)

I just built a box and gave it a spin with the "old" ata stuff and then 
with the "new" (AHCI) stuff.  It does perform a bit better and my BIOS 
claims it supports hotplug with ahci enabled as well...  Still have to 
test that.


Charles


--
Dan Langille - http://langille.org/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Dan Langille]

On 7/22/2010 3:30 AM, Charles Sprickman wrote:

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 2:59 AM, Andrey V. Elsukov wrote:

On 22.07.2010 10:32, Dan Langille wrote:

I'm not sure of the criteria, but this is what I'm running:

atapci0: port 0xdc00-0xdc0f mem
0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on
pci7

atapci1: port 0xac00-0xac0f mem
0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on
pci3

I added ahci_load="YES" to loader.conf and rebooted. Now I see:


You can add siis_load="YES" to loader.conf for SiI 3124.


Ahh, thank you.

I'm afraid to do that now, before I label my ZFS drives for fear that
the ZFS array will be messed up. But I do plan to do that for the
system after my plan is implemented. Thank you. :)


You may even get hotplug support if you're lucky. :)

I just built a box and gave it a spin with the "old" ata stuff and then
with the "new" (AHCI) stuff. It does perform a bit better and my BIOS
claims it supports hotplug with ahci enabled as well... Still have to
test that.


Well, I don't have anything to support hotplug.  All my stuff is internal.

http://sphotos.ak.fbcdn.net/hphotos-ak-ash1/hs430.ash1/23778_106837706002537_10289239443_171753_3508473_n.jpg



--
Dan Langille - http://langille.org/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Charles Sprickman]

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 3:30 AM, Charles Sprickman wrote:

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 2:59 AM, Andrey V. Elsukov wrote:

On 22.07.2010 10:32, Dan Langille wrote:

I'm not sure of the criteria, but this is what I'm running:

atapci0: port 0xdc00-0xdc0f mem
0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on
pci7

atapci1: port 0xac00-0xac0f mem
0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on
pci3

I added ahci_load="YES" to loader.conf and rebooted. Now I see:


You can add siis_load="YES" to loader.conf for SiI 3124.


Ahh, thank you.

I'm afraid to do that now, before I label my ZFS drives for fear that
the ZFS array will be messed up. But I do plan to do that for the
system after my plan is implemented. Thank you. :)


You may even get hotplug support if you're lucky. :)

I just built a box and gave it a spin with the "old" ata stuff and then
with the "new" (AHCI) stuff. It does perform a bit better and my BIOS
claims it supports hotplug with ahci enabled as well... Still have to
test that.


Well, I don't have anything to support hotplug.  All my stuff is internal.

http://sphotos.ak.fbcdn.net/hphotos-ak-ash1/hs430.ash1/23778_106837706002537_10289239443_171753_3508473_n.jpg


The frankenbox I'm testing on is a retrofitted 1U (it had a scsi 
backplane, now has none).


I am not certain, but I think with 8.1 (which it's running) and all the 
cam integration stuff, hotplug is possible.  Is a special backplane 
required?  I seriously don't know...  I'm going to give it a shot though.


Oh, you also might get NCQ.  Try:

[r...@h21 /tmp]# camcontrol tags ada0
(pass0:ahcich0:0:0:0): device openings: 32

Charles




--
Dan Langille - http://langille.org/


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Dan Langille]

On 7/22/2010 4:03 AM, Charles Sprickman wrote:

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 3:30 AM, Charles Sprickman wrote:

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 2:59 AM, Andrey V. Elsukov wrote:

On 22.07.2010 10:32, Dan Langille wrote:

I'm not sure of the criteria, but this is what I'm running:

atapci0: port 0xdc00-0xdc0f mem
0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on
pci7

atapci1: port 0xac00-0xac0f mem
0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on
pci3

I added ahci_load="YES" to loader.conf and rebooted. Now I see:


You can add siis_load="YES" to loader.conf for SiI 3124.


Ahh, thank you.

I'm afraid to do that now, before I label my ZFS drives for fear that
the ZFS array will be messed up. But I do plan to do that for the
system after my plan is implemented. Thank you. :)


You may even get hotplug support if you're lucky. :)

I just built a box and gave it a spin with the "old" ata stuff and then
with the "new" (AHCI) stuff. It does perform a bit better and my BIOS
claims it supports hotplug with ahci enabled as well... Still have to
test that.


Well, I don't have anything to support hotplug. All my stuff is internal.

http://sphotos.ak.fbcdn.net/hphotos-ak-ash1/hs430.ash1/23778_106837706002537_10289239443_171753_3508473_n.jpg



The frankenbox I'm testing on is a retrofitted 1U (it had a scsi
backplane, now has none).

I am not certain, but I think with 8.1 (which it's running) and all the
cam integration stuff, hotplug is possible. Is a special backplane
required? I seriously don't know... I'm going to give it a shot though.

Oh, you also might get NCQ. Try:

[r...@h21 /tmp]# camcontrol tags ada0
(pass0:ahcich0:0:0:0): device openings: 32


# camcontrol tags ada0
(pass0:siisch2:0:0:0): device openings: 31


--
Dan Langille - http://langille.org/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Dan Langille]

On 7/22/2010 4:03 AM, Charles Sprickman wrote:

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 3:30 AM, Charles Sprickman wrote:

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 2:59 AM, Andrey V. Elsukov wrote:

On 22.07.2010 10:32, Dan Langille wrote:

I'm not sure of the criteria, but this is what I'm running:

atapci0: port 0xdc00-0xdc0f mem
0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on
pci7

atapci1: port 0xac00-0xac0f mem
0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on
pci3

I added ahci_load="YES" to loader.conf and rebooted. Now I see:


You can add siis_load="YES" to loader.conf for SiI 3124.


Ahh, thank you.

I'm afraid to do that now, before I label my ZFS drives for fear that
the ZFS array will be messed up. But I do plan to do that for the
system after my plan is implemented. Thank you. :)


You may even get hotplug support if you're lucky. :)

I just built a box and gave it a spin with the "old" ata stuff and then
with the "new" (AHCI) stuff. It does perform a bit better and my BIOS
claims it supports hotplug with ahci enabled as well... Still have to
test that.


Well, I don't have anything to support hotplug. All my stuff is internal.

http://sphotos.ak.fbcdn.net/hphotos-ak-ash1/hs430.ash1/23778_106837706002537_10289239443_171753_3508473_n.jpg



The frankenbox I'm testing on is a retrofitted 1U (it had a scsi
backplane, now has none).

I am not certain, but I think with 8.1 (which it's running) and all the
cam integration stuff, hotplug is possible. Is a special backplane
required? I seriously don't know... I'm going to give it a shot though.

Oh, you also might get NCQ. Try:

[r...@h21 /tmp]# camcontrol tags ada0
(pass0:ahcich0:0:0:0): device openings: 32


# camcontrol tags ada0
(pass0:siisch2:0:0:0): device openings: 31

resending with this:

ada{0..4} give the above.

# camcontrol tags ada5
(pass5:ahcich0:0:0:0): device openings: 32

That's part of the gmirror array for the OS, along with ad6 which has 
similar output.


--
Dan Langille - http://langille.org/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Dan Langille]

On 7/22/2010 4:03 AM, Charles Sprickman wrote:

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 3:30 AM, Charles Sprickman wrote:

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 2:59 AM, Andrey V. Elsukov wrote:

On 22.07.2010 10:32, Dan Langille wrote:

I'm not sure of the criteria, but this is what I'm running:

atapci0: port 0xdc00-0xdc0f mem
0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on
pci7

atapci1: port 0xac00-0xac0f mem
0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on
pci3

I added ahci_load="YES" to loader.conf and rebooted. Now I see:


You can add siis_load="YES" to loader.conf for SiI 3124.


Ahh, thank you.

I'm afraid to do that now, before I label my ZFS drives for fear that
the ZFS array will be messed up. But I do plan to do that for the
system after my plan is implemented. Thank you. :)


You may even get hotplug support if you're lucky. :)

I just built a box and gave it a spin with the "old" ata stuff and then
with the "new" (AHCI) stuff. It does perform a bit better and my BIOS
claims it supports hotplug with ahci enabled as well... Still have to
test that.


Well, I don't have anything to support hotplug. All my stuff is internal.

http://sphotos.ak.fbcdn.net/hphotos-ak-ash1/hs430.ash1/23778_106837706002537_10289239443_171753_3508473_n.jpg



The frankenbox I'm testing on is a retrofitted 1U (it had a scsi
backplane, now has none).

I am not certain, but I think with 8.1 (which it's running) and all the
cam integration stuff, hotplug is possible. Is a special backplane
required? I seriously don't know... I'm going to give it a shot though.

Oh, you also might get NCQ. Try:

[r...@h21 /tmp]# camcontrol tags ada0
(pass0:ahcich0:0:0:0): device openings: 32


# camcontrol tags ada0
(pass0:siisch2:0:0:0): device openings: 31

resending with this:

ada{0..4} give the above.

# camcontrol tags ada5
(pass5:ahcich0:0:0:0): device openings: 32

That's part of the gmirror array for the OS, along with ad6 which has 
similar output.


And again with this output from one of the ZFS drives:

# camcontrol identify ada0
pass0:  ATA-8 SATA 2.x device
pass0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)

protocol  ATA/ATAPI-8 SATA 2.x
device model  Hitachi HDS722020ALA330
firmware revision JKAOA28A
serial number JK1130YAH531ST
WWN   5000cca221d068d5
cylinders 16383
heads 16
sectors/track 63
sector size   logical 512, physical 512, offset 0
LBA supported 268435455 sectors
LBA48 supported   3907029168 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM 7200

Feature  Support  EnableValue   Vendor
read ahead yes  yes
write cacheyes  yes
flush cacheyes  yes
overlapno
Tagged Command Queuing (TCQ)   no   no
Native Command Queuing (NCQ)   yes  32 tags
SMART  yes  yes
microcode download yes  yes
security   yes  no
power management   yes  yes
advanced power management  yes  no  0/0x00
automatic acoustic management  yes  no  254/0xFE128/0x80
media status notification  no   no
power-up in Standbyyes  no
write-read-verify  no   no  0/0x0
unload no   no
free-fall  no   no
data set management (TRIM) no


--
Dan Langille - http://langille.org/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Jeremy Chadwick]

On Thu, Jul 22, 2010 at 04:03:05AM -0400, Charles Sprickman wrote:
> On Thu, 22 Jul 2010, Dan Langille wrote:
> >Well, I don't have anything to support hotplug.  All my stuff is internal.
> >
> >http://sphotos.ak.fbcdn.net/hphotos-ak-ash1/hs430.ash1/23778_106837706002537_10289239443_171753_3508473_n.jpg
> 
> The frankenbox I'm testing on is a retrofitted 1U (it had a scsi
> backplane, now has none).
> 
> I am not certain, but I think with 8.1 (which it's running) and all
> the cam integration stuff, hotplug is possible.  Is a special
> backplane required?  I seriously don't know...  I'm going to give it
> a shot though.

Yes, a special backplane is required.
 
> Oh, you also might get NCQ.  Try:
> 
> [r...@h21 /tmp]# camcontrol tags ada0
> (pass0:ahcich0:0:0:0): device openings: 32

NCQ should be enabled by default.  "camcontrol identify" will provide
much more verbose details about the state of these disks.  Don't confuse
"identify" with "inquiry".

-- 
| 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 |

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Boris Samorodov]

On Wed, 21 Jul 2010 23:15:41 -0400 Dan Langille wrote:
> On 7/21/2010 11:05 PM, Dan Langille wrote (something close to this):

> > First, create a new GUID Partition Table partition scheme on the HDD:
> > gpart create -s GPT ad0
> >
> > Let's see how much space we have. This output will be used to determine
> > SOMEVALUE in the next command.
> >
> > gpart show
> >
> > Create a new partition within that scheme:
> > gpart add -b 34 -s SOMEVALUE -t freebsd-zfs ad0
> >
> > Now, label the thing:
> > glabel label -v disk00 /dev/ad0

That command will destroy secondary GPT.

> Or, is this more appropriate?
>   glabel label -v disk00 /dev/ad0s1

-- 
WBR, Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Charles Sprickman]

On Thu, 22 Jul 2010, Boris Samorodov wrote:


On Wed, 21 Jul 2010 23:15:41 -0400 Dan Langille wrote:

On 7/21/2010 11:05 PM, Dan Langille wrote (something close to this):



First, create a new GUID Partition Table partition scheme on the HDD:
gpart create -s GPT ad0

Let's see how much space we have. This output will be used to determine
SOMEVALUE in the next command.

gpart show

Create a new partition within that scheme:
gpart add -b 34 -s SOMEVALUE -t freebsd-zfs ad0

Now, label the thing:
glabel label -v disk00 /dev/ad0


That command will destroy secondary GPT.


I was just reading about GUID partitioning last night and saw that one of 
the benefits is that there's a copy of the partition table kept at the end 
of the disk.  That seems like a pretty neat feature.


Do you by any chance have a reference I can point to (I was documenting 
stuff about GPT in an internal wiki and this is a nice piece of info to 
have)?


Also, how does one access/use the "backup" partition table?

Thanks,

Charles


Or, is this more appropriate?
  glabel label -v disk00 /dev/ad0s1


--
WBR, Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Boris Samorodov]

Charles Sprickman  writes:
> On Thu, 22 Jul 2010, Boris Samorodov wrote:
>> On Wed, 21 Jul 2010 23:15:41 -0400 Dan Langille wrote:
>>> On 7/21/2010 11:05 PM, Dan Langille wrote (something close to this):
>>
 First, create a new GUID Partition Table partition scheme on the HDD:
 gpart create -s GPT ad0

 Let's see how much space we have. This output will be used to determine
 SOMEVALUE in the next command.

 gpart show

 Create a new partition within that scheme:
 gpart add -b 34 -s SOMEVALUE -t freebsd-zfs ad0

 Now, label the thing:
 glabel label -v disk00 /dev/ad0
>>
>> That command will destroy secondary GPT.
>
> I was just reading about GUID partitioning last night and saw that one
> of the benefits is that there's a copy of the partition table kept at
> the end of the disk.  That seems like a pretty neat feature.
>
> Do you by any chance have a reference I can point to (I was
> documenting stuff about GPT in an internal wiki and this is a nice
> piece of info to have)?
>
> Also, how does one access/use the "backup" partition table?

http://en.wikipedia.org/wiki/GUID_Partition_Table

-- 
WBR, bsam
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Changes to ipfw in 8.1

[Ian Smith]

On Wed, 21 Jul 2010, Spil Oss wrote:
 > Hi Sergey,
 > 
 > I'm dumbstruck!
 > 
 > Switching 'ip' to 'ip4' in both the divert rules fixed my problem.
 > Personally I think that should go into the UPDATING file as well. I
 > wouldn't have found it if you hadn't told me!
 > 
 > Many thanks,
 > 
 > Spil.

This points to a number of issues, not least the effect of people being 
led to using the currently dreadful IPFW section of the handbook, which 
contains so many conceptual and factual errors that I really don't know 
where to begin on a solution .. so I won't discuss that further except 
as it relates to the actual ruleset you're using.

In your just-filed PR http://www.freebsd.org/cgi/query-pr.cgi?pr=148827 
you say your ruleset is based on '30.6.5.7 An Example NAT and Stateful 
Ruleset', so I'm assuming it's broadly based on example #2 there.

 > On Wed, Jul 21, 2010 at 9:08 PM, Spil Oss  wrote:
 > > Hi Sergey,
 > >
 > > Has the change from ip to ip4 solved the problem for you? The
 > > documentation states that proto 'ip' is the same as 'all' "Matches any
 > > packet."
 > >
 > > Rule # 60
 > >     $cmd 060 skipto 1000 ip6 from any to any
 > > will have already skipped to the ipv6 rules block thus proto 'ip'
 > > should always match remaining packets.

You don't show any rules beyond number 510, so we must take it on faith 
that you're handling your ip6 traffic appropriately.  I don't know much 
about it, and will be guided by the IPv6 rules lately in rc.firewall.

However if natd is barfing on being passed ip6 packets, that should be 
fixed in natd, which should do nothing with packets it doesn't care 
about - as it does with ip4 packets not eligible for NAT translation - 
except to re-enter the firewall at the next higher-numbered rule, which 
of course relies on sysctl net.inet.ip.fw.one_pass being set to 0.

Either that or ipfw should explicitly decline to divert non-ip4 traffic.
I don't know whether or how this would also affect ipfw in-kernel nat.

If in fact no ip6 packets are being passed to natd as rule 60 indicates, 
at least for traffic inbound to ipfw, then that is indeed strange, but I 
suspect that on the outbound pass, using this rather confusing 'skipto 
500 .. keep-state' logic, perhaps some outbound ip6 packets may have 
been being passed to natd ..

Could you check to see if it works only changing the _outbound_ divert 
rule from ip to ip4, leaving the inbound one at 'ip'?  If so, this would 
validate your original theory re rule 60, on the inbound pass.  If not, 
it may be a useful data point for resolving the problem.

 > > Meanwhile I found bug 148137 [ipfw] call order of natd and ipfw startup 
 > > scripts
 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=148137&cat=conf
 > > Don't know if that's directly related, but it may be worth a try to
 > > revert back to the RELENG_8_0 script.
 > >
 > > Will let you now my findings.

Did you try that, to see whether it was an issue?  More below ..

 > > Kind regards,
 > >
 > > Spil.
 > >
 > >
 > > On Wed, Jul 21, 2010 at 2:57 PM, Sergey G Nasonov  wrote:
 > >> Hello Spill,
 > >>
 > >> I have get the same trouble after updating my 8.0 Stable. I thing you need
 > >> modify some firewall rules.
 > >>
 > >> Please change
 > >>
 > >> $cmd 100 divert natd ip from any to any in via $pif # Mangle inbound
 > >>
 > >> to
 > >>
 > >> $cmd 100 divert natd ip4 from any to any in via $pif # Mangle inbound
 > >>
 > >> and
 > >>
 > >> $cmd 500 divert natd ip from any to any out via $pif
 > >>
 > >> to
 > >>
 > >> $cmd 500 divert natd ip4 from any to any out via $pif
 > >>
 > >> accordingly.
 > >>
 > >> --
 > >>
 > >> Best Regards,
 > >>
 > >> Nasonov Sergey
 > >
 > >
 > > On Wed, Jul 21, 2010 at 11:40 AM, Spil Oss  wrote:
 > >> Hi,
 > >>
 > >> Testing FreeBSD 8.1 I noticed that I seem to have routing or nat or
 > >> firewall issues. (csupped RELENG_8_1 which was -RELEASE not -RC last
 > >> night?)
 > >> - 8.1 booted fine
 > >> - connections from the system itself were fine
 > >> - connections from my jails to the internet were not working
 > >> - connections from my LAN/WLAN to the internet were not working
 > >> Reverting back to 8.0-p2 with the same configuration works fine.
 > >>
 > >> In UPDATING I see that rc.firewall and rc.firewall6 were unified.
 > >>
 > >> Setup is
 > >> - xl0 connected to internet/public IP via dhcp
 > >> - bge0/wlan0(ath0) connected to LAN
 > >> - jails have ip's on bge0 in the same subnet as the LAN
 > >> - allow all from any to any via bge0|wlan0|lo0

The latter point looks problematic, see below.

 > >> - NAT using natd
 > >>
 > >> My guess is that something's changed to ipfw that is affecting my
 > >> network settings. Any clues where I went wrong?
 > >>
 > >> Help appreciated/ Kind regards,
 > >>
 > >> Spil.
 > >>
 > >> rc.conf:
 > >> firewall_enable="YES"
 > >> firewall_script="/etc/ipfw.rules"
 > >>
 > >> natd.conf
 > >> interface xl0
 > >> dynamic yes
 > >> same_ports yes
 > >> # http/https to http jail
 > >> redirect_port t

Re: Using GTP and glabel for ZFS arrays

[Daniel O'Connor]

On 22/07/2010, at 12:35, Dan Langille wrote:
> Why use glabel?
> 
> * So ZFS can find and use the correct HDD should the HDD device ever
>   get renumbered for whatever reason.  e.g. /dev/da0 becomes /dev/da6
>   when you move it to another controller.
> 
> Why use partitions?
> 
> * Primarily: two HDD of a given size, say 2TB, do not always provide
>   the same amount of available space.  If you use a slightly smaller
>   partition instead of the entire physical HDD, you're much more
>   likely to have a happier experience when it comes time to replace an
>   HDD.
> 
> * There seems to be a consensus amongst some that leaving the start and
>   and of your HDD empty.  Give the rest to ZFS.

I would combine both!

GPT generates a UUID for each partition and glabel presents this so ZFS can use 
it, eg I have..
[cain 19:45] ~ >sudo zpool status
  pool: tank
 state: ONLINE
 scrub: none requested
config:

NAMESTATE READ WRITE 
CKSUM
tankONLINE   0 0
 0
  raidz2ONLINE   0 0
 0
gptid/d7467802-418f-11df-bcfc-001517e077fb  ONLINE   0 0
 0
gptid/d7eeeced-418f-11df-bcfc-001517e077fb  ONLINE   0 0
 0
gptid/d8761aa0-418f-11df-bcfc-001517e077fb  ONLINE   0 0
 0
gptid/d9083d18-418f-11df-bcfc-001517e077fb  ONLINE   0 0
 0
gptid/d97203ec-418f-11df-bcfc-001517e077fb  ONLINE   0 0
 0

and on each disk..
[cain 19:46] ~ >gpart list ada0   
Geom name: ada0
fwheads: 16
fwsectors: 63
last: 1953525134
first: 34
entries: 128
scheme: GPT
Providers:
1. Name: ada0p1
   Mediasize: 8589934592 (8.0G)
   Sectorsize: 512
   Mode: r0w0e0
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 8589934592
   offset: 17408
   type: freebsd-swap
   index: 1
   end: 16777249
   start: 34
2. Name: ada0p2
   Mediasize: 991614917120 (924G)
   Sectorsize: 512
   Mode: r1w1e2
   rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 991614917120
   offset: 8589952000
   type: freebsd-zfs
   index: 2
   end: 1953525134
   start: 16777250
Consumers:
1. Name: ada0
   Mediasize: 1000204886016 (932G)
   Sectorsize: 512
   Mode: r1w1e3

The only tedious part is working out which drive has what UUIDs on it because 
gpart doesn't list them.

The advantage of using the UUIDs is that if you setup another machine the same 
way you don't have to worry about things when you plug in the disks from it to 
recover something. Or perhaps you are upgrading at the same time as replacing 
hardware so you have all the disks in at once.

> Create a new partition within that scheme:
> 
>  gpart add -b 34 -s SOMEVALUE -t freebsd-zfs ad0
> 
> Why '-b 34'?  Randi pointed me to 
> http://en.wikipedia.org/wiki/GUID_Partition_Table where it explains what the 
> first 33 LBA are used for.  It's not for us to use here.

If you don't specify -b it will DTRT - that's how I did it.

You can also specify the size (and start) in human units (Gb etc).

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C






___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Daniel O'Connor]

On 22/07/2010, at 13:59, Adam Vande More wrote:
> To be clear, we are talking about data partitions, not the boot one.
> Difficult for me to explain concisely, but basically it has to do with seek
> time.  A mis-aligned partition will almost always have an extra seek for
> each standard seek you'd have on aligned one.  There have been some
> discussions about in the archives, also this is not unique to FreeBSD so
> google will have a more detailed and probably better explanation.

Newer disks have 4kb sectors internally at least, and some expose it to the OS.

If you create your partitions unaligned to this every read and write will 
involve at least one more sector than it would otherwise and that hurts 
performance.

The disks which don't expose it have a jumper which offsets all accesses to 
Windows XP's performance doesn't take a dive but I'm not sure if that helps 
FreeBSD.

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C






___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Paul Mather]

On Jul 21, 2010, at 11:05 PM, Dan Langille wrote:

> I hope my terminology is correct
> 
> I have a ZFS array which uses raw devices.  I'd rather it use glabel and 
> supply the GEOM devices to ZFS instead.  In addition, I'll also partition the 
> HDD to avoid using the entire HDD: leave a little bit of space at the start 
> and end.
> 
> Why use glabel?
> 
> * So ZFS can find and use the correct HDD should the HDD device ever
>   get renumbered for whatever reason.  e.g. /dev/da0 becomes /dev/da6
>   when you move it to another controller.

I have created ZFS pools using this strategy.  However, about a year ago I 
still fell foul of the drive shuffling problem, when GEOM labels appeared not 
to be detected properly:

http://lists.freebsd.org/pipermail/freebsd-geom/2009-July/003654.html

This was using RELENG_7, and the problem was provoked by external USB drives.

The same issue might not occur with FreeBSD 8.x, but I thought I'd point out my 
experience as a possible warning about using glabel.

Nowadays, I use GPT labels ("gpart ... -l somelabel", referenced via 
/dev/gpt/somelabel).

> Why use partitions?
> 
> * Primarily: two HDD of a given size, say 2TB, do not always provide
>   the same amount of available space.  If you use a slightly smaller
>   partition instead of the entire physical HDD, you're much more
>   likely to have a happier experience when it comes time to replace an
>   HDD.
> 
> * There seems to be a consensus amongst some that leaving the start and
>   and of your HDD empty.  Give the rest to ZFS.

You should also try and accommodate 4K sector size drives these days.  
Apparently, the performance boosts from hitting 4K-aligned sectors can be very 
good.

Cheers,

Paul.___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Volodymyr Kostyrko]

22.07.2010 06:05, Dan Langille wrote:

Create a new partition within that scheme:

gpart add -b 34 -s SOMEVALUE -t freebsd-zfs ad0

Why '-b 34'? Randi pointed me to
http://en.wikipedia.org/wiki/GUID_Partition_Table where it explains what
the first 33 LBA are used for. It's not for us to use here.


gpart is not so dumb to not protect this space. If you don't specify -b 
when creating first partition it automagically defaults to 34.


--
Sphinx of black quartz judge my vow.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

vuxml alert - mDNS - patch available in bug tracking system

[Oliver Pinter]

For a month ago every day become an portaudit alert, that the mdnsd is
still vulnerable. The fix is available since ~1 month

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/147007
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Unable to install 8.x on a PowerEdge R810

[Mahlon E. Smith]

Picked up a couple of these powerhouse machines to be VirtualBox hosts.
24 core, 96G of RAM.  Trying to put (amd64) both 8.0-RELEASE and 8.1-RC2
on it with no luck whatsoever so far. Any help provided would be greatly
appreciated, I'm chomping at the bit pretty hard to put this hardware to
use, and was fairly surprised that FreeBSD didn't work on it through the
gate.

I've grabbed some screenshots from the DRAC, and dumped them here:

http://www.dropbox.com/gallery/7234177/1/r810?h=f5fb1d

(sorry, I realize that's not -incredibly- helpful and partially
truncated.  I'm currently limited to what I can screenshot, though I
suppose I could boot via console and log it all... come to think of it,
I'll go give that a try to get more comprehensive output.)

If I disable all the CPU options in the BIOS, I can get it to boot, but
it hangs after mounting md0 (I never see the sysinstall screen.)  Same
deal if I try booting in safe mode or without ACPI.

Otherwise, it spews errors for about 30 seconds so quickly I can't read
them, then panics with a page fault in swapper.

I'm sure we'd like to get BSD installing reliably on such a beast, and
I'm more than happy to play the guinea pig if someone would be willing
to provide some direction with some things to try.  Help!  These are
expensive paperweights!  :)

--
Mahlon E. Smith  
http://www.martini.nu/contact.html


pgphh6T0BkFOk.pgp
Description: PGP signature

Re: Unable to install 8.x on a PowerEdge R810

[Sean Bruno]

On Thu, 2010-07-22 at 14:38 -0700, Mahlon E. Smith wrote:
> Picked up a couple of these powerhouse machines to be VirtualBox hosts.
> 24 core, 96G of RAM.  Trying to put (amd64) both 8.0-RELEASE and 8.1-RC2
> on it with no luck whatsoever so far. Any help provided would be greatly
> appreciated, I'm chomping at the bit pretty hard to put this hardware to
> use, and was fairly surprised that FreeBSD didn't work on it through the
> gate.
> 
> I've grabbed some screenshots from the DRAC, and dumped them here:
> 
> http://www.dropbox.com/gallery/7234177/1/r810?h=f5fb1d
> 
> (sorry, I realize that's not -incredibly- helpful and partially
> truncated.  I'm currently limited to what I can screenshot, though I
> suppose I could boot via console and log it all... come to think of it,
> I'll go give that a try to get more comprehensive output.)
> 
> If I disable all the CPU options in the BIOS, I can get it to boot, but
> it hangs after mounting md0 (I never see the sysinstall screen.)  Same
> deal if I try booting in safe mode or without ACPI.
> 
> Otherwise, it spews errors for about 30 seconds so quickly I can't read
> them, then panics with a page fault in swapper.
> 
> I'm sure we'd like to get BSD installing reliably on such a beast, and
> I'm more than happy to play the guinea pig if someone would be willing
> to provide some direction with some things to try.  Help!  These are
> expensive paperweights!  :)
> 
> --
> Mahlon E. Smith  
> http://www.martini.nu/contact.html


Funny you should mention this box.  I've been arm wrestling with this
beastie for a couple of weeks and finally had some amount of success
today.

A couple of things:

1.  Reduce your RAM to 64G (seriously)
2.  Don't use the H200 Dell RAID controller.  It's not supported yet.
 -- Use the 6i or whatever the mfi(4) card is called.
3.  Don't compile in the ipmi(4) when you get the system up.
 -- I know there's an unpatched problem on 7 that is fixed in HEAD, but
have no idea if its patched in 8
4.  Try doing serial console installs. 
 -- at the Beastie prompt, hit [6]. then at the OK prompt, type "set   
console=comconsole"

Sean

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Unable to install 8.x on a PowerEdge R810

[Mahlon E. Smith]

On Thu, Jul 22, 2010, Mahlon E. Smith wrote:
> 
> [...]
> I suppose I could boot via console and log it all... come to think of
> it, I'll go give that a try to get more comprehensive output

Okay, here we go, output below my sig.

"panic: Built bad topology" -- oh, dear.  That's a new one for me.

Clues/suggestions happily accepted.

--
Mahlon E. Smith  
http://www.martini.nu/contact.html



OK boot -v
SMAP type=01 base= len=000a
SMAP type=01 base=0010 len=7f538000
SMAP type=02 base=7f638000 len=00016000
SMAP type=03 base=7f64e000 len=0007f000
SMAP type=02 base=7f6cd000 len=00933000
SMAP type=02 base=8000 len=1000
SMAP type=02 base=f17f len=2000
SMAP type=02 base=fe00 len=0200
SMAP type=01 base=0001 len=00178000
Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.1-RC2 #0: Tue Jun 29 20:21:55 UTC 2010
r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
Preloaded elf kernel "/boot/kernel/kernel" at 0x8126c000.
Preloaded mfs_root "/boot/mfsroot" at 0x8126c1d0.
Timecounter "i8254" frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 1995012507 Hz
CPU: Intel(R) Xeon(R) CPU   E7540  @ 2.00GHz (1995.01-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x206e6  Family = 6  Model = 2e  Stepping = 6
  
Features=0xbfebfbff
  
Features2=0xbce3bd
  AMD Features=0x28100800
  AMD Features2=0x1
  TSC: P-state invariant
real memory  = 103079215104 (98304 MB)
Physical memory chunk(s):
0x1000 - 0x0009bfff, 634880 bytes (155 pages)
0x012f8000 - 0x7f637fff, 2117337088 bytes (516928 pages)
0x0001 - 0x0017c7d9, 97842233344 bytes (23887264 pages)
avail memory = 99488772096 (94879 MB)
ACPI APIC Table: 
INTR: Adding local APIC 1 as a target
INTR: Adding local APIC 4 as a target
INTR: Adding local APIC 5 as a target
INTR: Adding local APIC 6 as a target
INTR: Adding local APIC 7 as a target
INTR: Adding local APIC 16 as a target
INTR: Adding local APIC 17 as a target
INTR: Adding local APIC 18 as a target
INTR: Adding local APIC 19 as a target
INTR: Adding local APIC 22 as a target
INTR: Adding local APIC 23 as a target
INTR: Adding local APIC 32 as a target
INTR: Adding local APIC 33 as a target
INTR: Adding local APIC 36 as a target
INTR: Adding local APIC 37 as a target
INTR: Adding local APIC 38 as a target
INTR: Adding local APIC 39 as a target
INTR: Adding local APIC 48 as a target
INTR: Adding local APIC 49 as a target
INTR: Adding local APIC 50 as a target
INTR: Adding local APIC 51 as a target
INTR: Adding local APIC 54 as a target
INTR: Adding local APIC 55 as a target
INTR: Adding local APIC 64 as a target
INTR: Adding local APIC 65 as a target
INTR: Adding local APIC 68 as a target
INTR: Adding local APIC 69 as a target
INTR: Adding local APIC 70 as a target
INTR: Adding local APIC 71 as a target
INTR: Adding local APIC 80 as a target
INTR: Adding local APIC 81 as a target
FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs
FreeBSD/SMP: 2 package(s) x 6 core(s) x 2 SMT threads
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  4
 cpu3 (AP): APIC ID:  5
 cpu4 (AP): APIC ID:  6
 cpu5 (AP): APIC ID:  7
 cpu6 (AP): APIC ID: 16
 cpu7 (AP): APIC ID: 17
 cpu8 (AP): APIC ID: 18
 cpu9 (AP): APIC ID: 19
 cpu10 (AP): APIC ID: 22
 cpu11 (AP): APIC ID: 23
 cpu12 (AP): APIC ID: 32
 cpu13 (AP): APIC ID: 33
 cpu14 (AP): APIC ID: 36
 cpu15 (AP): APIC ID: 37
 cpu16 (AP): APIC ID: 38
 cpu17 (AP): APIC ID: 39
 cpu18 (AP): APIC ID: 48
 cpu19 (AP): APIC ID: 49
 cpu20 (AP): APIC ID: 50
 cpu21 (AP): APIC ID: 51
 cpu22 (AP): APIC ID: 54
 cpu23 (AP): APIC ID: 55
 cpu24 (AP): APIC ID: 64
 cpu25 (AP): APIC ID: 65
 cpu26 (AP): APIC ID: 68
 cpu27 (AP): APIC ID: 69
 cpu28 (AP): APIC ID: 70
 cpu29 (AP): APIC ID: 71
 cpu30 (AP): APIC ID: 80
 cpu31 (AP): APIC ID: 81
  cpu (AP): APIC ID: 82 (disabled)
  cpu (AP): APIC ID: 83 (disabled)
  cpu (AP): APIC ID: 86 (disabled)
  cpu (AP): APIC ID: 87 (disabled)
  cpu (AP): APIC ID: 96 (disabled)
  cpu (AP): APIC ID: 97 (disabled)
  cpu (AP): APIC ID: 100 (disabled)
  cpu (AP): APIC ID: 101 (disabled)
  cpu (AP): APIC ID: 102 (disabled)
  cpu (AP): APIC ID: 103 (disabled)
  cpu (AP): APIC ID: 112 (disabled)
  cpu (AP): APIC ID: 113 (disabled)
  cpu (AP): APIC ID: 114 (disabled)
  cpu (AP): APIC ID: 115 (disabled)
  cpu (AP): APIC ID: 118 (disabled)
  cpu (AP): APIC ID: 119 (disabled)
APIC: CPU 0 has ACPI ID 1
APIC: CPU 1 has ACPI ID 25
APIC: CPU 2 has ACPI ID 5
APIC: CPU 3 has ACPI ID 29
APIC: CPU 4 has ACPI ID 9
APIC: CPU 5 has ACPI ID 33
APIC: CPU 6 has ACPI ID 13
APIC: CPU 7 has ACPI ID 37

Re: Unable to install 8.x on a PowerEdge R810

[Mahlon E. Smith]

On Thu, Jul 22, 2010, Sean Bruno wrote:
> 
> Funny you should mention this box.  I've been arm wrestling with this
> beastie for a couple of weeks and finally had some amount of success
> today.
> 
> A couple of things:
> 
> 1.  Reduce your RAM to 64G (seriously)
> 2.  Don't use the H200 Dell RAID controller.  It's not supported yet.
>  -- Use the 6i or whatever the mfi(4) card is called.
> 3.  Don't compile in the ipmi(4) when you get the system up.
>  -- I know there's an unpatched problem on 7 that is fixed in HEAD, but
> have no idea if its patched in 8
> 4.  Try doing serial console installs. 
>  -- at the Beastie prompt, hit [6]. then at the OK prompt, type "set   
> console=comconsole"


Thanks for the suggestions, Sean.

On a whim I decided to try with 8.1-RELEASE (since I obviously started
trying to get this goin' before it came out) -- lo, it put me right into
the sysinstall. ... that was an easy fix.  Heh.  (Is kern.smb.disabled
set for the 8.1 install or something?  I didn't change anything
in between attempts.)  In any event -- yay!

Install worked great, though it appears I need to keep hyperthreading
("logical processors" bios option) disabled for it to boot reliably.
Similar errors as before if I enable it.

real memory  = 103079215104 (98304 MB)
avail memory = 99492831232 (94883 MB)
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 24 CPUs
FreeBSD/SMP: 4 package(s) x 6 core(s)

Holy cow, that's a nice sight.

Got one panic shortly after getting it on the network:
http://dl.dropbox.com/u/7234177/panic.jpg

... but it looks like I'll have a lot of kernel and sysctl tweaking to
do regardless ("ix0: RX Descriptors exceed system mbuf max, using default
instead!"), so I'll report back to the list if the panic re-appears after
some tuning.

--
Mahlon E. Smith  
http://www.martini.nu/contact.html


pgpNZgSqwolyt.pgp
Description: PGP signature

Re: Using GTP and glabel for ZFS arrays

[Dan Langille]

Thank you to all the helpful discussion.  It's been very helpful and 
educational.  Based on the advice and suggestions, I'm going to adjust 
my original plan as follows.


NOTE: glabel will not be used.


First, create a new GUID Partition Table partition scheme on the HDD:

gpart create -s GPT ad0


Let's see how much space we have. This output will be used to determine
SOMEVALUE in the next command.

gpart show


Create a new partition within that scheme:

gpart add -b 1024 -s SOMEVALUE -t freebsd-zfs -l disk00 ad0

The -b 1024 ensures alignment on a 4KB boundary.

SOMEVALUE will be set so approximately 200MB is left empty at the end of 
the HDD.  That's part more than necessary to accommodate the different 
actualy size of 2TB HDD.


Repeat the above with ad1 to get disk01. Repeat for all other HDD...

Then create your zpool:

zpool create bigtank gpt/disk00 gpt/disk02 ... etc


This plan will be applied to an existing 5 HDD ZFS pool.  I have two new 
empty HDD which will be added to this new array (giving me 7 x 2TB HDD). 
 The array is raidz1 and I'm wondering if I want to go to raidz2.  That 
would be about 10TB and I'm only using up 3.1TB at present.  That 
represents about 4 months of backups.


I do not think I can adjust the existing zpool on the fly.  I think I 
need to copy everything elsewhere (i.e the 2 empty drives).  Then start 
the new zpool from scratch.


The risk: when the data is on the 2 spare HDD, there is no redundancy. 
I wonder if my friend Jerry has a spare 2TB HDD I could borrow for the 
evening.


--
Dan Langille - http://langille.org/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Unable to install 8.x on a PowerEdge R810

[Pyun YongHyeon]

On Thu, Jul 22, 2010 at 05:36:11PM -0700, Mahlon E. Smith wrote:
> On Thu, Jul 22, 2010, Sean Bruno wrote:
> > 
> > Funny you should mention this box.  I've been arm wrestling with this
> > beastie for a couple of weeks and finally had some amount of success
> > today.
> > 
> > A couple of things:
> > 
> > 1.  Reduce your RAM to 64G (seriously)
> > 2.  Don't use the H200 Dell RAID controller.  It's not supported yet.
> >  -- Use the 6i or whatever the mfi(4) card is called.
> > 3.  Don't compile in the ipmi(4) when you get the system up.
> >  -- I know there's an unpatched problem on 7 that is fixed in HEAD, but
> > have no idea if its patched in 8
> > 4.  Try doing serial console installs. 
> >  -- at the Beastie prompt, hit [6]. then at the OK prompt, type "set   
> > console=comconsole"
> 
> 
> Thanks for the suggestions, Sean.
> 
> On a whim I decided to try with 8.1-RELEASE (since I obviously started
> trying to get this goin' before it came out) -- lo, it put me right into
> the sysinstall. ... that was an easy fix.  Heh.  (Is kern.smb.disabled
> set for the 8.1 install or something?  I didn't change anything
> in between attempts.)  In any event -- yay!
> 
> Install worked great, though it appears I need to keep hyperthreading
> ("logical processors" bios option) disabled for it to boot reliably.
> Similar errors as before if I enable it.
> 
> real memory  = 103079215104 (98304 MB)
> avail memory = 99492831232 (94883 MB)
> ACPI APIC Table: 
> FreeBSD/SMP: Multiprocessor System Detected: 24 CPUs
> FreeBSD/SMP: 4 package(s) x 6 core(s)
> 
> Holy cow, that's a nice sight.
> 
> Got one panic shortly after getting it on the network:
> http://dl.dropbox.com/u/7234177/panic.jpg
> 
> ... but it looks like I'll have a lot of kernel and sysctl tweaking to
> do regardless ("ix0: RX Descriptors exceed system mbuf max, using default

Nonetheless it should not panic. Jack may want to know back trace
information for the panic above.(CCed)

> instead!"), so I'll report back to the list if the panic re-appears after
> some tuning.
> 
> --
> Mahlon E. Smith  
> http://www.martini.nu/contact.html


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Unable to install 8.x on a PowerEdge R810

[Chuck Swiger]

Hi, Mahlon--

On Jul 22, 2010, at 5:36 PM, Mahlon E. Smith wrote:
> Install worked great, though it appears I need to keep hyperthreading
> ("logical processors" bios option) disabled for it to boot reliably.
> Similar errors as before if I enable it.

I believe FreeBSD ships with MAXCPU set to 32 by default (check "sysctl 
kern.smp.maxcpus"); your machine with hyperthreading enabled probably goes past 
that #, which is why it crashes with the topology error being reported

Regards,
-- 
-Chuck

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Pawel Tyll]

> I do not think I can adjust the existing zpool on the fly.  I think I
> need to copy everything elsewhere (i.e the 2 empty drives).  Then start
> the new zpool from scratch.
You can, and you should (for educational purposes if not for fun :>),
unless you wish to change raidz1 to raidz2. Replace, wait for
resilver, if redoing used disk then offline it, wipe magic with dd
(16KB at the beginning and end of disk/partition will do), carry on
with GPT, rinse and repeat with next disk. When last vdev's replace
finishes, your pool will grow automagically.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Dan Langille]

On 7/22/2010 9:22 PM, Pawel Tyll wrote:

I do not think I can adjust the existing zpool on the fly.  I think I
need to copy everything elsewhere (i.e the 2 empty drives).  Then start
the new zpool from scratch.



You can, and you should (for educational purposes if not for fun :>),
unless you wish to change raidz1 to raidz2. Replace, wait for
resilver, if redoing used disk then offline it, wipe magic with dd
(16KB at the beginning and end of disk/partition will do), carry on
with GPT, rinse and repeat with next disk. When last vdev's replace
finishes, your pool will grow automagically.


So... the smaller size won't mess things up...

--
Dan Langille - http://langille.org/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Pawel Tyll]

> So... the smaller size won't mess things up...
If by smaller size you mean smaller size of existing
drives/partitions, then growing zpools by replacing smaller vdevs
with larger ones is supported and works. What isn't supported is
basically everything else:
- you can't change number of raid columns (add/remove vdevs from raid)
- you can't change number of parity columns (raidz1->2 or 3)
- you can't change vdevs to smaller ones, even if pool's free space
would permit that.

Good news is these features are planned/being worked on.

If you can attach more drives to your system without disconnecting
existing drives, then you can grow your pool pretty much risk-free.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Using GTP and glabel for ZFS arrays

[Daniel O'Connor]

On 23/07/2010, at 24:56, Volodymyr Kostyrko wrote:

> 22.07.2010 06:05, Dan Langille wrote:
>> Create a new partition within that scheme:
>> 
>> gpart add -b 34 -s SOMEVALUE -t freebsd-zfs ad0
>> 
>> Why '-b 34'? Randi pointed me to
>> http://en.wikipedia.org/wiki/GUID_Partition_Table where it explains what
>> the first 33 LBA are used for. It's not for us to use here.
> 
> gpart is not so dumb to not protect this space. If you don't specify -b when 
> creating first partition it automagically defaults to 34.

Maybe it should default to 40 to get 4k alignment..?
(Probably a POLA/legacy issue there)

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C






___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

latest 8.1 hangs on xpt_config

[Daniel Braniss]

It seems that the latest changes (last 7 days) introduced this problem:
...
run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config
...

i'll try to hunt this down, but any help is welcome.

danny


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: latest 8.1 hangs on xpt_config

[Jeremy Chadwick]

On Fri, Jul 23, 2010 at 09:35:55AM +0300, Daniel Braniss wrote:
> It seems that the latest changes (last 7 days) introduced this problem:
> ...
> run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
> run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
> run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config
> run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config
> ...
> 
> i'll try to hunt this down, but any help is welcome.

Recent to semi-recent commits relevant to xpt that I can find The
problem might not be even in xpt though.  Which xpt piece pertains to
you probably depends on your system setup/configuration.  Dates/times
are in PDT/UTC-0700:

-rw-r--r--1 root wheel   6037  1 Mar 22:48 
/usr/src/sys/cam/cam_xpt_internal.h
-rw-r--r--1 root wheel 124773  9 May 10:19 
/usr/src/sys/cam/cam_xpt.c
-rw-r--r--1 root wheel  72556 23 May 10:41 
/usr/src/sys/cam/scsi/scsi_xpt.c
-rw-r--r--1 root wheel  56663 19 Jul 05:28 
/usr/src/sys/cam/ata/ata_xpt.c

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cam/cam_xpt_internal.h
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cam/cam_xpt.c
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cam/scsi/scsi_xpt.c
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cam/ata/ata_xpt.c

-- 
| 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 |

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"