Re: file systems

[Nick Holland]

On 05/26/17 10:35, Friedrich Locke wrote:
> Hi folks,
> 
> does anybody here run OBSD with a file system bigger than 10TB ?
> How much time boot takes to bring the system up (i mean fsck) ?
> Are you using ffs2 ? With softdep ?
> 
> Thanks.

Error #1: assuming someone else's experience will have anything at all
to do with yours.  When doing things like this, you need to just test it
yourself with your data and see what happens.  And as I always preach,
"testing" doesn't stop at "I built it and it works!"  Experiment with
failure modes, look at how you move data to a new machine when you need
to, etc.  Your performance will depend greatly on your hw and your data.

Error #2: When you create a single file system that big, you are usually
Doing it Wrong (or at least, sub-optimally).  You really should be
"chunking" your data into more manageable chunks if at all possible.

Some of the benefits to "chunking" your data:
* If you can RO "full" file systems, your fsck time drops to zero for those.
* You buy storage when you need it instead of in advance.  Since storage
almost always gets bigger and cheaper, delaying storage purchase makes a
lot of sense.
* Even with modern hw, a gigabyte of data takes a while to move.  A
terabyte takes a long time to move.
* Someday, you will need to upgrade/replace the hardware.  Chunking your
data gives lots of options here, which might be the difference in doing
a hw replacement/upgrade in a routine hw maintenance window vs. spending
a very long weekend down.
* When something bad happens, you may spend a lot less time recreating
your data.

Nick.

kernel panic: ehci_device_clear_toggle

[Nicolas Schmidt]

Hi,

I just installed OpenBSD 6.1 and set up a CUPS server with a usb printer, and 
I'm experiencing kernel panics that seem usb related.
These kernel panics actually occured also on the old version of OpenBSD I 
upgraded from, but only very rarely (once every few months a most). Now I've 
had three panics in the course of a few hours. The irony is that one of the 
reasons for upgradings was this exact problem; I assumed it would have been 
fixed, as it was mentioned on this list already.

