-
Type Version/Name Describe the problem you're observing I created a pool on a new 4TB Seagate drive with two encrypted datasets. One dataset is using zstd compression. I copied test data over to both datasets. I exported the pool. I imported the pool. I checked both datasets for data integrity. dvol/data dataset data is good. dvol/data1 data is missing but referenced and reported used from "zfs get all" command, see below history. Describe how to reproduce the problem I do not have another new disk to test if I can reproduce the issue. Include any warning/errors/backtraces from the system logs I do not see any. History for review Installed openzfs from dkms status created pool with; created two datasets with; and zfs create -o encryption=on -o keylocation=prompt -o keyformat=passphrase dvol/data1 Everything looked good and both datasets showed in the dvol pool. I then copied data into both datasets. I tested export and import and after import dvol/data1 was empty. All data in dvol/data was there and confirmed could open files. zpool status -v
errors: No known data errors zpool history -il dvol zfs get all zfs load-key dvol/data1 I was prompted for passphrase, after entering it went back to prompt no data in dvol/data1 still; zpool get cachefile As seen from "zfs get all" dvol/data1 shows 168GB used; dvol/data1 used 168G - Odd behavior in dataset dvol/data Yet there is 82,340 items, totalling 36.8 GB (38.5 GB on disk) in the dvol/data dataset. All data is accessible. The only difference is the dvol/data dataset is using zstd compression and encryption "aes-256-gcm" and dvol/data1 is using encryption "aes-256-gcm" and no compression. They are using different passphrases. After export/import I created an empty folder in the dvol/data1 dataset and did another export/import. I did not copy any data into it but it does show in dvol/data1 dataset. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
Looks live you should just mount it, for example with |
Beta Was this translation helpful? Give feedback.
-
I had already tried that. As you see in the zfs get all "dvol/data mounted no -" yet I am able to access the data in that folder. As stated I also am able to create a new folder in the dvol/data1 dataset and export/import and that folder is accessible. The original "dvol/data1 used 168G - & dvol/data1 referenced 168G" is not accessible. I created /dvol_data1 I then issued "zfs set mountpoint=/dvol_data1 dvol/data1" no error returned. I then opened the folder browser and nothing is in it. As stated previously I did create a test folder and it showed after doing another export/import of the dvol pool. zfs get all after setting mountpoint Note dvol states mounted yes whereas dvol/data1 still states "dvol/data1 mounted no". I am still able to go to the folder path /dvol/data1 and see the test folder though but nothing shows in /dvol_data1. I was able to reproduce the issue on a new drive. See next message. |
Beta Was this translation helpful? Give feedback.
-
I followed the same steps with a new drive as I did creating the dvol. I just named this fvol. This time after export no data shows in fvol/data or fvol/data1. zfs get all Note fvol pool shows mounted and I do see the data and data1 folder in the fvol pool and folder path. All steps were followed that I used to create dvol creating fvol. zpool status -v
errors: No known data errors pool: fvol
errors: No known data errors zpool history -il fvol |
Beta Was this translation helpful? Give feedback.
-
zfs load-key for both encrypted datasets and then zfs mount -a worked for the fvol pool. The original dvol pool that did not work. What worked was zfs set mountpoint=/new_mountpoint dvol/data1 then zfs load-key dvol/data, zfs load-key dvol/data1 then zfs mount -a. All data originally copied to dvol/data was accessible and all data copied to dvol/data1 was accessible in the new mount point. Thank you gmelikov, greatly appreciated the guidance. |
Beta Was this translation helpful? Give feedback.
zfs load-key for both encrypted datasets and then zfs mount -a worked for the fvol pool. The original dvol pool that did not work. What worked was zfs set mountpoint=/new_mountpoint dvol/data1 then zfs load-key dvol/data, zfs load-key dvol/data1 then zfs mount -a. All data originally copied to dvol/data was accessible and all data copied to dvol/data1 was accessible in the new mount point. Thank you gmelikov, greatly appreciated the guidance.