Adding a volume remounts existing volumes???

Status
Not open for further replies.

David E

Contributor
Joined
Nov 1, 2013
Messages
119
I needed to move some data to another filer, so I plugged in a USB disk (da8) and created a new volume using just the new disk. It took a really long time so I checked dmesg and /var/log/messages and saw:

Code:
da8 at umass-sim0 bus 0 scbus8 target 0 lun 0
da8: <ASMT 2105 0> Fixed Direct Access SCSI-6 device
da8: Serial Number 00000000000000000000
da8: 40.000MB/s transfers
da8: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da8: quirks=0x2<NO_6_BYTE>
GEOM_ELI: Device da0p1.eli destroyed.
GEOM_ELI: Detached da0p1.eli on last close.
GEOM_ELI: Device da1p1.eli destroyed.
GEOM_ELI: Detached da1p1.eli on last close.
GEOM_ELI: Device da3p1.eli destroyed.
GEOM_ELI: Detached da3p1.eli on last close.
GEOM_ELI: Device da4p1.eli destroyed.
GEOM_ELI: Detached da4p1.eli on last close.
GEOM_ELI: Device da5p1.eli destroyed.
GEOM_ELI: Detached da5p1.eli on last close.
GEOM_ELI: Device da6p1.eli destroyed.
GEOM_ELI: Detached da6p1.eli on last close.
GEOM_ELI: Device da0p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware
GEOM_ELI: Device da1p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware
GEOM_ELI: Device da3p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware
GEOM_ELI: Device da4p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware
GEOM_ELI: Device da5p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware
GEOM_ELI: Device da6p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware
GEOM_ELI: Device da8p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware


It looks like it actually unmounted and remounted my existing mount - putting all my VMs and software that depends on the availability of that mount at risk, is this the case?? And if so, why in the world would it do that?

Secondly, can I just create the mount manually from the command line to avoid this web-based behavior?

Thirdly, ultimately I will need to unmount and move this, is there a way to do that safely without causing similar behavior to above? Can I just "zfs unmount XXX" from the command line, or will that cause other issues? Really wasn't expecting something so simple to have potentially major ramifications on production...
 

m0nkey_

MVP
Joined
Oct 27, 2015
Messages
2,739
No, it's not re-mounting the drives. I believe this is normal GELI behavior, because you added another drive while on-line .
 
Status
Not open for further replies.
Top