Bug 196136 - gbde and "zpool create" -> locks up the computer
Summary: gbde and "zpool create" -> locks up the computer
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: CURRENT
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-19 17:09 UTC by david
Modified: 2014-12-19 20:50 UTC (History)
0 users

See Also:


Attachments
picture of the error (143.11 KB, image/jpeg)
2014-12-19 20:43 UTC, david
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description david 2014-12-19 17:09:23 UTC
i'm trying to encrypt my external hard drive and am following the guide at https://www.freebsd.org/doc/handbook/disks-encrypting.html

with UFS, i have no problems creating the filesystem. all works as expected.
however, i wanted to use ZFS instead: when i type "zpool create backup /dev/da0p1.bde" the CPU usage goes through the roof (system CPU according to top), and eventually the whole computer becomes unresponsive and locks up. i've tried it multiple times with the same results. 

# gpart show da0
=>        40  7814037088  da0  GPT  (3.6T)
          40  7814037080    1  freebsd-zfs  (3.6T)
  7814037120           8       - free -  (4.0K)

# dmesg | grep da0
da0 at umass-sim0 bus 0 scbus9 target 0 lun 0
da0: <TOSHIBA MD04ACA400 0> Fixed Direct Access SCSI-6 device 
da0: Serial Number         X4RGK50ZFSBA
da0: 40.000MB/s transfers
da0: 3815447MB (7814037168 512 byte sectors: 255H 63S/T 486401C)
da0: quirks=0x2<NO_6_BYTE>
Comment 1 david 2014-12-19 20:43:16 UTC
Created attachment 150790 [details]
picture of the error

so i'm currently using UFS. i had to restart the PC, however i received the following error message (see the attached picture).
Comment 2 david 2014-12-19 20:50:27 UTC
(In reply to david from comment #1)
> Created attachment 150790 [details]
> picture of the error
> 
> so i'm currently using UFS. i had to restart the PC, however i received the
> following error message (see the attached picture).

but that seems to be my mistake. i hadn't done a "gdbe detach /dev/da0" :)