[Bug 212258] bootpool is not imported after reboot on a MBR partitioned drive

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212258

tsa...@gmail.com changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 212258] bootpool is not imported after reboot on a MBR partitioned drive

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212258

--- Comment #3 from tsa...@gmail.com ---
This is what I get after a clean install using MBR:

# zpool import
   pool: bootpool
 id: 942740621413601929
  state: ONLINE
 action: The pool can be imported using its name or numeric identifier.
 config:

bootpoolONLINE
  ada0s1a   ONLINE

Contents of the loader.conf:
# cat /boot/loader.conf
vfs.root.mountfrom="zfs:zroot/ROOT/default"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
zfs_load="YES"

After importing the bootpool, I did as you mentioned:
# zpool set cachefile=/boot/zfs/zpool.cache zroot
# zpool set cachefile=/boot/zfs/zpool.cache bootpool
# reboot

Same thing, bootpool remains exported after reboot
# zpool list
NAMESIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
zroot  11.9G   280M  11.7G - 1% 2%  1.00x  ONLINE  -

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 211990] iscsi fails to reconnect and does not release devices

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211990

Julien Cigar  changed:

   What|Removed |Added

 CC||jul...@perdition.city

--- Comment #11 from Julien Cigar  ---
I got a similar issue on:

FreeBSD filer1.prod.lan 10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11
18:38:15 UTC 2016
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

with:

root@filer1:/etc/rc.d # sysctl -a|grep -i 'iscsi'
kern.iscsi.fail_on_shutdown: 1
kern.iscsi.fail_on_disconnection: 1
kern.iscsi.maxtags: 255
kern.iscsi.login_timeout: 5
kern.iscsi.iscsid_timeout: 5
kern.iscsi.ping_timeout: 5
kern.iscsi.debug: 1

On the initiator side:

WARNING: 10.20.30.31 (iqn.1994-09.org.freebsd:filer1.prod.lan): no ping reply
(NOP-Out) after 5 seconds; dropping connection
WARNING: 10.20.30.31 (iqn.1994-09.org.freebsd:filer1.prod.lan): connection
error; dropping connection
WARNING: 10.20.30.31 (iqn.1994-09.org.freebsd:filer1.prod.lan): connection
error; dropping connection

On the target side:

WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): no ping reply (NOP-In)
after 5 seconds; reconnecting
WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In)
after 5 seconds; reconnecting
(da3:iscsi2:0:0:0): READ(10). CDB: 28 00 08 03 02 7a 00 00 01 00 
(da3:iscsi2:0:0:0): CAM status: CCB request aborted by the host
(da3:(da2:iscsi1:0:0:0): READ(10). CDB: 28 00 02 d7 49 e7 00 00 20 00 
iscsi2:0:(da2:iscsi1:0:0:0): CAM status: CCB request aborted by the host
0:(da2:0): iscsi1:0:Retrying command
0:0): Retrying command
(da3:iscsi2:0:0:0): READ(10). CDB: 28 00 02 d7 4a e7 00 00 20 00 
(da2:iscsi1:0:0:0): READ(10). CDB: 28 00 02 d7 4a 07 00 00 20 00 
(da3:iscsi2:0:0:0): CAM status: CCB request aborted by the host
(da2:iscsi1:0:0:0): CAM status: CCB request aborted by the host
(da3:(da2:iscsi2:0:iscsi1:0:0:0:0): 0): Retrying command
Retrying command
da3 at iscsi2 bus 0 scbus4 target 0 lun 0
da3:  s/n MYSERIAL   1 detached
da2 at iscsi1 bus 0 scbus3 target 0 lun 0
da2:  s/n MYSERIAL   0 detached
(da3:iscsi2:0:0:0): Periph destroyed
(da2:iscsi1:0:0:0): Periph destroyed
da2 at iscsi2 bus 0 scbus3 target 0 lun 0
da2:  Fixed Direct Access SPC-4 SCSI device
da2: Serial Number MYSERIAL   1
da2: 150.000MB/s transfers
da2: Command Queueing enabled
da2: 1840144MB (471076881 4096 byte sectors)
da3 at iscsi1 bus 0 scbus4 target 0 lun 0
da3:  Fixed Direct Access SPC-4 SCSI device
da3: Serial Number MYSERIAL   0
da3: 150.000MB/s transfers
da3: Command Queueing enabled
da3: 1840144MB (471076881 4096 byte sectors)
WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In)
after 5 seconds; reconnecting
WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): no ping reply (NOP-In)
after 5 seconds; reconnecting
(da3:iscsi1:0:0:0): READ(10). CDB: 28 00 02 d7 4c a7 00 00 20 00 
(da3:iscsi1:0:0:0): CAM status: CCB request aborted by the host
(da2:iscsi2:0:0:0): READ(10). CDB: 28 00 02 e0 f3 d4 00 00 04 00 
(da3:(da2:iscsi2:0:0:0): CAM status: CCB request aborted by the host
iscsi1:0:(da2:0:iscsi2:0:0): 0:Retrying command
0): Retrying command
(da3:iscsi1:0:0:0): READ(10). CDB: 28 00 02 d7 4d 07 00 00 20 00 
(da2:iscsi2:0:0:0): READ(10). CDB: 28 00 02 d7 4b c7 00 00 20 00 
(da3:iscsi1:0:0:0): CAM status: CCB request aborted by the host
(da2:iscsi2:0:0:0): CAM status: CCB request aborted by the host
(da3:(da2:iscsi1:0:iscsi2:0:0:0:0): 0): Retrying command
Retrying command
da3 at iscsi1 bus 0 scbus4 target 0 lun 0
da3:  s/n MYSERIAL   0 detached
da2 at iscsi2 bus 0 scbus3 target 0 lun 0
da2:  s/n MYSERIAL   1 detached
(da2:iscsi2:0:0:0): Periph destroyed
(da3:iscsi1:0:0:0): Periph destroyed
da2 at iscsi1 bus 0 scbus4 target 0 lun 0
da2:  Fixed Direct Access SPC-4 SCSI device
da2: Serial Number MYSERIAL   0
da2: 150.000MB/s transfers
da2: Command Queueing enabled
da2: 1840144MB (471076881 4096 byte sectors)
da3 at iscsi2 bus 0 scbus3 target 0 lun 0
da3:  Fixed Direct Access SPC-4 SCSI device
da3: Serial Number MYSERIAL   1
da3: 150.000MB/s transfers
da3: Command Queueing enabled
da3: 1840144MB (471076881 4096 byte sectors)
WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In)
after 5 seconds; reconnecting
(da2:iscsi1:0:0:0): READ(6). CDB: 08 00 00 00 20 00 
(da2:iscsi1:0:0:0): CAM status: CCB request aborted by the host
(da2:iscsi1:0:0:0): Retrying command
(da2:iscsi1:0:0:0): READ(6). CDB: 08 00 00 10 02 00 
(da2:iscsi1:0:0:0): CAM status: CCB request aborted by the host
(da2:iscsi1:0:0:0): Retrying command
da2 at iscsi1 bus 0 scbus4 target 0 lun 0
da2:  s/n MYSERIAL   0 detached
(da2:iscsi1:0:0:0): Periph destroyed
da2 at iscsi1 bus 0 scbus4 target 0 lun 0
da2:  Fixed Direct Access SPC-4 SCSI device
da2: Serial Number MYSERIAL   0
da2: 150.000MB/s transfers
da2: Command Queueing enabled
da2: 1840144MB (471076881 4096 byte sectors)
WARNING: 10.20.30

[Bug 213371] panic: spin lock held too long

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #30 from Wojciech Giel  ---
show active trace gives: "No such command"

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 211990] iscsi fails to reconnect and does not release devices

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211990

--- Comment #12 from Julien Cigar  ---
Some more info:

on filer2:

root@filer2:/home/jcigar # cat /etc/ctl.conf 

auth-group ag0 {
chap xxx xxx
}

portal-group pg0 {
discovery-auth-group no-authentication
listen 10.20.30.32
}

