sabertooth

Members
  • Posts

    39
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

sabertooth's Achievements

Rookie

Rookie (2/14)

3

Reputation

  1. Afraid it indeed was a zfs dataset since all my shares were on zfs in 6.11.5. Please remember that the share initially was created with Primary Storage set to Array containing a link to dataset with same name as the share. After migration, I did change the Primary Storage to zpool which probably explains the yellow warning symbol next to it. I suggest you try out the above listed steps.
  2. I am no longer seeing this with 6.12.4
  3. Please refer to attached screen-shot, clearly shows dummy_old share as non-exclusive and dummy as exclusive (on zdata) All steps are listed below: root@UnraidZFS:/mnt/user# mv dummy_old/* dummy/. root@UnraidZFS:/mnt/user# rm -rf dummy_old/ root@UnraidZFS:/mnt/user# zfs list NAME USED AVAIL REFER MOUNTPOINT zdata 5.47T 12.6T 805G /mnt/zdata zdata/dummy 1.04M 12.6T 1.04M /mnt/zdata/dummy
  4. Afraid it actually did, it worked for all of the below listed datasets: /mnt/zdata/cache /mnt/zdata/downloads /mnt/zdata/isos /mnt/zdata/media I will try to replicate this with a dummy dataset.
  5. From Unraid GUI. By move, I meant the contents i.e. mv source_dataset/* to destination_dataset/. Dataset was renamed as well as per ZFS master plugin and zfs list. zfs list NAME USED AVAIL REFER MOUNTPOINT zdata 5.47T 12.6T 805G /mnt/zdata zdata/cache 232G 12.6T 231G /mnt/zdata/cache zdata/downloads 153G 12.6T 153G /mnt/zdata/downloads zdata/isos 469G 12.6T 469G /mnt/zdata/isos zdata/media 128K 12.6T 128K /mnt/zdata/media zdata/prashant 2.32T 12.6T 2.32T /mnt/zdata/p------- zfs mount zdata /mnt/zdata zdata/cache /mnt/zdata/cache zdata/downloads /mnt/zdata/downloads zdata/isos /mnt/zdata/isos zdata/media /mnt/zdata/media zdata/prashant /mnt/zdata/p-------
  6. Hindsight is 20/20 😭, expensive mistake to say the least.
  7. So, let me try to explain the problem again. 6.11.5: ZFS(RAIDZ1) with zpool called zfs. User share e.g. downloads with a link data to a dataset called downloads in the zpool called zfs Upgrade to 6.12.4 6.12.4: Create a new pool - zdata, and add all HDDs. Global Share Settings -> Permit exclusive shares. Change primary storage for downloads to zfs pool zdata. Now, since the exclusive access is shown as NO renamed old share to downloads_old. created new share called downloads with primary storage as zdata. move data from downloads_old to downloads. Remove old share downloads_old. ^^^^^^^^^^ This is when I lost data ^^^^^^^^^^^^^^ NOTE: Before trying on downloads, I had tried with other shares. After this disaster, I left my last share as is to avoid more data loss. This is the share which you see as exclusive access marked as NO. I had TWO issues, a) Loss of data and b) How to enable exclusive access without going through arduous process creating a new share and copying close 3 TB of data.
  8. Apparently reading is hard. downloads I am still searching for an old copy.
  9. If that is the case why are contents mapped to the corresponding dataset on ZFS pool? So, did the upgrade messed it up ? i.e. after changing the primary storage (6.12.4) to dataset on zfs pool the original share (6.11.5) was left on disk1. Have lost close to 800 GB of data, I won't be trying to lose more data.
  10. That share in question is NOT on disk1 but on pool (zdata). As clearly mentioned in first post, share was created with a link to ZFS dataset in 6.11.5. Please see the first post.
  11. That share is thankfully intact. This share exist only on ZFS pool. How does one FIX this in the first place? Why close the BUG? Is there a way for me to recover deleted data?
  12. I have just one pool, please find the diagnostics as attached. unraidzfs-diagnostics-20230904-1514.zip