Re: RELENG_8 kernel as of Apr 14 does not boot
16.04.2012 11:26, Alexey Dokuchaev пишет: Hi, Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled This is stripped down kernel with everything possible loaded from modules. Any ideas? Did not see any warnings in UPDATING... Try to add 'device mem' to your kernel configuration. Eugene Grosbein ___ 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: RELENG_8 kernel as of Apr 14 does not boot
On Mon, Apr 16, 2012 at 01:37:29PM +0700, Eugene Grosbein wrote: 16.04.2012 11:26, Alexey Dokuchaev пишет: Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled Try to add 'device mem' to your kernel configuration. :-) I explicitly have nodevice mem and nodevice io in my config. They are being loaded from /boot/loader.conf. This worked fine for quite a while. I will try to have it compiled-in, but would still prefer it fixed, or in case it cannot be fixed and mem.ko cannot be loaded separately from now on, appropriate entry in UPDATING. ./danfe ___ 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
VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso
Hi, I am trying to run FreeBSD-9.0-RELEASE-amd64-bootonly.iso inside VirtualBox and am having some problems. The error messages I am getting are similar to the ones mentioned here: http://lists.freebsd.org/pipermail/freebsd-stable/2011-December/065079.html My host environment === Operating System: Windows 7, home edition, 64-bit VirtualBox for Windows, version 4.1.12 r77245 CPU Information I downloaded the CoreInfo.exe utility which is part of Windows Sysinternals utilities ( http://technet.microsoft.com/en-us/sysinternals/bb545027 ) According to this utility, my CPU is: Intel(R) Core(TM)2 Duo CPU T5450 @ 1.66GHz Intel64 Family 6 Model 15 Stepping 13, GenuineIntel HTT * Hyperthreading enabled HYPERVISOR - Hypervisor is present VMX - Supports Intel hardware-assisted virtualization SVM - Supports AMD hardware-assisted virtualization EM64T * Supports 64-bit mode So my CPU support 64-bit mode, but does not support hardware-assisted virtualization. Error message = If I try to mount and then boot it under VirtualBox, I get this error: CPU doesn't support long mode Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS 639kB/523264kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (r...@farrell.cse.buffalo.edu, Tue Jan 3 06:51:49 UTC 2012) Can't work out which disk we are booting from. Guess BIOS device 0x not found by probes, defaulting to disk0: FATAL: int13_harddisk: function 42. Can't use 64bits lba Does anyone know how to fix this problem in VirtualBox? QEMU for Windows Just to try something else, I downloaded QEMU 0.9.0 for Windows from: http://www.h7.dion.ne.jp/~qemu-win/ I extracted the zip file into a directory: C:\local\qemu-0.9.0-windows I then ran: cd c:\local\qemu-0.9.0-windows qemu-system-x86_64.exe -L . -m 128 -cdrom c:\temp\FreeBSD-9.0-RELEASE-amd64-bootonly.iso The ISO booted up just fine. From the dmesg output, this was the emulated CPU: CPU: QEMU Virtual CPU version 0.9.0 (1666.98-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x623 Family = 6 Model = 2 Stepping = 3 Features=0x78bfbfdFPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,SE36,CLFLUSH,MMX,FXSR,SSE,SSE2 Features2=0x1SSE3 AMD Features=0x20100800SYSCALL,NX,LM Does anyone know how I can get VirtualBox to behave the same way as QEMU for FreeBSD-9.0-RELEASE-amd64-bootonly.iso? Thanks. -- Craig Rodrigues rodr...@crodrigues.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: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso
On 16/04/12 09:08, Craig Rodrigues wrote: Hi, I am trying to run FreeBSD-9.0-RELEASE-amd64-bootonly.iso inside VirtualBox and am having some problems. The error messages I am getting are similar to the ones mentioned here: http://lists.freebsd.org/pipermail/freebsd-stable/2011-December/065079.html My host environment === Operating System: Windows 7, home edition, 64-bit VirtualBox for Windows, version 4.1.12 r77245 CPU Information I downloaded the CoreInfo.exe utility which is part of Windows Sysinternals utilities ( http://technet.microsoft.com/en-us/sysinternals/bb545027 ) According to this utility, my CPU is: Intel(R) Core(TM)2 Duo CPU T5450 @ 1.66GHz Intel64 Family 6 Model 15 Stepping 13, GenuineIntel HTT * Hyperthreading enabled HYPERVISOR- Hypervisor is present VMX - Supports Intel hardware-assisted virtualization SVM - Supports AMD hardware-assisted virtualization EM64T * Supports 64-bit mode So my CPU support 64-bit mode, but does not support hardware-assisted virtualization. Error message = If I try to mount and then boot it under VirtualBox, I get this error: CPU doesn't support long mode Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS 639kB/523264kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (r...@farrell.cse.buffalo.edu, Tue Jan 3 06:51:49 UTC 2012) Can't work out which disk we are booting from. Guess BIOS device 0x not found by probes, defaulting to disk0: FATAL: int13_harddisk: function 42. Can't use 64bits lba Does anyone know how to fix this problem in VirtualBox? QEMU for Windows Just to try something else, I downloaded QEMU 0.9.0 for Windows from: http://www.h7.dion.ne.jp/~qemu-win/ I extracted the zip file into a directory: C:\local\qemu-0.9.0-windows I then ran: cd c:\local\qemu-0.9.0-windows qemu-system-x86_64.exe -L . -m 128 -cdrom c:\temp\FreeBSD-9.0-RELEASE-amd64-bootonly.iso The ISO booted up just fine. From the dmesg output, this was the emulated CPU: CPU: QEMU Virtual CPU version 0.9.0 (1666.98-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x623 Family = 6 Model = 2 Stepping = 3 Features=0x78bfbfdFPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,SE36,CLFLUSH,MMX,FXSR,SSE,SSE2 Features2=0x1SSE3 AMD Features=0x20100800SYSCALL,NX,LM Does anyone know how I can get VirtualBox to behave the same way as QEMU for FreeBSD-9.0-RELEASE-amd64-bootonly.iso? Thanks. -- Craig Rodrigues rodr...@crodrigues.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 Hi, you can only use 64-bit guests if you have a cpu which supports hardware acceleration. From VirtualBox manual: VirtualBox's 64-bit guest support (added with version 2.0) and multiprocessing (SMP, added with version 3.0) both require hardware virtualization to be enabled. (This is not much of a limitation since the vast majority of today's 64-bit and multicore CPUs ship with hardware virtualization anyway; the exceptions to this rule are e.g. older Intel Celeron and AMD Opteron CPUs.) https://www.virtualbox.org/manual/ch10.html#hwvirt -- Claudius ___ 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: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso
On 16.04.2012 09:08, Craig Rodrigues wrote: Hi, I am trying to run FreeBSD-9.0-RELEASE-amd64-bootonly.iso inside VirtualBox and am having some problems. The error messages I am getting are similar to the ones mentioned here: http://lists.freebsd.org/pipermail/freebsd-stable/2011-December/065079.html [snip] Error message = If I try to mount and then boot it under VirtualBox, I get this error: CPU doesn't support long mode Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS 639kB/523264kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (r...@farrell.cse.buffalo.edu, Tue Jan 3 06:51:49 UTC 2012) Can't work out which disk we are booting from. Guess BIOS device 0x not found by probes, defaulting to disk0: FATAL: int13_harddisk: function 42. Can't use 64bits lba Please create a new VM with preset Operating System BSD and Version FreeBSD (64 bit). -- Bernhard Froehlich http://www.bluelife.at/ ___ 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: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso
On 04/16/2012 09:08 AM, Craig Rodrigues wrote: So my CPU support 64-bit mode, but does not support hardware-assisted virtualization. Intel doesn't support 64 bit software-only virtualization. You really need VTX for this to work. See also: http://en.wikipedia.org/wiki/X86_virtualization#64-bit Regards, Thomas ___ 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: RELENG_8 kernel as of Apr 14 does not boot
Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled Try to add 'device mem' to your kernel configuration. :-) I explicitly have nodevice mem and nodevice io in my config. They are being loaded from /boot/loader.conf. This worked fine for quite a while. I will try to have it compiled-in, but would still prefer it fixed, or in case it cannot be fixed and mem.ko cannot be loaded separately from now on, appropriate entry in UPDATING. It seems John Baldwin brought dependency of acpi.ko on device mem 4 days ago to RELENG_8 with MFC: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/acpica/acpi_wakeup.c#rev1.50.2.3 Eugene Grosbein ___ 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: LSI MegaRAID SAS 9240 with mfi driver?
On 31/03/2012, at 1:14 AM, Doug Ambrisko wrote:
John Baldwin writes:
| On Friday, March 30, 2012 12:06:40 am Jan Mikkelsen wrote:
| Hi,
|
...
| I have a loan LSI MegaRAID SAS 9240-4i controller for testing.
| The pciconf -lv output is:
|
| none3@pci0:1:0:0: class=0x010400 card=0x92411000 chip=0x00731000 rev=0x03
hdr=0x00
| vendor = 'LSI Logic / Symbios Logic'
| device = 'MegaRAID SAS 9240'
| class = mass storage
| subclass = RAID
|
| I added this line to src/sys/dev/mfi/mfi_pci.c
|
|{0x1000, 0x0073, 0x, 0x, MFI_FLAGS_GEN2, LSI MegaRAID SAS
9240},
|
| It gave this result (tried with hw.mfi.msi set to 0 and to 1):
|
| mfi0: LSI MegaRAID SAS 9240 port 0xdc00-0xdcff mem
0xfe7bc000-0xfe7b,0xfe7c-0xfe7f irq 16 at device 0.0 on pci1
| mfi0: Using MSI
| mfi0: Megaraid SAS driver Ver 3.00
| mfi0: Frame 0xff8000285000 timed out command 0x26C8040
| mfi0: failed to send init command
|
| The firmware is package 20.10.1-0077, which is the latest on the LSI
website.
|
| Is this path likely to work out? Any suggestions on where to go from here?
|
| You should try the updated mfi(4) driver that Doug (cc'd) is going to soon
| merge into HEAD. It syncs up with the mfi(4) driver on LSI's website which
| supports several cards that the current mfi(4) driver does not. (I'm not
| fully sure if the 9240 is in that group or not. Doug might know however.)
Yes, this card is supported with the mfi(4) in projects/head_mfi. Looks
like we fixed a couple of last minute found bugs when trying to create a
RAID wth mfiutil. This should be fixed now. I'm going to start the
merge to -current today. The version in head_mfi can run on older
versions of FreeBSD with the changes that Sean did.
I have just imported the mfi(4) and mfiutil(8) into a 9.0-RELEASE tree to try
this out.
When booting up with two fresh drives attached, they show up as usable JBOD
disks. However, I cannot use mfiutil to create anything with them. Every drive
gives
mfiutil: Drive n not available
Is this expected behaviour? How can I create a raid1 volume using mfiutil and
clean disks?
I tried using MegaCli from the LSI website (versions 8.02.16 and 8.02.21), but
they can't even detect the controller. I know you said at some point that a
very recent version of MegaCli was required. What version is necessary?
dmesg:
mfi0: Drake Skinny port 0xdc00-0xdcff mem
0xfe7bc000-0xfe7b,0xfe7c-0xfe7f irq 16 at device 0.0 on pci1
mfi0: Using MSI
mfi0: Megaraid SAS driver Ver 4.23
mfi0: 7021 (387925223s/0x0020/info) - Shutdown command received from host
mfi0: 7022 (boot + 4s/0x0020/info) - Firmware initialization started (PCI ID
0073/1000/9241/1000)
mfi0: 7023 (boot + 4s/0x0020/info) - Firmware version 2.120.244-1482
mfi0: 7024 (boot + 5s/0x0020/info) - Package version 20.10.1-0077
mfi0: 7025 (boot + 5s/0x0020/info) - Board Revision 03A
mfi0: 7026 (boot + 33s/0x0002/info) - Inserted: PD 32(e0xff/s1)
mfisyspd0: MFI System PD on mfi0
mfisyspd0: 1907729MB (3907029168 sectors) SYSPD volume
mfisyspd0: SYSPD volume attached
mfisyspd1: MFI System PD on mfi0
mfisyspd1: 1907729MB (3907029168 sectors) SYSPD volume
mfisyspd1: SYSPD volume attached
Thanks,
Jan Mikkelsen
___
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: Support for IPSec NAT-T in transoprt mode
Hi. On Sun, Apr 15, 2012 at 04:40:03PM +0300, Zmiter wrote: 14.04.2012 19:59, Bjoern A. Zeeb ??: On 13. Apr 2012, at 04:28 , Zmiter wrote: Hello. Does FreeBSD 8.[0-4] support IPSec NAT-T in transport mode? Or it's still in broken state? It's not broken; it was never implemented. No FreeBSD tree shipped does support transport mode at this time. There are patches but you also need to fix ipsec-tools or your ike daemon. If you do the latter I can commit the former. /bz Where could I get that patches? I'd like to test them and to see what could I do with them. You can get kernel patches in kern/146190, but as said in the pr and by Bjoern, it needs some work on userland (IKE daemon). And, if it's really so difficult to implement transport mode in kernel some way, I didn't review/try the patch, but kernel part seems to be done. describe it (I think, all the work for third parties will be implemented through pfkey interface), and wait some time (or may be help a little) until it'll be implemented in ipsec-tools. It's not the egg and chicken problem, may be the kernel must be the first. Or may be I'm not in theme so deep? Is it really some sort or big and principal incompatibilities with ipsec-tools? That's why I took the pr a while ago: to have a look at both parts (kernel and ipsec-tools) and try/commit that once patches exists for both. Afaik, no one already worked on the userland part for ipsec-tools (contact me if I'm wrong !). Yvan. ___ 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
watchdog timeout em driver 8.2-Release
Hi, Switch: HP ProCurve 2910al The switch does passive LACP Motherboard: Supermicro X8DTN+-F NIC: Quad Port Card, i.e. em1: em1@pci0:6:0:1: class=0x02 card=0x125e15d9 chip=0x105e8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'HP NC360T PCIe DP Gigabit Server Adapter (n1e5132)' class = network subclass = ethernet bar [10] = type Memory, range 32, base 0xfb9e, size 131072, enabled bar [14] = type Memory, range 32, base 0xfb9c, size 131072, enabled bar [18] = type I/O Port, range 32, base 0xcc00, size 32, enabled cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 256(256) link x4(x4) ecap 0001[100] = AER 1 0 fatal 1 non-fatal 0 corrected ecap 0003[140] = Serial 1 0025900484d8 I use CAT 6 cables and the switch and server are in the same cabinet. OS: FBSD is 8.2-Release rc.conf: ifconfig_em0=up ifconfig_em1=up ifconfig_em2=up ifconfig_em3=up cloned_interfaces=lagg0 ifconfig_lagg0=laggproto lacp laggport em0 laggport em1 laggport em2 laggport em3 ipv4_addrs_lagg0=192.168.80.20/24 Hm, what sysctls might be interesting? I use: net.inet.tcp.sendbuf_max=16777216 net.inet.tcp.recvbuf_max=16777216 net.inet.tcp.sendspace=65536 net.inet.tcp.recvspace=131072 kern.ipc.nmbclusters=230400 kern.maxvnodes=25 kern.maxfiles=65536 kern.maxfilesperproc=32768 vfs.read_max=32 loader.conf: does only contain stuff concerning zfs Except for swap the whole system uses zfs, swap is on a geom mirror. Once in a while i see this messages in /var/log/messages Apr 13 08:53:07 san02 kernel: em1: Watchdog timeout -- resetting Apr 13 08:53:07 san02 kernel: em1: Queue(0) tdh = 232, hw tdt = 190 Apr 13 08:53:07 san02 kernel: em1: TX(0) desc avail = 31,Next TX to Clean = 221 Apr 13 08:53:07 san02 kernel: em1: Link is Down Apr 13 08:53:07 san02 kernel: em1: link state changed to DOWN Sometimes nothing for days, sometimes under high Network load (NFSv3), sometimes multiple times a day. I see this message/behaviour on always the same two of the four interfaces (em1 and em3). Then the NIC does not have the ACTIVE flag anymore, an ifconfig em1 up solves the issue. But why does it loose the ACTIVE state and why does the NIC reset itself in the first place? On the switch i see that the port matching em1 on the server has left the trunk, so the missing ACTIVE flag is not lying 8-/ Googling found many postings with the same problem and one site suggested that this might be an ACPI problem but nothing concrete and the postings i found were mostly FBSD7 and older. Any pointers would be appreciated. Thank you --lars ___ 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
ATI Radeon 4250 in Dual Head Config?
My xorg.conf foo is pretty weak today. Does anyone have an ATI 4250 in a dual head config? I'd be interested in looking over your xorg.conf. Sean p.s. Mine at the moment, that doesn't work very well: http://people.freebsd.org/~sbruno/4250_xorg_conf.txt ___ 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: LSI MegaRAID SAS 9240 with mfi driver?
Jan Mikkelsen writes:
| On 31/03/2012, at 1:14 AM, Doug Ambrisko wrote:
| John Baldwin writes:
| | On Friday, March 30, 2012 12:06:40 am Jan Mikkelsen wrote:
| | Hi,
| |
| ...
|
| | I have a loan LSI MegaRAID SAS 9240-4i controller for testing.
| | The pciconf -lv output is:
| |
| | none3@pci0:1:0:0: class=0x010400 card=0x92411000 chip=0x00731000
rev=0x03 hdr=0x00
| | vendor = 'LSI Logic / Symbios Logic'
| | device = 'MegaRAID SAS 9240'
| | class = mass storage
| | subclass = RAID
| |
| | I added this line to src/sys/dev/mfi/mfi_pci.c
| |
| | {0x1000, 0x0073, 0x, 0x, MFI_FLAGS_GEN2, LSI MegaRAID
SAS 9240},
| |
| | It gave this result (tried with hw.mfi.msi set to 0 and to 1):
| |
| | mfi0: LSI MegaRAID SAS 9240 port 0xdc00-0xdcff mem
0xfe7bc000-0xfe7b,0xfe7c-0xfe7f irq 16 at device 0.0 on pci1
| | mfi0: Using MSI
| | mfi0: Megaraid SAS driver Ver 3.00
| | mfi0: Frame 0xff8000285000 timed out command 0x26C8040
| | mfi0: failed to send init command
| |
| | The firmware is package 20.10.1-0077, which is the latest on the LSI
website.
| |
| | Is this path likely to work out? Any suggestions on where to go from
here?
| |
| | You should try the updated mfi(4) driver that Doug (cc'd) is going to soon
| | merge into HEAD. It syncs up with the mfi(4) driver on LSI's website
which
| | supports several cards that the current mfi(4) driver does not. (I'm not
| | fully sure if the 9240 is in that group or not. Doug might know however.)
|
| Yes, this card is supported with the mfi(4) in projects/head_mfi. Looks
| like we fixed a couple of last minute found bugs when trying to create a
| RAID wth mfiutil. This should be fixed now. I'm going to start the
| merge to -current today. The version in head_mfi can run on older
| versions of FreeBSD with the changes that Sean did.
|
| I have just imported the mfi(4) and mfiutil(8) into a 9.0-RELEASE tree to
| try this out.
|
| When booting up with two fresh drives attached, they show up as usable
| JBOD disks. However, I cannot use mfiutil to create anything with them.
| Every drive gives
|
|mfiutil: Drive n not available
You might want to include the output of:
mfiutil show drives
and then the command you are trying to do to create a RAID with.
| Is this expected behaviour? How can I create a raid1 volume using
| mfiutil and clean disks?
I'm not sure if mfiutil can switch disks from JBOD mode to RAID.
I don't see any reason why it shouldn't. It can't go from RAID to
real JBOD mode since it doesn't have code to support that.
| I tried using MegaCli from the LSI website (versions 8.02.16 and
| 8.02.21), but they can't even detect the controller. I know you
| said at some point that a very recent version of MegaCli was
| required. What version is necessary?
What was the syntax you used since usage is cryptic? I've never
seen a MegaCli that couldn't access the card. What I meant by
more recent MegaCli is earlier versions didn't have the JBOD
commands in it. I have a 8.00.46 that knows about JBOD.
| dmesg:
|
| mfi0: Drake Skinny port 0xdc00-0xdcff mem
0xfe7bc000-0xfe7b,0xfe7c-0xfe7f irq 16 at device 0.0 on pci1
| mfi0: Using MSI
| mfi0: Megaraid SAS driver Ver 4.23
| mfi0: 7021 (387925223s/0x0020/info) - Shutdown command received from host
| mfi0: 7022 (boot + 4s/0x0020/info) - Firmware initialization started (PCI ID
0073/1000/9241/1000)
| mfi0: 7023 (boot + 4s/0x0020/info) - Firmware version 2.120.244-1482
| mfi0: 7024 (boot + 5s/0x0020/info) - Package version 20.10.1-0077
| mfi0: 7025 (boot + 5s/0x0020/info) - Board Revision 03A
| mfi0: 7026 (boot + 33s/0x0002/info) - Inserted: PD 32(e0xff/s1)
| mfisyspd0: MFI System PD on mfi0
| mfisyspd0: 1907729MB (3907029168 sectors) SYSPD volume
| mfisyspd0: SYSPD volume attached
| mfisyspd1: MFI System PD on mfi0
| mfisyspd1: 1907729MB (3907029168 sectors) SYSPD volume
| mfisyspd1: SYSPD volume attached
You are definitely in real JBOD mode with each drive being /dev/mfisyspd0
and /dev/mfisyspd1. So you can access the drives as those to do some
experiments with if you want to.
Doug A.
___
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: ATI Radeon 4250 in Dual Head Config?
On Mon, 16 Apr 2012, Sean Bruno wrote: Does anyone have an ATI 4250 in a dual head config? I'd be interested in looking over your xorg.conf. Sean p.s. Mine at the moment, that doesn't work very well: http://people.freebsd.org/~sbruno/4250_xorg_conf.txt Here's what I use with a 4650, comments removed to save space. Notes: 1. Don't use AEI: http://www.wonkity.com/~wblock/docs/html/aei.html 2. Monitors are assigned to connectors in the Device section. The Position option in the Monitor section defines what part they show. 3. This is one desktop across two monitors, the combined size set in the Virtual line. 4. HAL is not installed, but I'm fairly sure this will work either way. Section ServerLayout Identifier Manually Configured Screen 0 Screen0 0 0 Option DontZap Off Option AIGLX On Option AutoAddDevices Off EndSection Section Files ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/bitstream-vera/ EndSection Section DRI Group 0 Mode 0660 EndSection Section Extensions Option Composite Enable EndSection Section Monitor Identifier Monitor0 VendorName HWP ModelName2615 Option PreferredMode 1920x1200 Option Position 1280 0 EndSection Section Monitor Identifier Monitor1 VendorName SAM ModelName215 Option PreferredMode 1280x1024 Option Position 0 0 EndSection Section Device Identifier Card0 Driver radeon VendorName ATI Technologies Inc BoardName RV730 PRO [Radeon HD 4650] Option AccelMethod EXA Option Monitor-DVI-0 Monitor0 Option Monitor-VGA-0 Monitor1 Option ClockGating On Option DynamicPM On EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Virtual 3200 1200 EndSubSection EndSection ___ 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
ZFS options for FreeBSD 8.3
Hi all,
I have installed FreeBSD 8.3 amd64 release in an ESXi server. Due to
some limitations, I can only assign 2GiB of RAM to this virtual machine
and I need to use ZFS as filesystem to store some data (MySQL databases).
According to http://wiki.freebsd.org/ZFSTuningGuide I have configured
some options:
vfs.zfs.write_limit_override=268435456
kern.maxvnodes=25
According to ZFS version, FreeBSD 8,3 comes with version 28, and
reading previous guide there is not need to adjust nothing more.
But what about l2arc options?? Do I need to adjust vfs.zfs.arc_max and
vm.kmem_size options?? How can I calculate these values??
Thanks.
--
CL Martinez
carlopmart {at} gmail {d0t} com
___
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: ZFS options for FreeBSD 8.3
On 04/16/2012 07:10 PM, Chuck Swiger wrote:
On Apr 16, 2012, at 9:57 AM, carlopmart wrote:
I have installed FreeBSD 8.3 amd64 release in an ESXi server. Due to some
limitations, I can only assign 2GiB of RAM to this virtual machine and I need
to use ZFS as filesystem to store some data (MySQL databases).
That combination doesn't make much sense, frankly.
ZFS is very memory hungry-- I wouldn't want to run it on anything with less
than 4GB of RAM, although other folks around here have reported successful
setups under 2GB of RAM with some tuning. However, the data integrity benefits
of ZFS mostly come from it talking directly to disks in JBOD configuration; if
ZFS is just running in a VM and talking to a filesystem image, it loses much of
the advantage which it might otherwise provide.
You'd almost certainly get better MySQL performance by going with UFSv2 and
having the DB use most of the RAM, instead of having it be sucked away by ZFS.
Regards,
Thanks Chuck. Yes, I know it is not hte best option. But I need to
tunning this vm with ZFS. Almost, is the minimum RAM needed for ZFS
according to
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/filesystems-zfs.html.
--
CL Martinez
carlopmart {at} gmail {d0t} com
___
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
Any options on crypt+zfs ?
hail, I have a soekris running an atom and 2GB RAM and ZFS using 7 drives, small capacity though, to test and study if I can make my home server this box and this way. It will be a simple server, three users tops. I followed the handbook and made the geli step on the disks: Geom name: label/zfs1.eli State: ACTIVE EncryptionAlgorithm: AES-XTS KeyLength: 128 Crypto: software UsedKey: 0 Flags: NONE KeysAllocated: 38 KeysTotal: 38 Providers: 1. Name: label/zfs1.eli Mediasize: 160041881600 (149G) Sectorsize: 4096 Mode: r1w1e1 Consumers: 1. Name: label/zfs1 Mediasize: 160041885184 (149G) Sectorsize: 512 Mode: r1w1e1 all disks are this way (just 4 disks are on geli zfs). would it be faster, if I had geli over zfs, and not the other way (as is now) ? my performance is too low (I know the hardware is not that much, but I compared it to a friend's arm based AP-Router gadget and my setup is when much equal. I have 1.6 GHz Atom and 2GB ram, he has not half this ... I know can't compare arm and x86 clock for clock ...) I'll try to run geli on single disk, to see how much ZFS is impacting on performance, but, is there any other way around ? All I want is RAID5, and FreeBSD has not developed RAID5 from GEOM (AFAIK) since a long time. ZFS is the way people go in recent years. suggestions are welcome, just want to upgrade my old 8.0 BETA3 using geom mirror/stripe to a newer approach that would be supported by FreeBSD. I have an external enclosure for 4 SATA disks (port multiplier included) using 4 disks, another port multiplier 5x1 using now 3 disks, and: ahci1@pci0:13:0:0: class=0x010601 card=0x10601b21 chip=0x06121b21 rev=0x01 hdr=0x00 vendor = 'ASMedia Technology Inc.' class = mass storage subclass = SATA with two eSATA to the Port Multipliers. thanks, matheus machine: ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) Copyright (c) 1992-2012 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 9.0-RELEASE #0: Wed Apr 11 13:04:15 BRT 2012 root@macgyver:/usr/obj/usr/src/sys/net6501-amd64 amd64 ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) CPU: Genuine Intel(R) CPU@ 1.60GHz (1600.04-MHz K8-class CPU) Origin = GenuineIntel Id = 0x20661 Family = 6 Model = 26 Stepping = 1 Features=0xbfe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x40e3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 2147352576 (2047 MB) avail memory = 2046488576 (1951 MB) MPTable: Soekris net6501 Event timer LAPIC quality 400 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 ioapic0: Assuming intbase of 0 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd0 at kbdmux0 ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) ACPI: Table initialisation failed: AE_NOT_FOUND ACPI: Try disabling either ACPI or apic support. cryptosoft0: software crypto on motherboard -- We will call you Cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ 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: ZFS options for FreeBSD 8.3
On 04/16/2012 07:35 PM, Chuck Swiger wrote:
On Apr 16, 2012, at 10:28 AM, carlopmart wrote:
Thanks Chuck. Yes, I know it is not hte best option. But I need to tunning this
vm with ZFS.
Um, why?
Becaus, we can't assing more ...
Almost, is the minimum RAM needed for ZFS according to
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/filesystems-zfs.html.
Yeah-- note the bit about system panics under load due to the kernel running
out of available memory.
Regards,
Sure, but I don't expect a heavy load under this server ...
Thanks.
--
CL Martinez
carlopmart {at} gmail {d0t} com
___
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: ZFS options for FreeBSD 8.3
On Apr 16, 2012, at 9:57 AM, carlopmart wrote: I have installed FreeBSD 8.3 amd64 release in an ESXi server. Due to some limitations, I can only assign 2GiB of RAM to this virtual machine and I need to use ZFS as filesystem to store some data (MySQL databases). That combination doesn't make much sense, frankly. ZFS is very memory hungry-- I wouldn't want to run it on anything with less than 4GB of RAM, although other folks around here have reported successful setups under 2GB of RAM with some tuning. However, the data integrity benefits of ZFS mostly come from it talking directly to disks in JBOD configuration; if ZFS is just running in a VM and talking to a filesystem image, it loses much of the advantage which it might otherwise provide. You'd almost certainly get better MySQL performance by going with UFSv2 and having the DB use most of the RAM, instead of having it be sucked away by ZFS. 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: ZFS options for FreeBSD 8.3
On 04/16/2012 08:04 PM, Chuck Swiger wrote:
On Apr 16, 2012, at 10:54 AM, carlopmart wrote:
On 04/16/2012 07:35 PM, Chuck Swiger wrote:
On Apr 16, 2012, at 10:28 AM, carlopmart wrote:
Thanks Chuck. Yes, I know it is not hte best option. But I need to tunning this
vm with ZFS.
Um, why?
Becaus, we can't assing more ...
My question was not why can't you assign more RAM to the VM. :-)
It was, why do you need to run with ZFS...?
Regards,
Because we need to add virtual disks frequently (using hot swap feature
that ESXi provides) without dismounting any filesystem...
Basically I will use zfs as a disk volume manager. I will not use dedup,
encryption features, etc ...
--
CL Martinez
carlopmart {at} gmail {d0t} com
___
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: ZFS options for FreeBSD 8.3
On Apr 16, 2012, at 10:28 AM, carlopmart wrote: Thanks Chuck. Yes, I know it is not hte best option. But I need to tunning this vm with ZFS. Um, why? Almost, is the minimum RAM needed for ZFS according to http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/filesystems-zfs.html. Yeah-- note the bit about system panics under load due to the kernel running out of available memory. 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
Troubleshooting jail startup problem
Hello, I recently setup a new server with 9-STABLE (freshly built today), but i am having problem setting up jails on this system. I have previously setup jails on version 8 systems without any issue. I installed a jail using the method described in the handbook, but when i try to start it using /etc/rc.d/jail start, it fails. --- # /etc/rc.d/jail start Configuring jails:. Starting jails: cannot start jail web: . --- How can i troubleshoot this? There are no useful errors logged anywhere. If i manually start the jail using the below command, it works just fine. --- # jail -c path=/jails/web host.hostname=web.local ip4.addr=10.57.227.98 command=/bin/sh /etc/rc --- Below is my rc.conf --- hostname=jail.local defaultrouter=10.57.227.254 ifconfig_bce0=inet 10.57.227.97 netmask 255.255.255.0 ifconfig_bce0_alias0=inet 10.57.227.98 netmask 0x ifconfig_bce0_alias1=inet 10.57.227.99 netmask 0x ifconfig_bce0_alias2=inet 10.57.227.100 netmask 0x ifconfig_bce0_alias3=inet 10.57.227.101 netmask 0x # dumpdev=NO sshd_enable=YES ntpd_enable=YES syslogd_flags=-4 -b 10.57.227.97 # jail_enable=YES jail_list=web #jail_interface=bce0 #jail_devfs_enable=YES #jail_devfs_ruleset=devfsrules_jail #jail_fdescfs_enable=YES #jail_procfs_enable=YES # jail_web_rootdir=/jails/web jail_web_hostname=web.local jail_web_ip=10.57.227.98 --- Thanks. ___ 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: ZFS options for FreeBSD 8.3
On Apr 16, 2012, at 10:54 AM, carlopmart wrote: On 04/16/2012 07:35 PM, Chuck Swiger wrote: On Apr 16, 2012, at 10:28 AM, carlopmart wrote: Thanks Chuck. Yes, I know it is not hte best option. But I need to tunning this vm with ZFS. Um, why? Becaus, we can't assing more ... My question was not why can't you assign more RAM to the VM. :-) It was, why do you need to run with ZFS...? 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: Troubleshooting jail startup problem
On Mon, 2012-04-16 at 14:49 -0400, Mike Jakubik wrote: Hello, I recently setup a new server with 9-STABLE (freshly built today), but i am having problem setting up jails on this system. I have previously setup jails on version 8 systems without any issue. I installed a jail using the method described in the handbook, but when i try to start it using /etc/rc.d/jail start, it fails. --- # /etc/rc.d/jail start Configuring jails:. Starting jails: cannot start jail web: . --- How can i troubleshoot this? There are no useful errors logged anywhere. If i manually start the jail using the below command, it works just fine. I ran sh -x /etc/rc.d/jail start to get some more debug info, but im still unable to see why it is failing. It does throw one error jail: unknown parameter: allow.nomount, but that appears to be after it already failed. Here is the complete output: http://pastebin.com/S6Xd8aST Thanks. ___ 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: Troubleshooting jail startup problem
On Mon, 2012-04-16 at 15:10 -0400, Mike Jakubik wrote: I ran sh -x /etc/rc.d/jail start to get some more debug info, but im still unable to see why it is failing. It does throw one error jail: unknown parameter: allow.nomount, but that appears to be after it already failed. This appears to be the culprit, a bug that's in CURRENT, that somehow made it in to 9-STABLE. http://www.freebsd.org/cgi/query-pr.cgi?pr=165515 ___ 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: Support for IPSec NAT-T in transoprt mode
16.04.2012 12:59, VANHULLEBUS Yvan написал: I didn't review/try the patch, but kernel part seems to be done. Upon my testing it's not so good as it seems. I found some trouble with it. 1. sysctl net.inet.esp.esp_ignore_natt_cksum works not as expected. If there is troubles with function key_compute_natt_cksum, bad (not recalculated) checksums are not ignored and packets are droped, increasing bad udp checksums counter. 2. received by L2TP daemon decrypted packets seemed to it as packets originated from NAT address, but not from LAN behind the NAT. So, L2TP daemon answers them back to NAT, and ofcourse they not satisfy the SPD policy and not being encrypted through IPSec, as a result they are never arrive to the NATed host. May be I'm doing something wrong, but my little research shows me described results. I'll be appressiating any help with that. 16.04.2012 Zmiter ___ 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
kldload uhci lockup
I observed that following could cause machine lockup since at least 8-CURRENT. Now I'm on 9-STABLE No usb in kernel, attached mouse pointer. # kldload usb ums ehci # kldload uhci or # kldload uhci usb ums ehci uhci is required for working mouse. Can anyone confirm? Please test few different iterations, as it's probably not easily reproducible. Most times nothing happens, if machine slow downs to crawl/halt , it's on uhci loading stage I suppose. Best if somebody could pin this down on their machine, as I don't have time to debug this now/would have to alter my configuration considerably. best regards, - Jakub Lach -- View this message in context: http://freebsd.1045724.n5.nabble.com/kldload-uhci-lockup-tp5644899p5644899.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ 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: Any options on crypt+zfs ?
On 2012-04-16, at 13:32 , Nenhum_de_Nos wrote: hail, I have a soekris running an atom and 2GB RAM and ZFS using 7 drives, small capacity though, to test and study if I can make my home server this box and this way. It will be a simple server, three users tops. I followed the handbook and made the geli step on the disks: Geom name: label/zfs1.eli State: ACTIVE EncryptionAlgorithm: AES-XTS KeyLength: 128 Crypto: software UsedKey: 0 Flags: NONE KeysAllocated: 38 KeysTotal: 38 Providers: 1. Name: label/zfs1.eli Mediasize: 160041881600 (149G) Sectorsize: 4096 Mode: r1w1e1 Consumers: 1. Name: label/zfs1 Mediasize: 160041885184 (149G) Sectorsize: 512 Mode: r1w1e1 all disks are this way (just 4 disks are on geli zfs). would it be faster, if I had geli over zfs, and not the other way (as is now) ? my performance is too low (I know the hardware is not that much, but I compared it to a friend's arm based AP-Router gadget and my setup is when much equal. I have 1.6 GHz Atom and 2GB ram, he has not half this ... I know can't compare arm and x86 clock for clock ...) I'll try to run geli on single disk, to see how much ZFS is impacting on performance, but, is there any other way around ? All I want is RAID5, and FreeBSD has not developed RAID5 from GEOM (AFAIK) since a long time. ZFS is the way people go in recent years. suggestions are welcome, just want to upgrade my old 8.0 BETA3 using geom mirror/stripe to a newer approach that would be supported by FreeBSD. I have an external enclosure for 4 SATA disks (port multiplier included) using 4 disks, another port multiplier 5x1 using now 3 disks, and: ahci1@pci0:13:0:0:class=0x010601 card=0x10601b21 chip=0x06121b21 rev=0x01 hdr=0x00 vendor = 'ASMedia Technology Inc.' class = mass storage subclass = SATA with two eSATA to the Port Multipliers. thanks, matheus machine: ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) Copyright (c) 1992-2012 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 9.0-RELEASE #0: Wed Apr 11 13:04:15 BRT 2012 root@macgyver:/usr/obj/usr/src/sys/net6501-amd64 amd64 ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) CPU: Genuine Intel(R) CPU@ 1.60GHz (1600.04-MHz K8-class CPU) Origin = GenuineIntel Id = 0x20661 Family = 6 Model = 26 Stepping = 1 Features=0xbfe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x40e3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 2147352576 (2047 MB) avail memory = 2046488576 (1951 MB) MPTable: Soekris net6501 Event timer LAPIC quality 400 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 ioapic0: Assuming intbase of 0 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd0 at kbdmux0 ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) ACPI: Table initialisation failed: AE_NOT_FOUND ACPI: Try disabling either ACPI or apic support. cryptosoft0: software crypto on motherboard -- We will call you Cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ 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 The ideal solution will be ZFS with crypto support, but unfortunately this is only available on Oracle Sun 5.11 for now. The GELI is very good, but it is mostly for single device/file image encryption. Each new GELI device in the ZFS mirror/RAIDZ configuration will add extra overhead. GELI on top of ZFS volume/file-backed will be even worse. You could consider PEFS from ports on top of any ZFS pool. PEFS is a kernel level stacked cryptographic filesystem for FreeBSD: http://www.freshports.org/sysutils/pefs-kmod/ http://wiki.freebsd.org/PEFS https://github.com/glk/pefs P.S. ZFS RAIDZ1/RAIDZ2 pool is more sophisticated solution than RAID5/RAID6. ___ 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: LSI MegaRAID SAS 9240 with mfi driver?
On 17/04/2012, at 2:32 AM, Doug Ambrisko wrote: Jan Mikkelsen writes: | On 31/03/2012, at 1:14 AM, Doug Ambrisko wrote: ... | Yes, this card is supported with the mfi(4) in projects/head_mfi. Looks | like we fixed a couple of last minute found bugs when trying to create a | RAID wth mfiutil. This should be fixed now. I'm going to start the | merge to -current today. The version in head_mfi can run on older | versions of FreeBSD with the changes that Sean did. | | I have just imported the mfi(4) and mfiutil(8) into a 9.0-RELEASE tree to | try this out. | | When booting up with two fresh drives attached, they show up as usable | JBOD disks. However, I cannot use mfiutil to create anything with them. | Every drive gives | |mfiutil: Drive n not available You might want to include the output of: mfiutil show drives and then the command you are trying to do to create a RAID with. | Is this expected behaviour? How can I create a raid1 volume using | mfiutil and clean disks? I'm not sure if mfiutil can switch disks from JBOD mode to RAID. I don't see any reason why it shouldn't. It can't go from RAID to real JBOD mode since it doesn't have code to support that. | I tried using MegaCli from the LSI website (versions 8.02.16 and | 8.02.21), but they can't even detect the controller. I know you | said at some point that a very recent version of MegaCli was | required. What version is necessary? What was the syntax you used since usage is cryptic? I've never seen a MegaCli that couldn't access the card. What I meant by more recent MegaCli is earlier versions didn't have the JBOD commands in it. I have a 8.00.46 that knows about JBOD. The MegaCli problem was an embarrassing operator error which I can't blame on the bad UI. mfiutil create jbod … doesn't create a JBOD disk, it creates a raid0 volume. I think that was expected. The biggest problem with this controller and just mfiutil is that you can't get a drive from the JBOD state to the unconfigured-good state, and a blank disk starts in JBOD. So to do any setup you need to resort to the BIOS utility or MegaCli. For each disk to change from JBOD to Unconfigured-good so that it can be used to create a volume, I needed to do: MegaCli -PDMakeGood -Physdrv '[64:1]' -force -a0 Obviously with the right drivespec. Once they're in this state I can use mfiutil to create volumes. I can get drives from the unconfigured-good state to JBOD by doing MegaCli -PDMakeJBOD …. This is just in a little test machine with a few drives. Now that it is working to this level I will get a server with a 9240 and give it a proper run. I'll also try the driver out in one of the 9261 based servers we've got here. Thanks! Jan. ___ 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: Any options on crypt+zfs ?
On Mon, April 16, 2012 22:42, Andriy Bakay wrote: On 2012-04-16, at 13:32 , Nenhum_de_Nos wrote: hail, I have a soekris running an atom and 2GB RAM and ZFS using 7 drives, small capacity though, to test and study if I can make my home server this box and this way. It will be a simple server, three users tops. I followed the handbook and made the geli step on the disks: Geom name: label/zfs1.eli State: ACTIVE EncryptionAlgorithm: AES-XTS KeyLength: 128 Crypto: software UsedKey: 0 Flags: NONE KeysAllocated: 38 KeysTotal: 38 Providers: 1. Name: label/zfs1.eli Mediasize: 160041881600 (149G) Sectorsize: 4096 Mode: r1w1e1 Consumers: 1. Name: label/zfs1 Mediasize: 160041885184 (149G) Sectorsize: 512 Mode: r1w1e1 all disks are this way (just 4 disks are on geli zfs). would it be faster, if I had geli over zfs, and not the other way (as is now) ? my performance is too low (I know the hardware is not that much, but I compared it to a friend's arm based AP-Router gadget and my setup is when much equal. I have 1.6 GHz Atom and 2GB ram, he has not half this ... I know can't compare arm and x86 clock for clock ...) I'll try to run geli on single disk, to see how much ZFS is impacting on performance, but, is there any other way around ? All I want is RAID5, and FreeBSD has not developed RAID5 from GEOM (AFAIK) since a long time. ZFS is the way people go in recent years. suggestions are welcome, just want to upgrade my old 8.0 BETA3 using geom mirror/stripe to a newer approach that would be supported by FreeBSD. I have an external enclosure for 4 SATA disks (port multiplier included) using 4 disks, another port multiplier 5x1 using now 3 disks, and: ahci1@pci0:13:0:0: class=0x010601 card=0x10601b21 chip=0x06121b21 rev=0x01 hdr=0x00 vendor = 'ASMedia Technology Inc.' class = mass storage subclass = SATA with two eSATA to the Port Multipliers. thanks, matheus machine: ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) Copyright (c) 1992-2012 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 9.0-RELEASE #0: Wed Apr 11 13:04:15 BRT 2012 root@macgyver:/usr/obj/usr/src/sys/net6501-amd64 amd64 ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) CPU: Genuine Intel(R) CPU@ 1.60GHz (1600.04-MHz K8-class CPU) Origin = GenuineIntel Id = 0x20661 Family = 6 Model = 26 Stepping = 1 Features=0xbfe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x40e3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 2147352576 (2047 MB) avail memory = 2046488576 (1951 MB) MPTable: Soekris net6501 Event timer LAPIC quality 400 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 ioapic0: Assuming intbase of 0 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd0 at kbdmux0 ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) ACPI: Table initialisation failed: AE_NOT_FOUND ACPI: Try disabling either ACPI or apic support. cryptosoft0: software crypto on motherboard -- We will call you Cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ 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 The ideal solution will be ZFS with crypto support, but unfortunately this is only available on Oracle Sun 5.11 for now. The GELI is very good, but it is mostly for single device/file image encryption. Each new GELI device in the ZFS mirror/RAIDZ configuration will add extra overhead. GELI on top of ZFS volume/file-backed will be even worse. You could consider PEFS from ports on top of any ZFS pool. PEFS is a kernel level stacked cryptographic filesystem for FreeBSD: http://www.freshports.org/sysutils/pefs-kmod/ http://wiki.freebsd.org/PEFS https://github.com/glk/pefs P.S. ZFS RAIDZ1/RAIDZ2 pool is more sophisticated solution than RAID5/RAID6. Thanks Andriy, I'll read about it. Can I consider this PEFS so stable as GELI ? thanks, matheus -- We will call you Cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
Re: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso
On Mon, Apr 16, 2012 at 12:08 AM, Craig Rodrigues rodr...@crodrigues.org wrote: My host environment === Operating System: Windows 7, home edition, 64-bit VirtualBox for Windows, version 4.1.12 r77245 CPU Information I downloaded the CoreInfo.exe utility which is part of Windows Sysinternals utilities ( http://technet.microsoft.com/en-us/sysinternals/bb545027 ) According to this utility, my CPU is: Intel(R) Core(TM)2 Duo CPU T5450 @ 1.66GHz Intel64 Family 6 Model 15 Stepping 13, GenuineIntel HTT * Hyperthreading enabled HYPERVISOR - Hypervisor is present VMX - Supports Intel hardware-assisted virtualization SVM - Supports AMD hardware-assisted virtualization EM64T * Supports 64-bit mode So my CPU support 64-bit mode, but does not support hardware-assisted virtualization. Error message = If I try to mount and then boot it under VirtualBox, I get this error: CPU doesn't support long mode Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS 639kB/523264kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (r...@farrell.cse.buffalo.edu, Tue Jan 3 06:51:49 UTC 2012) Can't work out which disk we are booting from. Guess BIOS device 0x not found by probes, defaulting to disk0: FATAL: int13_harddisk: function 42. Can't use 64bits lba Does anyone know how to fix this problem in VirtualBox? Hi, After exchanging a few e-mails with Bernard, I think I understand the problem. According to the VirtualBox manual: http://www.virtualbox.org/manual/ch03.html#intro-64bitguests The CPU needs to support hardware-assisted virtualization in order for VirtualBox to support 64-bit guests. Without the CPU support, VirtualBox cannot do it. I double checked this with CoreInfo.exe from Windows Sysinternals utilities, and also from the Intel data sheet for my CPU: http://ark.intel.com/products/30787 (VT-x option not supported) I will use QEMU under Windows until I can get a better machine. :) -- Craig Rodrigues rodr...@crodrigues.org -- Craig Rodrigues rodr...@crodrigues.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: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso
On Mon, Apr 16, 2012 at 10:30 PM, Craig Rodrigues rodr...@crodrigues.orgwrote: After exchanging a few e-mails with Bernard, I think I understand the problem. According to the VirtualBox manual: http://www.virtualbox.org/manual/ch03.html#intro-64bitguests The CPU needs to support hardware-assisted virtualization in order for VirtualBox to support 64-bit guests. Without the CPU support, VirtualBox cannot do it. I double checked this with CoreInfo.exe from Windows Sysinternals utilities, and also from the Intel data sheet for my CPU: http://ark.intel.com/products/30787 (VT-x option not supported) I will use QEMU under Windows until I can get a better machine. :) I believe a Windows 7 product key will activate either 32 or 64 install, so unless you have a specific reason to install 64 bit then you are likely better using 32 anyway. 32 bit OS's and apps use less memory than their corresponding 64 bit counterparts. -- Adam Vande More ___ 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
