Comment 1 for bug 1733588

This is straightforward to reproduce in a dev SAIO by putting an object to a 4+2 EC policy:

```
swift@vm-15:~/swift$ tail -f /var/log/swift/storage4.error
Nov 9 10:07:38 vm-15 object-server: STDERR: 127.0.0.1 - - [09/Nov/2017 10:07:38] "HEAD /sdb4/30/AUTH_test/c1/LICENSE HTTP/1.1" 404 141 0.000864 (txn: tx82fc8e48cd5a4e848d339-005a0428ea)
Nov 9 10:07:38 vm-15 object-server: STDERR: (23538) accepted ('127.0.0.1', 59694)
Nov 9 10:07:38 vm-15 container-server: STDERR: (23519) accepted ('127.0.0.1', 43880)
Nov 9 10:07:38 vm-15 container-server: STDERR: 127.0.0.1 - - [09/Nov/2017 10:07:38] "PUT /sdb8/509/AUTH_test/c1/LICENSE HTTP/1.1" 201 120 0.000587 (txn: tx20d4a7a566f940d4849cb-005a0428ea)
Nov 9 10:07:38 vm-15 container-server: STDERR: (23519) accepted ('127.0.0.1', 43882)
Nov 9 10:07:38 vm-15 container-server: STDERR: 127.0.0.1 - - [09/Nov/2017 10:07:38] "PUT /sdb4/734/.expiring_objects/1510185559/1510222068-AUTH_test/c1/LICENSE HTTP/1.1" 201 120 0.004376 (txn: tx20d4a7a566f940d4849cb-005a0428ea)
Nov 9 10:07:38 vm-15 object-server: X-Delete-At-Container header must be specified for expiring objects background PUT to work properly. Making best guess as to the container name for now. (txn: tx20d4a7a566f940d4849cb-005a0428ea)
Nov 9 10:07:38 vm-15 object-server: STDERR: 127.0.0.1 - - [09/Nov/2017 10:07:38] "PUT /sdb8/30/AUTH_test/c1/LICENSE HTTP/1.1" 201 181 0.055915 (txn: tx20d4a7a566f940d4849cb-005a0428ea)
Nov 9 10:07:38 vm-15 container-server: STDERR: (23519) accepted ('127.0.0.1', 43894)
Nov 9 10:07:38 vm-15 container-server: STDERR: 127.0.0.1 - - [09/Nov/2017 10:07:38] "PUT /sdb8/509/AUTH_test/c1/LICENSE HTTP/1.1" 201 120 0.001048 (txn: tx20d4a7a566f940d4849cb-005a0428ea)

```