target iqn.2016-08.lan.prod:target0 {
auth-group ag0
portal-group pg0

lun 0 {
blocksize 4096
path /dev/gpt/f2data0
}
}

target iqn.2016-08.lan.prod:target1 {
auth-group ag0
portal-group pg0

lun 0 {
blocksize 4096
path /dev/gpt/f2data1
}
}

root@filer2:/home/jcigar # ifconfig bge1
bge1: flags=8843 metric 0 mtu 9000
   
options=c019b
ether d0:bf:9c:3a:b7:25
inet 10.20.30.32 netmask 0xff00 broadcast 10.20.30.255 
nd6 options=29
media: Ethernet autoselect (1000baseT )
status: active

root@filer2:/home/jcigar # pciconf -lv bge1
bge1@pci0:2:0:1:class=0x02 card=0x22e8103c chip=0x165f14e4 rev=0x00
hdr=0x00
vendor = 'Broadcom Corporation'
device = 'NetXtreme BCM5720 Gigabit Ethernet PCIe'
class  = network
subclass   = ethernet

root@filer2:/home/jcigar # grep 'bge1' /var/run/dmesg.boot 
bge1:  mem
0x92b0-0x92b0,0x92b1-0x92b1,0x92b2-0x92b2 at device 0.1
on pci2
bge1: APE FW version: NCSI v1.3.12.0
bge1: CHIP ID 0x0572; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus1:  on bge1
bge1: Using defaults for TSO: 65518/35/2048
bge1: Ethernet address: d0:bf:9c:3a:b7:25
bge1: link state changed to DOWN
bge1: link state changed to UP

on filer1.prod.lan:

root@filer1:/home/jcigar # cat /etc/iscsi.conf 

t0 {
TargetAddress   = 10.20.30.32
TargetName  = iqn.2016-08.lan.prod:target0
AuthMethod  = CHAP
chapIName   = xxx
chapSecret  = xxx
}

t1 {
TargetAddress   = 10.20.30.32
TargetName  = iqn.2016-08.lan.prod:target1
AuthMethod  = CHAP
chapIName   = xxx
chapSecret  = xxx
}

root@filer1:/home/jcigar # ifconfig bge1
bge1: flags=8843 metric 0 mtu 9000
   
options=c019b
ether d0:bf:9c:3a:c6:e1
inet 10.20.30.31 netmask 0xff00 broadcast 10.20.30.255 
nd6 options=29
media: Ethernet autoselect (1000baseT )
status: active

root@filer1:/home/jcigar # pciconf -lv bge1
bge1@pci0:2:0:1:class=0x02 card=0x22e8103c chip=0x165f14e4 rev=0x00
hdr=0x00
vendor = 'Broadcom Corporation'
device = 'NetXtreme BCM5720 Gigabit Ethernet PCIe'
class  = network
subclass   = ethernet

root@filer1:/home/jcigar # grep 'bge1' /var/run/dmesg.boot 
bge1:  mem
0x92b0-0x92b0,0x92b1-0x92b1,0x92b2-0x92b2 at device 0.1
on pci2
bge1: APE FW version: NCSI v1.3.12.0
bge1: CHIP ID 0x0572; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus1:  on bge1
bge1: Using defaults for TSO: 65518/35/2048
bge1: Ethernet address: d0:bf:9c:3a:c6:e1
bge1: link state changed to DOWN
bge1: link state changed to UP

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 212875] [patch] add -d (domain) flag to hostname

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212875

Ben RUBSON  changed:

   What|Removed |Added

 Attachment #175028|0   |1
is obsolete||

--- Comment #2 from Ben RUBSON  ---
Created attachment 175863
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175863&action=edit
patch to add -d flag to hostname

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 212875] [patch] add -d (domain) flag to hostname

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212875

--- Comment #3 from Ben RUBSON  ---
I've just modified the patch according to your last comment Kurt.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 212875] [patch] add -d (domain) flag to hostname

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212875

Ben RUBSON  changed:

   What|Removed |Added

 Attachment #175863|0   |1