I would like to file a bug report, but I can't gather all the infos asked for 
https://www.openbsd.org/ddb.html, as the keyboard stops working after the 
kernel panic (probably because it's a usb keyboard). So, here's the output I 
can give you:

# panic: ehci_device_clear_toggle: queue active
Stopped at  Debugger+0x7:   leave
TID PID UID PRFLAGS PFLAGS  CPU COMMAND
*359035 78367   541 0x1002  0x8 1   usb
216484  46276   0   0x14000 0x200   0   reaper
Debugger(d0a08f55,f54ee848,d09d62e0,f54ee848,0) at Debugger+0x7
panic(d09d62e0,dbaed460,f54ee88c,d08a0895,0) at panic+0x71
ehci_device_clear_toggle(d5d8ff00,d5d8ff00,d5a02800,0,2) at 
ehci_device_clear_toggle+0x29
usbd_clear_endpoint_stall(d5d8ff00,d5d8ff00,0,f54ee8dc,400) at 
usbd_clear_endpoint_stall+0x20
ugen_do_write(d5aa,1,f54eee8c,1,f54eed10) at ugen_do_write+0x2a8
ugenwrite(3f01,f54eee8c,1,d0508d09,db91169c) at ugenwrite+0x4f
spec_write(f54eedb8,db7b2aa4,f54eee74,d03cd5e9,d0bf6ae0) at spec_write+0xa7
VOP_WRITE(dba0fccc,f54eee8c,1,dbaf2c00,17a8840) at VOP_WRITE+0x42
vn_write(db91169c,db91116b4,f54eee8c,dbaf2c00,d0bf6ae0) at vn_write+0x8a
dofilewritev(db7b2aa4,8,db91169c,f54eeef4,1) at dofilewritev+0x1c6
sys_write(db7b2aa4,f54eef5c,f54eef7c,0,200286) at sys_write+0x8f
syscall() at syscall+0x250
--- syscall (number -813756072) ---
0x6:



One piece of context: the uid 541 is the user _cups, under which cupsd runs.

Best,
Nicolas

"athn0: could not load firmware" for AR9271

[Maximilian Pichler]

Hi,

I'm trying to use an Olimex MOD-WIFI-AR9271-ANT USB wireless adapter, but:
# dmesg
OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr  1 13:45:56 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
[...]
athn0 at uhub0 port 5 configuration 1 interface 0 "ATHEROS UB93" rev
2.00/1.08 addr 2
athn0: could not load firmware
[...]

The athn firmware is installed:
# fw_update -i
Installed: athn-firmware-1.1p1
Installed, extra: iwi-firmware-3.1p2 radeondrm-firmware-20150927
pgt-firmware-1.2p4 bwi-firmware-1.4p4 urtwn-firmware-1.2
ipw-firmware-1.3p2 iwn-firmware-5.11p1 uath-firmware-2.0p1
iwm-firmware-0.20161101 otus-firmware-1.0p1 wpi-firmware-3.2p1
vmm-firmware-1.10.2p2 rsu-firmware-1.2p0 acx-firmware-1.4p5
upgt-firmware-1.1p4 rtwn-firmware-1.0 malo-firmware-1.4p4
uvideo-firmware-1.2p2

And the device is there:
# usbdevs -vdf /dev/usb0
Controller /dev/usb0:
addr 1: high speed, self powered, config 1, EHCI root hub(0x),
ATI(0x1002), rev 1.00
  uhub0
 port 1 powered
 port 2 powered
 port 3 powered
 port 4 powered
 port 5 addr 2: high speed, power 500 mA, config 1, UB93(0x3327),
ATHEROS(0x13d3), rev 1.08, iSerialNumber 12345
   athn0

According to the manufacturer
(https://www.olimex.com/Products/USB-Modules/MOD-WIFI-AR9271-ANT/)
this is an AR9271 chip, which is listed on the athn man page. What am
I missing?

Thanks

Max

Re: bioctl crypto size limitation ?

[sharon s.]

On 05/25/17 22:59, Florian Ermisch wrote:

Just make slice sd0a smaller
than 100% of the RAID array.

Regards, Florian

Am 25. Mai 2017 19:03:59 MESZ schrieb myml...@gmx.com:

I'm wondering if there is a limit to the size of a disk for full disk
encryption.

I'm trying to encrypt a 32Tb raid 6 drive on a lsi 9265-8i with 8 x 6Tb

drives and it's failing with the error "unknown error". (very
descriptive!)

I was able to encrypt the 256Gb system disk without error during
installation.

Without encrypting the 32Tb drive, I had no problem creating the FS and

mounting it.

I know people will say this is a bad idea because of fsck (and maybe
other reasons), but this drive will be mounted ro 99% of the time.

Steps to recreate:

dd if=/dev/random of=/dev/rsd0c bs=1m   (took over a week)

fdisk -iy -g sd0  (I left off the "-b 960" because this is not a
bootable partiton)

disklabel -E sd0

Label editor (enter '?' for help at any prompt)

a a

offset: [64]
size: [70319603585]
FS type: [4.2BSD] RAID

w
q

# bioctl -v -c C -l sd0a softraid0
New passphrase:
Re-type passphrase:
Deriving key using bcrypt PBKDF with 16 rounds...
bioctl: unknown error


dmesg:

OpenBSD 6.1-current (GENERIC.MP) #54: Thu May 11 19:20:09 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 34333851648 (32743MB)
avail mem = 33287512064 (31745MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0x9d000 (51 entries)
bios0: vendor American Megatrends Inc. version "2.1" date 03/17/2012
bios0: Supermicro X8DT3
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP APIC MCFG SLIT SLIC OEMB SRAT HPET SSDT
acpi0: wakeup devices NPE1(S4) NPE2(S4) NPE3(S4) NPE4(S4) NPE5(S4)
NPE6(S4) NPE7(S4) NPE8(S4) NPE9(S4) NPEA(S4) P0P1(S4) PS2K(S4) USB0(S4)

USB1(S4) USB2(S4) USB5(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.32 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2400324600 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 133MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.00 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 18 (application processor)
cpu2: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.01 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 9, package 0
cpu3 at mainbus0: apid 20 (application processor)
cpu3: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.00 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 10, package 0
cpu4 at mainbus0: apid 32 (application processor)
cpu4: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.01 MHz
cpu4:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 0, core 0, package 1
cpu5 at mainbus0: apid 48 (application processor)
cpu5: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.01 MHz
cpu5:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 0, core 8, package 1
cpu6 at mainbus0: apid 50 (application processor)
cpu6: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.01 MHz
cpu6:

Re: bioctl crypto size limitation ?

[sharon s.]

On 05/26/17 15:49, sharon s. wrote:



On 05/26/17 11:43, Ted Unangst wrote:

  sharon s. wrote:

softraid0: invalid metadata format
You filled the disk with random data, which is not a valid metadata 
format...
I followed the FAQ, 
http://www.openbsd.org/faq/faq14.html#softraidCrypto .
Sorry, I was hasty. You can also try creating smaller partitions. 
16TB, 8TB,

etc. to see what works. That would be helpful information to have.



8Tb seems to be fine, 16 not so much.  Ran into a weird issue where I 
couldn't try with 12Tb.


# dd if=/dev/random of=/dev/rsd0c bs=1m
^C4310+0 records in
4309+0 records out
4518313984 bytes transferred in 90.924 secs (49692799 bytes/sec)
20170526-1539: tbisch@store:/root:# fdisk -iy -g sd0
Writing MBR at offset 0.
Writing GPT.

# disklabel -E sd0
Label editor (enter '?' for help at any prompt)
> a a
offset: [64]
size: [70319603585] 16T
Rounding size to cylinder (16065 sectors): 34359741611
FS type: [4.2BSD] RAID
> w
> q
No label changes.

# bioctl -v -c C -l sd0a softraid0
New passphrase:
Re-type passphrase:
Deriving key using bcrypt PBKDF with 16 rounds...
bioctl: unknown error


# dd if=/dev/random of=/dev/rsd0c bs=1m
^C2465+0 records in
2464+0 records out
2583691264 bytes transferred in 51.839 secs (49840098 bytes/sec)

# fdisk -iy -g  sd0
Writing MBR at offset 0.
Writing GPT.

# disklabel -E sd0
Label editor (enter '?' for help at any prompt)
> a a
offset: [64]
size: [70319603585] 8T
Rounding size to cylinder (16065 sectors): 17179878806
FS type: [4.2BSD] RAID
> w
> q
No label changes.

# bioctl -v -c C -l sd0a softraid0
New passphrase:
Re-type passphrase:
Deriving key using bcrypt PBKDF with 16 rounds...
softraid0: CRYPTO volume attached as sd4


# dd if=/dev/random of=/dev/rsd0c bs=1m
^C2914+0 records in
2913+0 records out
3054501888 bytes transferred in 61.213 secs (49899553 bytes/sec)
20170526-1544: tbisch@store:/root:# fdisk -iy -g sd0
Writing MBR at offset 0.
Writing GPT.

# disklabel -E sd0
Label editor (enter '?' for help at any prompt)
> a a
offset: [64]
size: [70319603585] 12T
Rounding size to cylinder (16065 sectors): 25769818241
FS type: [4.2BSD] RAID
> w
disklabel: ioctl DIOCWDINFO: Open partition would move or shrink
disklabel: unable to write label


Stupid me, I forgot that the softraid device was still attached.

12Tb, 14Tb and 15Tb works as well, 16 seems to be where it breaks.

# dd if=/dev/random of=/dev/rsd0c bs=1m
^C526+0 records in
525+0 records out
550502400 bytes transferred in 11.298 secs (48724516 bytes/sec)
20170526-1551: tbisch@store:/root:# fdisk -iy -g sd0
Writing MBR at offset 0.
Writing GPT.

# disklabel -E sd0
Label editor (enter '?' for help at any prompt)
> a a
offset: [64]
size: [70319603585] 12T
Rounding size to cylinder (16065 sectors): 25769818241
FS type: [4.2BSD] RAID
> w
> q
No label changes.

# bioctl -v -c C -l sd0a softraid0
New passphrase:
Re-type passphrase:
Deriving key using bcrypt PBKDF with 16 rounds...
softraid0: CRYPTO volume attached as sd4


# dd if=/dev/random of=/dev/rsd0c bs=1m
^C1526+0 records in
1525+0 records out
1599078400 bytes transferred in 32.276 secs (49543440 bytes/sec)

# fdisk -iy -g  sd0
Writing MBR at offset 0.
Writing GPT.

# disklabel -E sd0
Label editor (enter '?' for help at any prompt)
> a a
offset: [64]
size: [70319603585] 15T
Rounding size to cylinder (16065 sectors): 32212268801
FS type: [4.2BSD] RAID
> w
> q
No label changes.

# bioctl -v -c C -l sd0a softraid0
New passphrase:
Re-type passphrase:
Deriving key using bcrypt PBKDF with 16 rounds...
softraid0: CRYPTO volume attached as sd4

Re: bioctl crypto size limitation ?

[sharon s.]

On 05/26/17 11:43, Ted Unangst wrote:

  sharon s. wrote:

softraid0: invalid metadata format

You filled the disk with random data, which is not a valid metadata format...

I followed the FAQ, http://www.openbsd.org/faq/faq14.html#softraidCrypto .

Sorry, I was hasty. You can also try creating smaller partitions. 16TB, 8TB,
etc. to see what works. That would be helpful information to have.



8Tb seems to be fine, 16 not so much.  Ran into a weird issue where I 
couldn't try with 12Tb.


# dd if=/dev/random of=/dev/rsd0c bs=1m
^C4310+0 records in
4309+0 records out
4518313984 bytes transferred in 90.924 secs (49692799 bytes/sec)
20170526-1539: tbisch@store:/root:# fdisk -iy -g sd0
Writing MBR at offset 0.
Writing GPT.

# disklabel -E sd0
Label editor (enter '?' for help at any prompt)
> a a
offset: [64]
size: [70319603585] 16T
Rounding size to cylinder (16065 sectors): 34359741611
FS type: [4.2BSD] RAID
> w
> q
No label changes.

# bioctl -v -c C -l sd0a softraid0
New passphrase:
Re-type passphrase:
Deriving key using bcrypt PBKDF with 16 rounds...
bioctl: unknown error


# dd if=/dev/random of=/dev/rsd0c bs=1m
^C2465+0 records in
2464+0 records out
2583691264 bytes transferred in 51.839 secs (49840098 bytes/sec)

# fdisk -iy -g  sd0
Writing MBR at offset 0.
Writing GPT.

# disklabel -E sd0
Label editor (enter '?' for help at any prompt)
> a a
offset: [64]
size: [70319603585] 8T
Rounding size to cylinder (16065 sectors): 17179878806
FS type: [4.2BSD] RAID
> w
> q
No label changes.

# bioctl -v -c C -l sd0a softraid0
New passphrase:
Re-type passphrase:
Deriving key using bcrypt PBKDF with 16 rounds...
softraid0: CRYPTO volume attached as sd4


# dd if=/dev/random of=/dev/rsd0c bs=1m
^C2914+0 records in
2913+0 records out
3054501888 bytes transferred in 61.213 secs (49899553 bytes/sec)
20170526-1544: tbisch@store:/root:# fdisk -iy -g sd0
Writing MBR at offset 0.
Writing GPT.

# disklabel -E sd0
Label editor (enter '?' for help at any prompt)
> a a
offset: [64]
size: [70319603585] 12T
Rounding size to cylinder (16065 sectors): 25769818241
FS type: [4.2BSD] RAID
> w
disklabel: ioctl DIOCWDINFO: Open partition would move or shrink
disklabel: unable to write label

Re: bioctl crypto size limitation ?

[sharon s.]

On 05/26/17 12:00, Christian Weisgerber wrote:

On 2017-05-25, myml...@gmx.com  wrote:


fdisk -iy -g sd0  (I left off the "-b 960" because this is not a
bootable partiton)

Back in March, Eric Huiban noticed this:

| i just performed some remote connection... recreating GPT with an .i EFI
| boot partition. The softraid is now 2.7TiB... Grumbl! conclusion :
| bioctl needs a mandatory bootable partition to act correctly even on
| disks not aimed to be bootable.

https://marc.info/?l=openbsd-misc=148854591221493=2


using the "-b 960" doesn't help:

# dd if=/dev/random of=/dev/rsd0c bs=1m

^C18404+0 records in
18403+0 records out
19296944128 bytes transferred in 386.986 secs (49864646 bytes/sec)


# fdisk -iy -g -b 960 sd0
Writing MBR at offset 0.
Writing GPT.


# disklabel -E sd0
Label editor (enter '?' for help at any prompt)
> a a
offset: [1024]
size: [70319602625]
FS type: [4.2BSD] RAID
> w
> q
No label changes.

:# bioctl -v -c C -l sd0a softraid0
New passphrase:
Re-type passphrase:
Deriving key using bcrypt PBKDF with 16 rounds...
bioctl: unknown error

Re: bioctl crypto size limitation ?

[sharon s.]

On 05/26/17 09:11, Joel Sing wrote:

On Saturday 27 May 2017 01:56:06 Joel Sing wrote:

On Friday 26 May 2017 01:05:59 sharon s. wrote:

On 05/26/17 00:45, Ted Unangst wrote:

myml...@gmx.com wrote:

Steps to recreate:

dd if=/dev/random of=/dev/rsd0c bs=1m   (took over a week)

fdisk -iy -g sd0  (I left off the "-b 960" because this is not a
bootable partiton)

disklabel -E sd0

Label editor (enter '?' for help at any prompt)

   > a a

offset: [64]
size: [70319603585]
FS type: [4.2BSD] RAID

   > w
   > q

# bioctl -v -c C -l sd0a softraid0
New passphrase:
Re-type passphrase:
Deriving key using bcrypt PBKDF with 16 rounds...
bioctl: unknown error

softraid0: invalid metadata format

You filled the disk with random data, which is not a valid metadata
format...

I followed the FAQ, http://www.openbsd.org/faq/faq14.html#softraidCrypto .

Hrmmm, it looks like that part of the FAQ is incorrect or missing a step.
You should be able to work around it by either zeroing the first ~1MB of
disk (per the FAQ), or by using 'bioctl -C force' (carefully).

Actually, re-reading this it should be correct - the "invalid metadata format"
error is more likely indicating an issue identifying the partition type/size
(as unhelpful as that is). Could you provide the output from `disklabel sd0'?

Currently have have created a standard filesystem and have it mounted, 
disklable looks like so:


20170526-1519: tbisch@store:/root:# disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: MR9265-8i
duid: 194997bb8410087b
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 4377192
total sectors: 70319603712
boundstart: 1024
boundend: 70319603649
drivedata: 0

16 partitions:
#size   offset  fstype [fsize bsize   cpg]
  a:  70319602560 1024  4.2BSD   8192 65536 52270 # /data
  c:  703196037120  unused
  i:  960   64   MSDOS

I was a little surprised that the offset was 1024, haven't seen that before.

If i unmount, send some random data to the drive, re-init the drive and 
then run run disklabel it looks like so:

# umount /backup

# dd if=/dev/random of=/dev/rsd0c bs=1m
^C7342+0 records in
7341+0 records out
7697596416 bytes transferred in 153.355 secs (50194418 bytes/sec)

# fdisk -iy -g sd0
Writing MBR at offset 0.
Writing GPT.


# disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: MR9265-8i
duid: 8100dcb121ad1107
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 4377192
total sectors: 70319603712
boundstart: 64
boundend: 70319603649
drivedata: 0

16 partitions:
#size   offset  fstype [fsize bsize   cpg]
  a:  70319603585   64RAID
  c:  703196037120  unused

Additionally, the system kernel paniced when I was moving data to it the 
other day, the automatic fsck took 8 minutes for the 32Tb drive.

Re: Valgrind W^X Violation

[Stuart Henderson]

[ moved to ports@ ]

On 2017-05-25, Peter Ezetta  wrote:
> Hello Misc,
>
> I have been trying to get Valgrind to run on OpenBSD 6.1-release, with
> all errata applied via syspatch(8), and I am having no luck. When
> executing Valgrind against any binary (or no binary at all), it claims to
> run out of memory and dumps a W^X violation error into the dmesg
> output.
>
> There have been several other mailing list posts about this issue over
> the last few months, but nothing seems to have come of it:
>
> http://openbsd-archive.7691.n7.nabble.com/valgrind-error-W-X-violation-td299828.html
> http://openbsd-archive.7691.n7.nabble.com/W-X-issues-running-valgrind-td305977.html
>
> I have tried reaching out to the package maintainer listed in pkg_info,
> but haven’t heard anything back yet. Is there anything that I can do to
> assist in debugging and fixing this issue? If it would be of any use to
> anyone, I have ktrace dumps, but the output was a bit verbose for an
> already long email. I can forward along if it would be helpful.
>
> It appears that the next step may be to update my system to follow current,
> grab a copy of the ports tree, and attempt to build the package with
> -Wl,-z,wxneeded. Am I on the right track here?

I just committed a diff adding USE_WXNEEDED=Yes and the patch from
https://marc.info/?l=openbsd-ports=149541633922860=2 which removes
the most major breakage. (It will show up in package snaps in a few days,
if you want to build it yourself you must use a port build directory on
a "wxallowed" filesystem, e.g. you could do something like
"make WRKOBJDIR=/usr/local/pobj package"

Also note (especially if you try it with programs from OpenBSD base),
if a program uses pledge(2) this may interfere with valgrind.

Caveat emptor: since it has been broken for ~ a year, I think it's
safe to say that this port is not really maintained any more.

Re: Limits on OBSD amd64

[STeve Andre']

On 05/26/17 10:28, Stuart Henderson wrote:

On 2017-05-26, Friedrich Locke  wrote:

Hi folks,

i wonder what is the maximum file system size OBSD supports using different
file systems like FFS


afaik, this is 1TB


FFS2


"as much as you have RAM to fsck"...


and ZFS ?


0 bytes.





On a 10T disk I created an 8T file with dd=/dev/zero of=bff.  I didn't
test it, but saw that I had the correct amount of space left.

--STeve Andre'

Re: bioctl crypto size limitation ?

[Paul de Weerd]

On Thu, May 25, 2017 at 10:03:59AM -0700, myml...@gmx.com wrote:
| I'm wondering if there is a limit to the size of a disk for full disk
| encryption.

My biggest crypto disk is:

[weerd@pom] $ df -h /store
Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/sd16a 5.4T841G4.3T16%/store

[weerd@pom] $ dmesg | grep sd16
sd16 at scsibus12 targ 2 lun 0:  SCSI2 0/direct fixed
sd16: 5723166MB, 512 bytes/sector, 11721044513 sectors

It is backed by this physical disk:

[weerd@pom] $ doas bioctl -vhi softraid0 
Volume  Status   Size Device  
softraid0 1 Online   5.5T sd16CRYPTO
  0 Online   5.5T 1:0.0   noencl 
 'unknown serial'

[weerd@pom] $ dmesg | grep -e '^sd1[ :]'
sd1 at scsibus1 targ 2 lun 0:  SCSI3 0/direct 
fixed naa.50014ee2b81f4111
sd1: 5723166MB, 512 bytes/sector, 11721045168 sectors

disklabels are as follows:

sd1:
16 partitions:
#size   offset  fstype [fsize bsize   cpg]
  a:  11721045041   64RAID
  c:  117210451680  unused

sd16:
#size   offset  fstype [fsize bsize   cpg]
  a:  11721044288   64  4.2BSD   8192 65536 52270 # /store
  c:  117210445130  unused

I did not create the -b special boot partition on either of these
volumes.  Everything worked just fine without.  The reduction in
sector count is due to rounding.

Cheers,

Paul 'WEiRD' de Weerd

| I'm trying to encrypt a 32Tb raid 6 drive on a lsi 9265-8i with 8 x 6Tb
| drives and it's failing with the error "unknown error". (very descriptive!)
| 
| I was able to encrypt the 256Gb system disk without error during
| installation.
| 
| Without encrypting the 32Tb drive, I had no problem creating the FS and
| mounting it.
| 
| I know people will say this is a bad idea because of fsck (and maybe other
| reasons), but this drive will be mounted ro 99% of the time.
| 
| Steps to recreate:
| 
| dd if=/dev/random of=/dev/rsd0c bs=1m   (took over a week)
| 
| fdisk -iy -g sd0  (I left off the "-b 960" because this is not a bootable
| partiton)
| 
| disklabel -E sd0
| 
| Label editor (enter '?' for help at any prompt)
| > a a
| offset: [64]
| size: [70319603585]
| FS type: [4.2BSD] RAID
| > w
| > q
| 
| # bioctl -v -c C -l sd0a softraid0
| New passphrase:
| Re-type passphrase:
| Deriving key using bcrypt PBKDF with 16 rounds...
| bioctl: unknown error
| 
| 
| dmesg:
| 
| OpenBSD 6.1-current (GENERIC.MP) #54: Thu May 11 19:20:09 MDT 2017
| dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
| real mem = 34333851648 (32743MB)
| avail mem = 33287512064 (31745MB)
| mpath0 at root
| scsibus0 at mpath0: 256 targets
| mainbus0 at root
| bios0 at mainbus0: SMBIOS rev. 2.6 @ 0x9d000 (51 entries)
| bios0: vendor American Megatrends Inc. version "2.1" date 03/17/2012
| bios0: Supermicro X8DT3
| acpi0 at bios0: rev 2
| acpi0: sleep states S0 S1 S4 S5
| acpi0: tables DSDT FACP APIC MCFG SLIT SLIC OEMB SRAT HPET SSDT
| acpi0: wakeup devices NPE1(S4) NPE2(S4) NPE3(S4) NPE4(S4) NPE5(S4) NPE6(S4)
| NPE7(S4) NPE8(S4) NPE9(S4) NPEA(S4) P0P1(S4) PS2K(S4) USB0(S4) USB1(S4)
| USB2(S4) USB5(S4) [...]
| acpitimer0 at acpi0: 3579545 Hz, 24 bits
| acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
| cpu0 at mainbus0: apid 0 (boot processor)
| cpu0: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.32 MHz
| cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
| cpu0: 256KB 64b/line 8-way L2 cache
| cpu0: TSC frequency 2400324600 Hz
| cpu0: smt 0, core 0, package 0
| mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
| cpu0: apic clock running at 133MHz
| cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
| cpu1 at mainbus0: apid 2 (application processor)
| cpu1: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.00 MHz
| cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
| cpu1: 256KB 64b/line 8-way L2 cache
| cpu1: smt 0, core 1, package 0
| cpu2 at mainbus0: apid 18 (application processor)
| cpu2: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.01 MHz
| cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
| cpu2: 256KB 64b/line 8-way L2 cache
| cpu2: smt 0, core 

Re: bioctl crypto size limitation ?

[Christian Weisgerber]

On 2017-05-25, myml...@gmx.com  wrote:

> fdisk -iy -g sd0  (I left off the "-b 960" because this is not a 
> bootable partiton)

Back in March, Eric Huiban noticed this:

| i just performed some remote connection... recreating GPT with an .i EFI
| boot partition. The softraid is now 2.7TiB... Grumbl! conclusion : 
| bioctl needs a mandatory bootable partition to act correctly even on 
| disks not aimed to be bootable.

https://marc.info/?l=openbsd-misc=148854591221493=2

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de

Re: bioctl crypto size limitation ?

[Ted Unangst]

 sharon s. wrote:
> >
> >> softraid0: invalid metadata format
> > You filled the disk with random data, which is not a valid metadata 
> > format...
> I followed the FAQ, http://www.openbsd.org/faq/faq14.html#softraidCrypto .

Sorry, I was hasty. You can also try creating smaller partitions. 16TB, 8TB,
etc. to see what works. That would be helpful information to have.

Re: ldapd dies with assert failure

[Allan Streib]

> assertion "p->upper >= p->lower" failed: file 
> "/usr/src/usr.sbin/ldapd/btree.c", line 1949, function "btree_add_node"

A follow-up for those not reading bugs@

ldapd sets its page size based on the block size of the filesystem. If
this is large (> 1TB?) and uses FFS2 then the block size is larger than
uint16_t, causing the failed assertion.

A workaround for now is to be sure your ldap db files are on a partition
with a block size < 65535. Use dumpfs(8) to check.

Thanks Todd and Stuart for the help.

Allan

Re: Limits on OBSD amd64

[Kamil Cholewiński]

On Fri, 26 May 2017, Stuart Henderson  wrote:
>> and ZFS ?
>
> 0 bytes.

-1 bytes and ENOENT? :)

Re: bioctl crypto size limitation ?

[Joel Sing]

On Saturday 27 May 2017 01:56:06 Joel Sing wrote:
> On Friday 26 May 2017 01:05:59 sharon s. wrote:
> > On 05/26/17 00:45, Ted Unangst wrote:
> > > myml...@gmx.com wrote:
> > >> Steps to recreate:
> > >> 
> > >> dd if=/dev/random of=/dev/rsd0c bs=1m   (took over a week)
> > >> 
> > >> fdisk -iy -g sd0  (I left off the "-b 960" because this is not a
> > >> bootable partiton)
> > >> 
> > >> disklabel -E sd0
> > >> 
> > >> Label editor (enter '?' for help at any prompt)
> > >> 
> > >>   > a a
> > >> 
> > >> offset: [64]
> > >> size: [70319603585]
> > >> FS type: [4.2BSD] RAID
> > >> 
> > >>   > w
> > >>   > q
> > >> 
> > >> # bioctl -v -c C -l sd0a softraid0
> > >> New passphrase:
> > >> Re-type passphrase:
> > >> Deriving key using bcrypt PBKDF with 16 rounds...
> > >> bioctl: unknown error
> > >> 
> > >> softraid0: invalid metadata format
> > > 
> > > You filled the disk with random data, which is not a valid metadata
> > > format...
> > 
> > I followed the FAQ, http://www.openbsd.org/faq/faq14.html#softraidCrypto .
> 
> Hrmmm, it looks like that part of the FAQ is incorrect or missing a step.
> You should be able to work around it by either zeroing the first ~1MB of
> disk (per the FAQ), or by using 'bioctl -C force' (carefully).

Actually, re-reading this it should be correct - the "invalid metadata format" 
error is more likely indicating an issue identifying the partition type/size 
(as unhelpful as that is). Could you provide the output from `disklabel sd0'?

Re: bioctl crypto size limitation ?

[Joel Sing]

On Friday 26 May 2017 01:05:59 sharon s. wrote:
> On 05/26/17 00:45, Ted Unangst wrote:
> > myml...@gmx.com wrote:
> >> Steps to recreate:
> >> 
> >> dd if=/dev/random of=/dev/rsd0c bs=1m   (took over a week)
> >> 
> >> fdisk -iy -g sd0  (I left off the "-b 960" because this is not a
> >> bootable partiton)
> >> 
> >> disklabel -E sd0
> >> 
> >> Label editor (enter '?' for help at any prompt)
> >> 
> >>   > a a
> >> 
> >> offset: [64]
> >> size: [70319603585]
> >> FS type: [4.2BSD] RAID
> >> 
> >>   > w
> >>   > q
> >> 
> >> # bioctl -v -c C -l sd0a softraid0
> >> New passphrase:
> >> Re-type passphrase:
> >> Deriving key using bcrypt PBKDF with 16 rounds...
> >> bioctl: unknown error
> >> 
> >> softraid0: invalid metadata format
> > 
> > You filled the disk with random data, which is not a valid metadata
> > format...
>
> I followed the FAQ, http://www.openbsd.org/faq/faq14.html#softraidCrypto .

Hrmmm, it looks like that part of the FAQ is incorrect or missing a step. You 
should be able to work around it by either zeroing the first ~1MB of disk (per 
the FAQ), or by using 'bioctl -C force' (carefully).

Re: file systems

[Christer Solskogen]

One 27T drive?!


On May 26, 2017 17:27, "Scott Bonds"  wrote:

> I've got a 27T drive, single partition, about half full. Combination of
> big files and lots of small ones. 32G of ECC RAM. Hardware RAID5 ATM though
> I've used software RAID5 on the same array and that was good too.  I keep
> offline backups of everything. I think it takes around an hour to fsck, but
> I haven't timed it. Not using softdep. Not RO. Not sure what the file
> system is, whatever newfs chose...disklabel says fstype is 4.2BSD.
>
> On 05/26, Peter Hessler wrote:
>
>> On 2017 May 26 (Fri) at 11:35:49 -0300 (-0300), Friedrich Locke wrote:
>> :Hi folks,
>> :
>> :does anybody here run OBSD with a file system bigger than 10TB ?
>> :How much time boot takes to bring the system up (i mean fsck) ?
>> :Are you using ffs2 ? With softdep ?
>> :
>> :Thanks.
>>
>> I created a 24T disk with ff2.  I populated 2Tb of it while in async
>> mode, then pulled the power.  fsck took only 5 minutes.
>>
>> Later, I repartitioned the machine to the sizes we actually want
>> (several 5T partitions) and it is running as ftp.hostserver.de.  We
>> aren't using softdep, and generally run RO on many of the partitions.
>>
>> Please give it a try on your own hardware, paritition sizes, and
>> collection of files.
>>
>> --
>> Don't say "yes" until I finish talking.
>> -- Darryl F. Zanuck
>>
>>
>

Re: file systems

[Steven McDonald]

On Fri, 26 May 2017 11:35:49 -0300
Friedrich Locke  wrote:

> Hi folks,
> 
> does anybody here run OBSD with a file system bigger than 10TB ?
> How much time boot takes to bring the system up (i mean fsck) ?
> Are you using ffs2 ? With softdep ?
> 
> Thanks.

This depends heavily on how you plan to use the filesystem. I have an 8
TB filesystem (FFS2 with softdep) that takes several hours to fsck,
mostly in phase 2 ("Check Pathnames") because of a very large number of
hard links.

Re: file systems

[Scott Bonds]

I've got a 27T drive, single partition, about half full. Combination of 
big files and lots of small ones. 32G of ECC RAM. Hardware RAID5 ATM 
though I've used software RAID5 on the same array and that was good too.  
I keep offline backups of everything. I think it takes around an hour to 
fsck, but I haven't timed it. Not using softdep. Not RO. Not sure what 
the file system is, whatever newfs chose...disklabel says fstype is 
4.2BSD.


On 05/26, Peter Hessler wrote:

On 2017 May 26 (Fri) at 11:35:49 -0300 (-0300), Friedrich Locke wrote:
:Hi folks,
:
:does anybody here run OBSD with a file system bigger than 10TB ?
:How much time boot takes to bring the system up (i mean fsck) ?
:Are you using ffs2 ? With softdep ?
:
:Thanks.

I created a 24T disk with ff2.  I populated 2Tb of it while in async
mode, then pulled the power.  fsck took only 5 minutes.

Later, I repartitioned the machine to the sizes we actually want
(several 5T partitions) and it is running as ftp.hostserver.de.  We
aren't using softdep, and generally run RO on many of the partitions.

Please give it a try on your own hardware, paritition sizes, and
collection of files.

--
Don't say "yes" until I finish talking.
-- Darryl F. Zanuck

Re: smtpd doesn't start

[Mik J]

Hello,I had the same problem recently.Please check the rights on the file 
smtpd.conf and if necessary chmod 600 smtpd.conf

 

Le Vendredi 26 mai 2017 15h08, Ted Unangst  a écrit :
 

 Choose a display name wrote:
> >As always, you can post your smtpd.config, dmesg and any errors
> >you're receiving. "it doesn't work" and "i have a problem" won't
> >get you much help on this list.
> 
> I get no error, smtpd just hangs if network is up.
> It looks like this:
> 
> # smtpctl show stats
> smtpctl: smtpd doesn't seem to be running
> # /usr/sbin/smtpd
> (it hangs without any output)
> ^C

this sounds a lot like a DNS failure.



   

Re: bioctl crypto size limitation ?

[sharon s.]

On 05/26/17 00:45, Ted Unangst wrote:

myml...@gmx.com wrote:

Steps to recreate:

dd if=/dev/random of=/dev/rsd0c bs=1m   (took over a week)

fdisk -iy -g sd0  (I left off the "-b 960" because this is not a
bootable partiton)

disklabel -E sd0

Label editor (enter '?' for help at any prompt)
  > a a
offset: [64]
size: [70319603585]
FS type: [4.2BSD] RAID
  > w
  > q

# bioctl -v -c C -l sd0a softraid0
New passphrase:
Re-type passphrase:
Deriving key using bcrypt PBKDF with 16 rounds...
bioctl: unknown error



softraid0: invalid metadata format

You filled the disk with random data, which is not a valid metadata format...

I followed the FAQ, http://www.openbsd.org/faq/faq14.html#softraidCrypto .

Re: file systems

[Peter Hessler]

On 2017 May 26 (Fri) at 11:35:49 -0300 (-0300), Friedrich Locke wrote:
:Hi folks,
:
:does anybody here run OBSD with a file system bigger than 10TB ?
:How much time boot takes to bring the system up (i mean fsck) ?
:Are you using ffs2 ? With softdep ?
:
:Thanks.

I created a 24T disk with ff2.  I populated 2Tb of it while in async
mode, then pulled the power.  fsck took only 5 minutes.

Later, I repartitioned the machine to the sizes we actually want
(several 5T partitions) and it is running as ftp.hostserver.de.  We
aren't using softdep, and generally run RO on many of the partitions.

Please give it a try on your own hardware, paritition sizes, and
collection of files.

-- 
Don't say "yes" until I finish talking.
-- Darryl F. Zanuck

file systems

[Friedrich Locke]

Hi folks,

does anybody here run OBSD with a file system bigger than 10TB ?
How much time boot takes to bring the system up (i mean fsck) ?
Are you using ffs2 ? With softdep ?

Thanks.

Re: Limits on OBSD amd64

[Stuart Henderson]

On 2017-05-26, Friedrich Locke  wrote:
> Hi folks,
>
> i wonder what is the maximum file system size OBSD supports using different
> file systems like FFS

afaik, this is 1TB

> FFS2

"as much as you have RAM to fsck"...

> and ZFS ?

0 bytes.

Autoinstall ... too "auto"?

[Erling Westenvik]

Autoinstall(8) and its ability to automate the trivial but time
consuming task of typing info like keyboard layout and network setup -
not to mention encrypted passwords and ssh keys! - by supplying the
information in a response file, is great. Add the ability to supply a
template for disklabel and it is absolutely wonderful.

However, there appears to be a fly in the ointment: If you want to
deviate from the "one disk, one disklabel"-dogma, like when needing a
partially encrypted installation, you're out of luck!

I'm in need of rolling out machines with a close to FDE configuration.
"Close to" meaning a single physical disk where everything is encrypted
except for a root partition. (Please don't ask why. I have good reasons
and run a lot of machines with a setup like this. I would simply like to
automate the cumbersome installation process.)

I do a PXE boot and select (S)hell to prepare the disk after bsd.rd has
fired up:

   # disklabel -E sd0 (phsyical disk)
   a a  (specifying a 1G partion)
   a p  (specifying a 249G for softraid crypto)
   w
   q

   # bioctl -c C -l /dev/sd0p softraid0
   entering passphrase x 2

   # cd /dev; sh ./MAKEDEV sd1

Then I start autoinstall:

   # autoinstall

So far so good. At this point autoinstall will recognize the root disk
[sd0] and the additional encrypted volume [sd1].

   Available disks are sd0, sd1.

In the response file I have:

   Which disk is the root disk = sd0

But, from here on things start to go wrong.

If I'm not supplying a template for disklabel, the installer will assume
I want to use the whole disk and will autopartition it, removing the
crypto partition (p) in the process. But, if I DO supply a template for
disklabel, the installer will ALSO remove the crypto partion. It may
fail with:

   disklabel: ioctl DIOCWDINFO: Open partition would move or shrink

Guess I'm out of luck and will have to revert to manual install.

>From what I'm able to infer, autoinstall (and perhaps the manuel
installer as well) would benefit from being able to recognize something
like:

   Use (A)uto layout, (E)dit auto layout, (K)eep existing layout or

   create (C)ustom layout = K

That way, one could manually setup disks and initiate any RAID
configuration before starting autoinstall - leaning back and watch it
complete the job?

Erling

Re: smtpd doesn't start

[Ted Unangst]

Choose a display name wrote:
> >As always, you can post your smtpd.config, dmesg and any errors
> >you're receiving. "it doesn't work" and "i have a problem" won't
> >get you much help on this list.
> 
> I get no error, smtpd just hangs if network is up.
> It looks like this:
> 
> # smtpctl show stats
> smtpctl: smtpd doesn't seem to be running
> # /usr/sbin/smtpd
> (it hangs without any output)
> ^C

this sounds a lot like a DNS failure.

Re: smtpd doesn't start

[Choose a display name]

>As always, you can post your smtpd.config, dmesg and any errors
>you're receiving. "it doesn't work" and "i have a problem" won't
>get you much help on this list.

I get no error, smtpd just hangs if network is up.
It looks like this:

# smtpctl show stats
smtpctl: smtpd doesn't seem to be running
# /usr/sbin/smtpd
(it hangs without any output)
^C
# /usr/sbin/smtpd -dv
(same thing)
^C
# /usr/sbin/smtpd -n
(hangs again)
^C
# ifconfig athn0 down
# /usr/sbin/smtpd -d
info: OpenSMTPD 6.0.0 starting
# smtpctl show stats
control.session=1
...
# cat /etc/mail/smtpd.conf
# $OpenBSD: smtpd.conf,v 1.9 2016/05/03 18:43:45 jung Exp $

# This is the smtpd server system-wide configuration file.
# See smtpd.conf(5) for more information.

table aliases file:/etc/mail/aliases

# To accept external mail, replace with: listen on all
#
listen on lo0

# Uncomment the following to accept external mail for domain "example.org"
#
# accept from any for domain "example.org" alias  deliver to mbox
accept for local alias  deliver to mbox
accept from local for any relay
# cat /etc/hostname.athn0
nwid nwid
wpakey wpakey
dhcp
# dmesg
OpenBSD 6.1 (GENERIC.MP) #6: Mon May 22 20:34:30 CEST 2017
rob...@syspatch-61-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
.MP
real mem = 8533958656 (8138MB)
avail mem = 8270639104 (7887MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7daa0020 (8 entries)
bios0: vendor coreboot version "CBET4000 4.5" date 10/18/2016
bios0: LENOVO 745584G
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT MCFG TCPA APIC DMAR HPET
acpi0: wakeup devices HDEF(S4) USB1(S4) USB2(S4) USB3(S4) EHC1(S4) USB4(S4) USB5
(S4) USB6(S4) EHC2(S4) SLT1(S4) SLT2(S4) SLT3(S4) SLT6(S4) LANC(S3) LANR(S3) 
SLPB(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0 addr 0xf000, bus 0-63
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz, 1600.34 MHz
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR
cpu0: 3MB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 266MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz, 1600.06 MHz
cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR
cpu1: 3MB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEGP)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP02)
acpiprt4 at acpi0: bus 3 (RP03)
acpiprt5 at acpi0: bus 4 (RP04)
acpiprt6 at acpi0: bus -1 (RP05)
acpiprt7 at acpi0: bus -1 (RP06)
acpiprt8 at acpi0: bus 5 (PCIB)
acpiec0 at acpi0
acpicpu0 at acpi0
C1: bogo buffer
C2: bogo buffer
C3: bogo buffer: C1(@1 halt!), PSS
acpicpu1 at acpi0
C1: bogo buffer
C2: bogo buffer
C3: bogo buffer: C1(@1 halt!), PSS
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at acpi0: critical temperature is 99 degC
acpithinkpad0 at acpi0
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT0 model "08K8193" serial 15 type LION oem "JingYi"
acpibat1 at acpi0: BAT1 not present
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: LID_
"PNP0303" at acpi0 not configured
"PNP0F13" at acpi0 not configured
"GOOGCB00" at acpi0 not configured
acpidock0 at acpi0: DOCK not docked (0)
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: LCD0
cpu0: Enhanced SpeedStep 1600 MHz: speeds: 2401, 2400, 1600, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07
inteldrm0 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0: msi
inteldrm0: 1280x800, 32bpp
error: [drm:pid0:intel_pipe_config_compare] *ERROR* mismatch in adjusted_mode.fl
ags(DRM_MODE_FLAG_PHSYNC) (expected 0, found 1)
pipe state doesn't match!
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured
em0 at pci0 dev 25 function 0 "Intel ICH9 IGP M" rev 0x03: msi, address 00:11:22
:33:44:55
uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 2 int 16
uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 2 int 17
uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 2 int 18

ipsec.conf

[Hrvoje Popovski]

Hi all,

i having ipsec.conf like this:

ike esp from 10.200.136.0/21 to any \
local 10.64.135.246 peer 10.4.57.68 \
main auth hmac-sha1 enc aes group modp1024 \
quick auth hmac-sha1 enc aes group modp1024 \
psk b9278b3051cd17674305833971c22b11514eac51


and with ipsecctl -nvf ipsec.conf i'm getting

C add
[phase1-peer-10.4.57.68-local-10.64.135.246]:Transforms=phase1-transform-peer-10.4.57.68-local-10.64.135.246-RSA_SIG-SHA-AES128-MODP_3072
force

C set
[phase2-protocol-from-10.200.136.0/21-to-0.0.0.0/0]:Transforms=phase2-transform-from-10.200.136.0/21-to-0.0.0.0/0-AES128-SHA2_256-MODP_3072-TUNNEL
force

full output of ipsecctl -nvf in attachment


but if i put psk before "main auth ..."  i'm getting:


C add
[phase1-peer-10.4.57.68-local-10.64.135.246]:Transforms=phase1-transform-peer-10.4.57.68-local-10.64.135.246-PRE_SHARED-SHA-AES128-MODP_3072
force

C set
[phase2-protocol-from-10.200.136.0/21-to-0.0.0.0/0]:Transforms=phase2-transform-from-10.200.136.0/21-to-0.0.0.0/0-AES128-SHA2_256-MODP_3072-TUNNEL
force


but still i'm getting AES128-SHA2_256-MODP_3072 although i configured
modp1024 or modp4096 and sha1 


am i doing something wrong here?



OpenBSD 6.1-current (GENERIC.MP) #10: Sun May 21 15:47:29 CEST 2017
hrv...@x3550m4.srce.hr:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 34314383360 (32724MB)
avail mem = 33268629504 (31727MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7e67b000 (84 entries)
bios0: vendor IBM version "-[D7E156DUS-2.30]-" date 11/09/2016
bios0: IBM IBM System x3550 M4 -[791425Z]-
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP TCPA ERST HEST HPET APIC MCFG OEM0 OEM1 SLIT
SRAT SLIC SSDT SSDT SSDT SSDT DMAR
acpi0: wakeup devices MRP1(S4) DCC0(S4) MRP3(S4) MRP5(S4) EHC2(S5)
PEX0(S5) PEX7(S5) EHC1(S5) IP2P(S3) MRPB(S4) MRPC(S4) MRPD(S4) MRPF(S4)
MRPG(S4) MRPH(S4) MRPI(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz, 2100.31 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2100305700 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz, 2099.99 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz, 2099.99 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz, 2099.99 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 8 (application processor)
cpu4: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz, 2099.99 MHz
cpu4:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 0, core 4, package 0
cpu5 at mainbus0: apid 10 (application processor)
cpu5: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz, 2099.99 MHz
cpu5:

Banana Pi R1 - working dwge(4)

[Peter J. Philipp]

Hi,

With the help of Francisco Gaitan, who set up a remote console to the 
Banana Pi R1 I donated to him last year, I have put together the driver for
this device.  It is based on Paul Irofti's brswphy(4) in part and on
Wolfgang Solfrank's bswphy.c driver.  I just put these drivers together and
they worked after reboot.  Here is Francisco's mail to openbsd-arm requesting
a driver:

http://marc.info/?l=openbsd-arm=147637120802717=2

So far as far as I understand it the port on port0 works.  I'm unsure if any
port will work really.  We're gonna look at setting up this device with vlan's
to the BCM53125 which supports vlans, but that'll take more analysis on my end.

If there is will to put this into OpenBSD by a developer I'm willing to put
this together into a patch.  We used sources from -current from a few days
ago so it's fairly up to date.

dmesg follow after my signature.

-peter

rebooting...

U-Boot SPL 2017.03 (Apr 01 2017 - 16:25:44)
DRAM: 1024 MiB
CPU: 91200Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1


U-Boot 2017.03 (Apr 01 2017 - 16:25:44 -0600) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Lamobo R1
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:serial
Out:   serial
Err:   serial
SCSI:  SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   eth0: ethernet@01c5
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found
   scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found EFI removable media binary efi/boot/bootarm.efi
reading efi/boot/bootarm.efi
64684 bytes read in 38 ms (1.6 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
## Starting EFI application at 4200 ...
Scanning disks on scsi...
Scanning disks on usb...
Scanning disks on mmc...
MMC Device 1 not found
MMC Device 2 not found
MMC Device 3 not found
Found 6 disks
>> OpenBSD/armv7 BOOTARM 0.5
boot>
booting sd0a:/bsd: 3860936+161388+491228 [80+511648+239985]=0x506f48

OpenBSD/armv7 booting ...
arg0 0xc0806f48 arg1 0x0 arg2 0x4800
Allocating page tables
freestart = 0x40807000, free_pages = 260089 (0x0003f7f9)
IRQ stack: p0x40835000 v0xc0835000
ABT stack: p0x40836000 v0xc0836000
UND stack: p0x40837000 v0xc0837000
SVC stack: p0x40838000 v0xc0838000
Creating L1 page table at 0x40808000
Mapping kernel
Constructing L2 page tables
undefined page pmap [ using 752128 bytes of bsd ELF symbol table ]
board type: 0
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2017 OpenBSD. All rights reserved.  https://www.OpenBSD.org

OpenBSD 6.1-current (GENERIC) #1: Mon May 22 17:46:54 CEST 2017
r...@cerium.rootbark.com:/usr/src/sys/arch/armv7/compile/GENERIC
real mem  = 1073741824 (1024MB)
avail mem = 1044307968 (995MB)
mainbus0 at root: Lamobo R1
cpu0 at mainbus0: ARM Cortex A7 rev 4 (ARMv7 core)
cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
cpu0: 32KB(32b/l,2way) I-cache, 32KB(64b/l,4way) wr-back D-cache
cortex0 at mainbus0
sxiccmu0 at mainbus0
psci0 at mainbus0
agtimer0 at mainbus0: tick rate 24000 KHz
simplebus0 at mainbus0: "soc"
sxipio0 at simplebus0: 175 pins
sximmc0 at simplebus0
sdmmc0 at sximmc0: 4-bit, sd high-speed, mmc high-speed, dma
ehci0 at simplebus0
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Generic EHCI root hub" rev 2.00/1.00 
addr 1
sxiahci0 at simplebus0: AHCI 1.1
scsibus0 at sxiahci0: 32 targets
ehci1 at simplebus0
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Generic EHCI root hub" rev 2.00/1.00 
addr 1
sxidog0 at simplebus0
sxirtc0 at simplebus0
com0 at simplebus0: ns16550, no working fifo
com0: console
com1 at simplebus0: ns16550, no working fifo
com2 at simplebus0: ns16550, no working fifo
dwge0 at simplebus0
dwge0: address: 02:d7:08:00:d0:8b
bswphy0 at dwge0 phy 0: BCM53125 1000baseT PHY, rev. 4
ifmedia_set: no match for 0x100/0xfffe
ampintc0 at simplebus0 nirq 160, ncpu 2
gpio0 at sxipio0: 32 pins
gpio1 at sxipio0: 32 pins
gpio2 at sxipio0: 32 pins
gpio3 at sxipio0: 32 pins
gpio4 at sxipio0: 32 pins
gpio5 at sxipio0: 32 pins
gpio6 at sxipio0: 32 pins
gpio7 at sxipio0: 32 pins
gpio8 at sxipio0: 32 pins
scsibus1 at sdmmc0: 2 targets, initiator 0
sd0 at scsibus1 targ 1 lun 0:  SCSI2 0/direct removable
sd0: 15247MB, 512 bytes/sector, 31225856 sectors
urtwn0 at uhub1 port 1 configuration 1 interface 0 "Realtek 802.11n WLAN 
Adapter" rev 2.00/2.00 addr 2
urtwn0: MAC/BB RTL8192CU, RF 6052 2T2R, address 28:f3:66:41:c9:de
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 

Limits on OBSD amd64

[Friedrich Locke]

Hi folks,

i wonder what is the maximum file system size OBSD supports using different
file systems like FFS, FFS2 and ZFS ?

May you clarify it to me ?

Thanks a lot for your time and cooperation.

Best regards.

Re: bioctl crypto size limitation ?

[Ted Unangst]

myml...@gmx.com wrote:
> Steps to recreate:
> 
> dd if=/dev/random of=/dev/rsd0c bs=1m   (took over a week)
> 
> fdisk -iy -g sd0  (I left off the "-b 960" because this is not a 
> bootable partiton)
> 
> disklabel -E sd0
> 
> Label editor (enter '?' for help at any prompt)
>  > a a
> offset: [64]
> size: [70319603585]
> FS type: [4.2BSD] RAID
>  > w
>  > q
> 
> # bioctl -v -c C -l sd0a softraid0
> New passphrase:
> Re-type passphrase:
> Deriving key using bcrypt PBKDF with 16 rounds...
> bioctl: unknown error


> softraid0: invalid metadata format

You filled the disk with random data, which is not a valid metadata format...

unit test for openiked

[Agoston Toth]

Hello!
Could you please help me out if you have any unit or function test suites for 
openiked?I could not find it in CVS.

Regards, Agoston

Re: Happy birthday Theo!

[Gilles Chehade]

On Thu, May 25, 2017 at 04:20:37PM -0700,  sharon s. wrote:
> At some point.. birthdays stop being happy. only speaking from
> experience.. :)
> 

that reads like an early stage of depression ?

you may want to M-x doctor ;-)

-- 
Gilles Chehade

https://www.poolp.org  @poolpOrg

Re: bioctl crypto size limitation ?

[Florian Ermisch]

Just make slice sd0a smaller
than 100% of the RAID array.

Regards, Florian 

Am 25. Mai 2017 19:03:59 MESZ schrieb myml...@gmx.com:
>I'm wondering if there is a limit to the size of a disk for full disk 
>encryption.
>
>I'm trying to encrypt a 32Tb raid 6 drive on a lsi 9265-8i with 8 x 6Tb
>
>drives and it's failing with the error "unknown error". (very
>descriptive!)
>
>I was able to encrypt the 256Gb system disk without error during 
>installation.
>
>Without encrypting the 32Tb drive, I had no problem creating the FS and
>
>mounting it.
>
>I know people will say this is a bad idea because of fsck (and maybe 
>other reasons), but this drive will be mounted ro 99% of the time.
>
>Steps to recreate:
>
>dd if=/dev/random of=/dev/rsd0c bs=1m   (took over a week)
>
>fdisk -iy -g sd0  (I left off the "-b 960" because this is not a 
>bootable partiton)
>
>disklabel -E sd0
>
>Label editor (enter '?' for help at any prompt)
> > a a
>offset: [64]
>size: [70319603585]
>FS type: [4.2BSD] RAID
> > w
> > q
>
># bioctl -v -c C -l sd0a softraid0
>New passphrase:
>Re-type passphrase:
>Deriving key using bcrypt PBKDF with 16 rounds...
>bioctl: unknown error
>
>
>dmesg:
>
>OpenBSD 6.1-current (GENERIC.MP) #54: Thu May 11 19:20:09 MDT 2017
>dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>real mem = 34333851648 (32743MB)
>avail mem = 33287512064 (31745MB)
>mpath0 at root
>scsibus0 at mpath0: 256 targets
>mainbus0 at root
>bios0 at mainbus0: SMBIOS rev. 2.6 @ 0x9d000 (51 entries)
>bios0: vendor American Megatrends Inc. version "2.1" date 03/17/2012
>bios0: Supermicro X8DT3
>acpi0 at bios0: rev 2
>acpi0: sleep states S0 S1 S4 S5
>acpi0: tables DSDT FACP APIC MCFG SLIT SLIC OEMB SRAT HPET SSDT
>acpi0: wakeup devices NPE1(S4) NPE2(S4) NPE3(S4) NPE4(S4) NPE5(S4) 
>NPE6(S4) NPE7(S4) NPE8(S4) NPE9(S4) NPEA(S4) P0P1(S4) PS2K(S4) USB0(S4)
>
>USB1(S4) USB2(S4) USB5(S4) [...]
>acpitimer0 at acpi0: 3579545 Hz, 24 bits
>acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
>cpu0 at mainbus0: apid 0 (boot processor)
>cpu0: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.32 MHz
>cpu0: 
>FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
>cpu0: 256KB 64b/line 8-way L2 cache
>cpu0: TSC frequency 2400324600 Hz
>cpu0: smt 0, core 0, package 0
>mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
>cpu0: apic clock running at 133MHz
>cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
>cpu1 at mainbus0: apid 2 (application processor)
>cpu1: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.00 MHz
>cpu1: 
>FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
>cpu1: 256KB 64b/line 8-way L2 cache
>cpu1: smt 0, core 1, package 0
>cpu2 at mainbus0: apid 18 (application processor)
>cpu2: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.01 MHz
>cpu2: 
>FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
>cpu2: 256KB 64b/line 8-way L2 cache
>cpu2: smt 0, core 9, package 0
>cpu3 at mainbus0: apid 20 (application processor)
>cpu3: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.00 MHz
>cpu3: 
>FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
>cpu3: 256KB 64b/line 8-way L2 cache
>cpu3: smt 0, core 10, package 0
>cpu4 at mainbus0: apid 32 (application processor)
>cpu4: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.01 MHz
>cpu4: 
>FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
>cpu4: 256KB 64b/line 8-way L2 cache
>cpu4: smt 0, core 0, package 1
>cpu5 at mainbus0: apid 48 (application processor)
>cpu5: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.01 MHz
>cpu5: 
>FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
>cpu5: 256KB 64b/line 8-way L2 cache
>cpu5: smt 0, core 8, package 1
>cpu6 at mainbus0: apid 50 (application processor)
>cpu6: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.01 MHz
>cpu6: