suspend/resume versus OpenZFS on USB

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

suspend/resume versus OpenZFS on USB

grahamperrin
This week for the first time I toyed with OpenZFS on a USB device: a
mobile hard disk drive connected to the dock of an HP EliteBook 8570p.

A light test, with the pool imported but not writing to the dataset at
suspend time.

At resume time (22:31), the device was still physically connected but
the pool suffered an I/O failure (and the keyboard and trackball on USB
were unusable).

Sep  3 22:31:03 momh167-gjp4-8570p ZFS[11239]: vdev state changed,
pool_guid=$8076233369858608335 vdev_guid=$13893535540375859253
Sep  3 22:31:03 momh167-gjp4-8570p ZFS[11243]: pool I/O failure,
zpool=$Transcend error=$28
Sep  3 22:31:03 momh167-gjp4-8570p ZFS[11247]: pool I/O failure,
zpool=$Transcend error=$28
Sep  3 22:31:03 momh167-gjp4-8570p ZFS[11251]: pool I/O failure,
zpool=$Transcend error=$28
Sep  3 22:31:03 momh167-gjp4-8570p ZFS[11255]: pool I/O failure,
zpool=$Transcend error=$28
Sep  3 22:31:03 momh167-gjp4-8570p ZFS[11259]: catastrophic pool I/O
failure, zpool=$Transcend

I cleared pool errors (after which the keyboard and trackball became
usable), exported the pool, physically disconnected the drive, restarted
the OS, reconnected, imported and – luckily – cleared the remaining
metadata errors through a scrub.

Please, might something be done to improve suspend/resume reliability
with storage on USB?

Might I/O failures be less likely if I connect the drive to the notebook
instead of its dock?

TIA

----

More from /var/log/messages at https://pastebin.com/CqRYbFZm

Other relevant info below.

root@momh167-gjp4-8570p:~ # date ; uptime ; uname -v
Thu Sep  3 22:45:07 BST 2020
10:45PM  up 6 mins, 6 users, load averages: 0.20, 0.27, 0.13
FreeBSD 13.0-CURRENT #63 r364768: Tue Aug 25 20:08:23 BST 2020
root@momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
root@momh167-gjp4-8570p:~ # zpool status -v
   pool: copperbowl
  state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
         still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
         the pool may no longer be accessible by software that does not
support
         the features. See zpool-features(5) for details.
   scan: scrub repaired 0B in 01:39:31 with 0 errors on Thu Sep  3
01:12:21 2020
config:

         NAME          STATE     READ WRITE CKSUM
         copperbowl    ONLINE       0     0     0
           ada0p4.eli  ONLINE       0     0     0

errors: No known data errors
root@momh167-gjp4-8570p:~ # zpool import Transcend && zfs load-key
Transcend/VirtualBox
Enter passphrase for 'Transcend/VirtualBox':
root@momh167-gjp4-8570p:~ # zpool status -v Transcend
   pool: Transcend
  state: ONLINE
status: One or more devices has experienced an error resulting in data
         corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
         entire pool from backup.
    see: https://zfsonlinux.org/msg/ZFS-8000-8A
   scan: scrub repaired 0B in 00:15:33 with 0 errors on Wed Sep  2
22:38:56 2020
config:

         NAME        STATE     READ WRITE CKSUM
         Transcend   ONLINE       0     0     0
           da0p1     ONLINE       0     0     0

errors: Permanent errors have been detected in the following files:

         <metadata>:<0x0>
         <metadata>:<0x3d>
root@momh167-gjp4-8570p:~ # zpool scrub Transcend
root@momh167-gjp4-8570p:~ # zfs version
zfs-0.8.0-1
zfs-kmod-0.8.0-1
root@momh167-gjp4-8570p:~ # zpool status -v Transcend
   pool: Transcend
  state: ONLINE
   scan: scrub repaired 0B in 00:17:53 with 0 errors on Thu Sep  3
23:03:57 2020
config:

         NAME        STATE     READ WRITE CKSUM
         Transcend   ONLINE       0     0     0
           da0p1     ONLINE       0     0     0

errors: No known data errors
root@momh167-gjp4-8570p:~ # zfs get
compression,compressratio,encryption,used,referenced,mountpoint
Transcend Transcend/VirtualBox
NAME                  PROPERTY       VALUE SOURCE
Transcend             compression    zstd                      local
Transcend             compressratio  1.70x                     -
Transcend             encryption     off default
Transcend             used           76.4G                     -
Transcend             referenced     76.4G                     -
Transcend             mountpoint     /Volumes/t500             local
Transcend/VirtualBox  compression    zstd inherited from Transcend
Transcend/VirtualBox  compressratio  1.00x                     -
Transcend/VirtualBox  encryption     aes-256-gcm               -
Transcend/VirtualBox  used           200K                      -
Transcend/VirtualBox  referenced     200K                      -
Transcend/VirtualBox  mountpoint     /Volumes/t500/VirtualBox inherited
from Transcend
root@momh167-gjp4-8570p:~ # ls -hl
/Volumes/t500/VirtualBox/Windows/Windows.vdi
-rw-------  1 grahamperrin  grahamperrin    69G Sep  3 16:58
/Volumes/t500/VirtualBox/Windows/Windows.vdi
root@momh167-gjp4-8570p:~ # du -hs
/Volumes/t500/VirtualBox/Windows/Windows.vdi
  36G    /Volumes/t500/VirtualBox/Windows/Windows.vdi
root@momh167-gjp4-8570p:~ #

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: suspend/resume versus OpenZFS on USB

Hans Petter Selasky-6
On 2020-09-04 01:42, Graham Perrin wrote:

> This week for the first time I toyed with OpenZFS on a USB device: a
> mobile hard disk drive connected to the dock of an HP EliteBook 8570p.
>
> A light test, with the pool imported but not writing to the dataset at
> suspend time.
>
> At resume time (22:31), the device was still physically connected but
> the pool suffered an I/O failure (and the keyboard and trackball on USB
> were unusable).
>
> Sep  3 22:31:03 momh167-gjp4-8570p ZFS[11239]: vdev state changed,
> pool_guid=$8076233369858608335 vdev_guid=$13893535540375859253
> Sep  3 22:31:03 momh167-gjp4-8570p ZFS[11243]: pool I/O failure,
> zpool=$Transcend error=$28
> Sep  3 22:31:03 momh167-gjp4-8570p ZFS[11247]: pool I/O failure,
> zpool=$Transcend error=$28
> Sep  3 22:31:03 momh167-gjp4-8570p ZFS[11251]: pool I/O failure,
> zpool=$Transcend error=$28
> Sep  3 22:31:03 momh167-gjp4-8570p ZFS[11255]: pool I/O failure,
> zpool=$Transcend error=$28
> Sep  3 22:31:03 momh167-gjp4-8570p ZFS[11259]: catastrophic pool I/O
> failure, zpool=$Transcend
>
> I cleared pool errors (after which the keyboard and trackball became
> usable), exported the pool, physically disconnected the drive, restarted
> the OS, reconnected, imported and – luckily – cleared the remaining
> metadata errors through a scrub.
>
> Please, might something be done to improve suspend/resume reliability
> with storage on USB?
>
> Might I/O failures be less likely if I connect the drive to the notebook
> instead of its dock?
>
> TIA
>
> ----
>
> More from /var/log/messages at https://pastebin.com/CqRYbFZm
>
> Other relevant info below.
>
> root@momh167-gjp4-8570p:~ # date ; uptime ; uname -v
> Thu Sep  3 22:45:07 BST 2020
> 10:45PM  up 6 mins, 6 users, load averages: 0.20, 0.27, 0.13
> FreeBSD 13.0-CURRENT #63 r364768: Tue Aug 25 20:08:23 BST 2020
> root@momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
> root@momh167-gjp4-8570p:~ # zpool status -v
>    pool: copperbowl
>   state: ONLINE
> status: Some supported features are not enabled on the pool. The pool can
>          still be used, but some features are unavailable.
> action: Enable all features using 'zpool upgrade'. Once this is done,
>          the pool may no longer be accessible by software that does not
> support
>          the features. See zpool-features(5) for details.
>    scan: scrub repaired 0B in 01:39:31 with 0 errors on Thu Sep  3
> 01:12:21 2020
> config:
>
>          NAME          STATE     READ WRITE CKSUM
>          copperbowl    ONLINE       0     0     0
>            ada0p4.eli  ONLINE       0     0     0
>
> errors: No known data errors
> root@momh167-gjp4-8570p:~ # zpool import Transcend && zfs load-key
> Transcend/VirtualBox
> Enter passphrase for 'Transcend/VirtualBox':
> root@momh167-gjp4-8570p:~ # zpool status -v Transcend
>    pool: Transcend
>   state: ONLINE
> status: One or more devices has experienced an error resulting in data
>          corruption.  Applications may be affected.
> action: Restore the file in question if possible.  Otherwise restore the
>          entire pool from backup.
>     see: https://zfsonlinux.org/msg/ZFS-8000-8A
>    scan: scrub repaired 0B in 00:15:33 with 0 errors on Wed Sep  2
> 22:38:56 2020
> config:
>
>          NAME        STATE     READ WRITE CKSUM
>          Transcend   ONLINE       0     0     0
>            da0p1     ONLINE       0     0     0
>
> errors: Permanent errors have been detected in the following files:
>
>          <metadata>:<0x0>
>          <metadata>:<0x3d>
> root@momh167-gjp4-8570p:~ # zpool scrub Transcend
> root@momh167-gjp4-8570p:~ # zfs version
> zfs-0.8.0-1
> zfs-kmod-0.8.0-1
> root@momh167-gjp4-8570p:~ # zpool status -v Transcend
>    pool: Transcend
>   state: ONLINE
>    scan: scrub repaired 0B in 00:17:53 with 0 errors on Thu Sep  3
> 23:03:57 2020
> config:
>
>          NAME        STATE     READ WRITE CKSUM
>          Transcend   ONLINE       0     0     0
>            da0p1     ONLINE       0     0     0
>
> errors: No known data errors
> root@momh167-gjp4-8570p:~ # zfs get
> compression,compressratio,encryption,used,referenced,mountpoint
> Transcend Transcend/VirtualBox
> NAME                  PROPERTY       VALUE SOURCE
> Transcend             compression    zstd                      local
> Transcend             compressratio  1.70x                     -
> Transcend             encryption     off default
> Transcend             used           76.4G                     -
> Transcend             referenced     76.4G                     -
> Transcend             mountpoint     /Volumes/t500             local
> Transcend/VirtualBox  compression    zstd inherited from Transcend
> Transcend/VirtualBox  compressratio  1.00x                     -
> Transcend/VirtualBox  encryption     aes-256-gcm               -
> Transcend/VirtualBox  used           200K                      -
> Transcend/VirtualBox  referenced     200K                      -
> Transcend/VirtualBox  mountpoint     /Volumes/t500/VirtualBox inherited
> from Transcend
> root@momh167-gjp4-8570p:~ # ls -hl
> /Volumes/t500/VirtualBox/Windows/Windows.vdi
> -rw-------  1 grahamperrin  grahamperrin    69G Sep  3 16:58
> /Volumes/t500/VirtualBox/Windows/Windows.vdi
> root@momh167-gjp4-8570p:~ # du -hs
> /Volumes/t500/VirtualBox/Windows/Windows.vdi
>   36G    /Volumes/t500/VirtualBox/Windows/Windows.vdi
> root@momh167-gjp4-8570p:~ #
>

We need output from "procstat -akk" to see where ZFS/USB is hanging.

--HPS

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: suspend/resume versus OpenZFS on USB