is obsolete||

--- Comment #4 from Ben RUBSON  ---
Created attachment 175866
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175866&action=edit
patch to add -d flag to hostname

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 212258] bootpool is not imported after reboot on a MBR partitioned drive

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212258

--- Comment #4 from Petr Fischer  ---
I also checked zpool.cache by:

zdb -CU /boot/zfs/zpool.cache

Everything OK, correct devices inside cache file, bootpool still exported after
reboot.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 213572] Support for Setting base system build options via dialog

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213572

Bug ID: 213572
   Summary: Support for Setting base system build options via
dialog
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: conf
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: roberf...@gmail.com

Created attachment 175870
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175870&action=edit
Compressed patches for the config targets

As described on the Ideas Page
(https://wiki.freebsd.org/IdeasPage#Support_for_setting_base_system_build_options_via_dialog.281.29)
and as it is specified on the article "Contributing to FreeBSD", I send my
proposal for the configuration of the build using dialog.

The short description for the options (stored on tools/build/options/shortdesc)
must be reviewed to improve them.

The new functionalities include the config and rmconfig targets.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 208554] usr.bin/sed :sed functions 'i' and 'a' discard leading white space

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208554

Pedro F. Giffuni  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2134
   ||74

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 213474] sed behaviuor with a/i/c operands.

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474

Pedro F. Giffuni  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2085
   ||54
 CC||p...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 213474] sed behavior change with a/i/c operands.

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474

Pedro F. Giffuni  changed:

   What|Removed |Added

Summary|sed behaviuor with a/i/c|sed behavior change with
   |operands.   |a/i/c operands.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 213474] sed behaviuor with a/i/c operands.

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474

--- Comment #1 from Pedro F. Giffuni  ---
I am not sure this can be classified as a regression.

It is certainly a change in behavior with the idea of being more compatible
with GNU sed: some people may be moving from linux to FreeBSD and may
appreciate the compatibility.

Standards don't force either behavior though, and I do see it would be somewhat
advantageous to do some things different than GNU sed, but I am completely
agnostic here.

If we revert to the previous behavior I would prefer it be done fast but OTOH,
the damage is already done for 11.0.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 213462] Retry_count in minidump code delaying ENOSPC by around 30 minutes for live cores.

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213462

--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:

Author: stevek
Date: Mon Oct 17 22:57:41 UTC 2016
New revision: 307540
URL: https://svnweb.freebsd.org/changeset/base/307540

Log:
  Add sysctl to make amd64 minidump retry count tunable at runtime.

  PR:   213462
  Submitted by: RaviPrakash Darbha 
  Reviewed by:  cemi, markj
  Approved by:  sjg (mentor)
  Obtained from:Juniper Networks
  Differential Revision:https://reviews.freebsd.org/D8254

Changes:
  head/sys/amd64/amd64/minidump_machdep.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 213474] sed behavior change with a/i/c operands.

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474

--- Comment #2 from Pedro F. Giffuni  ---
Created attachment 175892
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175892&action=edit
Proof-of-concept: provide a compile-time flag for GNU compatibility

An idea that could use polishing is to re-use the WITHOUT_GNU_SUPPORT to decide
whether sed should attempt to behave in a GNU compatible way or not.

I am leaning towards defaulting to the previous behavior: as Sergey states,
people can always install GNU sed if the want.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 213584] tar's 'g' substitution flag is broken

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213584

Bug ID: 213584
   Summary: tar's 'g' substitution flag is broken
   Product: Base System
   Version: 10.3-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: d...@freebsd.org

When extracting a zip archive it may be required to replace the '\' with '/'. 
To achieve this the following command is used:

# tar -s'|\\|/|g' -xf /path/to/zip

however the substitution only applies to the first occurance per file.  This
has been confirmed to happen on FreeBSD < 11.  

See Port's commit 424052 for further details.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 213572] Support for Setting base system build options via dialog

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213572

Mark Linimon  changed:

   What|Removed |Added

   Keywords||feature, patch
 CC||b...@freebsd.org,
   ||bdrew...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"