grahamperrin
On 04/09/2020 09:01, Hans Petter Selasky wrote:

> On 2020-09-04 01:42, Graham Perrin wrote:
>> This week for the first time I toyed with OpenZFS on a USB device: a
>> mobile hard disk drive connected to the dock of an HP EliteBook 8570p.
>>
>> A light test, with the pool imported but not writing to the dataset
>> at suspend time.
>>
>> At resume time (22:31), the device was still physically connected but
>> the pool suffered an I/O failure (and the keyboard and trackball on
>> USB were unusable).

> We need output from "procstat -akk" to see where ZFS/USB is hanging.
>
> --HPS

For test purposes I reproduced the behaviour with a different device, a
USB flash drive (connected to the same dock).

Attached:

2020-09-05 09:27:55 procstat -akk.txt

– output from procstat -akk

2020-09-05 09:17:59 suspend 09:26:49 resume.txt

– the output in context.

Thank you

Graham


_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

2020-09-05 09:27:55 procstat -akk.txt (268K) Download Attachment
2020-09-05 09:17:59 suspend 09:26:49 resume.txt (331K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: suspend/resume versus OpenZFS on USB

Hans Petter Selasky-6
On 2020-09-05 11:00, Graham Perrin wrote:

> On 04/09/2020 09:01, Hans Petter Selasky wrote:
>> On 2020-09-04 01:42, Graham Perrin wrote:
>>> This week for the first time I toyed with OpenZFS on a USB device: a
>>> mobile hard disk drive connected to the dock of an HP EliteBook 8570p.
>>>
>>> A light test, with the pool imported but not writing to the dataset
>>> at suspend time.
>>>
>>> At resume time (22:31), the device was still physically connected but
>>> the pool suffered an I/O failure (and the keyboard and trackball on
>>> USB were unusable).
> …
>> We need output from "procstat -akk" to see where ZFS/USB is hanging.
>>
>> --HPS
>
> For test purposes I reproduced the behaviour with a different device, a
> USB flash drive (connected to the same dock).
>
> Attached:
>
> 2020-09-05 09:27:55 procstat -akk.txt
>
> – output from procstat -akk
>
> 2020-09-05 09:17:59 suspend 09:26:49 resume.txt
>
> – the output in context.
>
> Thank you
>
> Graham
>
>

Hi,

USB is not hanging.

It looks like a problem with USB resume, that no devices are recognized,
until you re-plug them ...

--HPS
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: suspend/resume versus OpenZFS on USB

grahamperrin
On 05/09/2020 10:26, Hans Petter Selasky wrote:

> On 2020-09-05 11:00, Graham Perrin wrote:
>> On 04/09/2020 09:01, Hans Petter Selasky wrote:
>>> On 2020-09-04 01:42, Graham Perrin wrote:
>>>> This week for the first time I toyed with OpenZFS on a USB device:
>>>> a mobile hard disk drive connected to the dock of an HP EliteBook
>>>> 8570p.
>>>>
>>>> A light test, with the pool imported but not writing to the dataset
>>>> at suspend time.
>>>>
>>>> At resume time (22:31), the device was still physically connected
>>>> but the pool suffered an I/O failure (and the keyboard and
>>>> trackball on USB were unusable).
>> …
>>> We need output from "procstat -akk" to see where ZFS/USB is hanging.
>>>
>>> --HPS
>>
>> For test purposes I reproduced the behaviour with a different device,
>> a USB flash drive (connected to the same dock).
>>
>> Attached:
>>
>> 2020-09-05 09:27:55 procstat -akk.txt
>>
>> – output from procstat -akk
>>
>> 2020-09-05 09:17:59 suspend 09:26:49 resume.txt
>>
>> – the output in context.
>>
>> Thank you
>>
>> Graham
>>
>>
>
> Hi,
>
> USB is not hanging.
>
> It looks like a problem with USB resume, that no devices are
> recognized, until you re-plug them ...
>
> --HPS

Hi

If I export the pool before suspend, no problem at resume time.

An alternative scenario, with the notebook removed from its dock. With
nothing other than the USB device connected (at da0), if the pool is
imported and online at suspend time, then at resume time:

* the pool is SUSPENDED
* da0p1 is shown as REMOVED
* zpool clear followed by zpool scrub will lead to disappearance of the
permanent errors, without physically touching the USB flash drive,
however the resulting device is at da1.

Example below.

----

root@momh167-gjp4-8570p:~ # zpool status -v usb
   pool: usb
  state: ONLINE
   scan: scrub repaired 0B in 00:00:04 with 0 errors on Sat Sep  5
18:00:31 2020
config:

         NAME        STATE     READ WRITE CKSUM
         usb         ONLINE       0     0     0
           da0p1     ONLINE       0     0     0

errors: No known data errors
root@momh167-gjp4-8570p:~ # acpiconf -s 3
root@momh167-gjp4-8570p:~ # zpool status -v usb
   pool: usb
  state: SUSPENDED
status: One or more devices are faulted in response to IO failures.
action: Make sure the affected devices are connected, then run 'zpool
clear'.
    see: https://zfsonlinux.org/msg/ZFS-8000-HC
   scan: scrub repaired 0B in 00:00:04 with 0 errors on Sat Sep  5
18:00:31 2020
config:

         NAME        STATE     READ WRITE CKSUM
         usb         UNAVAIL      0     0     0  insufficient replicas
           da0p1     REMOVED      0     0     0

errors: List of errors unavailable: pool I/O is currently suspended
root@momh167-gjp4-8570p:~ # zpool clear usb
root@momh167-gjp4-8570p:~ # zpool status -v usb
   pool: usb
  state: ONLINE
status: One or more devices has experienced an error resulting in data
         corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
         entire pool from backup.
    see: https://zfsonlinux.org/msg/ZFS-8000-8A
   scan: scrub repaired 0B in 00:00:04 with 0 errors on Sat Sep  5
18:00:31 2020
config:

         NAME        STATE     READ WRITE CKSUM
         usb         ONLINE       0     0     0
           da1p1     ONLINE       0     0     0

errors: Permanent errors have been detected in the following files:

         <metadata>:<0x0>
         <metadata>:<0x3d>
root@momh167-gjp4-8570p:~ # zpool scrub usb
root@momh167-gjp4-8570p:~ # zpool status -v usb
   pool: usb
  state: ONLINE
   scan: scrub repaired 0B in 00:00:01 with 0 errors on Sat Sep  5
18:04:05 2020
config:

         NAME        STATE     READ WRITE CKSUM
         usb         ONLINE       0     0     0
           da1p1     ONLINE       0     0     0

errors: No known data errors
root@momh167-gjp4-8570p:~ # ls /dev/da*
/dev/da0        /dev/da0p1      /dev/da1        /dev/da1p1
root@momh167-gjp4-8570p:~ #

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: suspend/resume versus OpenZFS on USB

grahamperrin
I'm not sure what was going on with device numbers in my previous
report, but this much seems to be easily and consistently reproducible.

If the pool is ONLINE and imported at suspend time – and if not actively
writing to the device at suspend time – then at resume time:

* the pool is SUSPENDED
* the device is shown as REMOVED
* zpool clear followed by zpool scrub lead to disappearance of permanent
metadata errors, without physically touching the device.

----

root@momh167-gjp4-8570p:~ # ls /dev/da*
/dev/da0        /dev/da0p1      /dev/da1        /dev/da1p1
root@momh167-gjp4-8570p:~ # zpool status usb
   pool: usb
  state: ONLINE
   scan: scrub repaired 0B in 00:00:08 with 0 errors on Sat Sep 12
02:55:26 2020
config:

         NAME        STATE     READ WRITE CKSUM
         usb         ONLINE       0     0     0
           da0p1     ONLINE       0     0     0

errors: No known data errors
root@momh167-gjp4-8570p:~ # date ; uname -v ; zfs version ; acpiconf -s3
Sat Sep 12 02:59:20 BST 2020
FreeBSD 13.0-CURRENT #64 r365364: Sun Sep  6 01:38:18 BST 2020
root@momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
zfs-0.8.0-1
zfs-kmod-0.8.0-1
root@momh167-gjp4-8570p:~ # zpool status -v
   pool: copperbowl
  state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
         still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
         the pool may no longer be accessible by software that does not
support
         the features. See zpool-features(5) for details.
   scan: scrub repaired 0B in 01:39:31 with 0 errors on Thu Sep  3
01:12:21 2020
config:

         NAME          STATE     READ WRITE CKSUM
         copperbowl    ONLINE       0     0     0
           ada0p4.eli  ONLINE       0     0     0

errors: No known data errors

   pool: usb
  state: SUSPENDED
status: One or more devices are faulted in response to IO failures.
action: Make sure the affected devices are connected, then run 'zpool
clear'.
    see: https://zfsonlinux.org/msg/ZFS-8000-HC
   scan: scrub repaired 0B in 00:00:08 with 0 errors on Sat Sep 12
02:55:26 2020
config:

         NAME        STATE     READ WRITE CKSUM
         usb         UNAVAIL      0     0     0  insufficient replicas
           da0p1     REMOVED      0     0     0

errors: List of errors unavailable: pool I/O is currently suspended
root@momh167-gjp4-8570p:~ # zpool clear usb && zpool scrub usb
root@momh167-gjp4-8570p:~ # date ; zpool status usb
Sat Sep 12 03:00:19 BST 2020
   pool: usb
  state: ONLINE
   scan: scrub repaired 0B in 00:00:01 with 0 errors on Sat Sep 12
03:00:11 2020
config:

         NAME        STATE     READ WRITE CKSUM
         usb         ONLINE       0     0     0
           da0p1     ONLINE       0     0     0

errors: No known data errors
root@momh167-gjp4-8570p:~ #

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: suspend/resume versus OpenZFS on USB

grahamperrin
On 12/09/2020 03:09, Graham Perrin wrote:
> … If the pool is ONLINE and imported at suspend time – and if not
> actively writing to the device at suspend time …

Testing more aggressively (still with a low spec USB flash drive),
attempting to suspend _immediately after_ writes to the file system.

Second test:

----

root@momh167-gjp4-8570p:~ # date ; uptime ; uname -v ; zfs version
Sat Sep 12 04:13:07 BST 2020
  4:13AM  up 8 mins, 5 users, load averages: 0.95, 0.60, 0.30
FreeBSD 13.0-CURRENT #64 r365364: Sun Sep  6 01:38:18 BST 2020
root@momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
zfs-0.8.0-1
zfs-kmod-0.8.0-1
root@momh167-gjp4-8570p:~ # zpool status usb ; zfs get mountpoint usb
   pool: usb
  state: ONLINE
   scan: scrub repaired 0B in 00:00:01 with 0 errors on Sat Sep 12
03:20:51 2020
config:

         NAME        STATE     READ WRITE CKSUM
         usb         ONLINE       0     0     0
           da0p1     ONLINE       0     0     0

errors: No known data errors
NAME  PROPERTY    VALUE         SOURCE
usb   mountpoint  /Volumes/usb  local
root@momh167-gjp4-8570p:~ # du -hs
/usr/home/grahamperrin/Videos/palmtree.mp4
  68M    /usr/home/grahamperrin/Videos/palmtree.mp4
root@momh167-gjp4-8570p:~ # gdd status=progress bs=1M
if="/usr/home/grahamperrin/Videos/palmtree.mp4"
of="/Volumes/usb/palmtree.mp4" ; date ; acpiconf -s3

----

In both tests: suspend failed, it was necessary to force off the computer.

Photographs of the second test:
<https://photos.app.goo.gl/5WRVrCRioCEwnmUg6>


_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"